Well, no, I'm not sure since I'm pretty new to this.
What I want is an iPXE based image that the dhcp server will serve. I want
this second stage iPXE to initiate a new dhcpdiscover using new dhcp header
options, specifically the client id. This is what I was trying to do in my
other thread i
On 12/04/16 22:32, Maule Mark wrote:
I've been trying to find an ipxe src base that supports Mellanox PCI
vendor:device ID 15b3:1003. Specifically, I'm trying to get a
undionly,kpxe build for x86_64 that will support this device.
Are you sure that you mean this? The undionly.kpxe binary conta
I've been trying to find an ipxe src base that supports Mellanox PCI
vendor:device ID 15b3:1003. Specifically, I'm trying to get a undionly,kpxe
build for x86_64 that will support this device.
I've tried some of the branches under
https://git.ipxe.org/vendor/mellanox/flexboot.git. The flexboot
On 12/04/16 17:08, Maule Mark wrote:
Yea, they use client-identifier a lot, but I don't see that they ever
say what the id should be, only that it is unique on the subnet. Since
in the general case a system might want to have independent ipaddr's
from the same subnet assigned to dhcp clients run
Yea, they use client-identifier a lot, but I don't see that they ever say what
the id should be, only that it is unique on the subnet. Since in the general
case a system might want to have independent ipaddr's from the same subnet
assigned to dhcp clients running per-port, wouldn't that mean we
On 12/04/16 15:29, Maule Mark wrote:
But wouldn't that cause issues in the general case? If all of the IB
ports will then carry the same client_id, then you can only use dhcp to
assign an ipaddr to one of them (in the general case).
The client hardware address (chaddr) will still be unique.
R
But wouldn't that cause issues in the general case? If all of the IB ports
will then carry the same client_id, then you can only use dhcp to assign an
ipaddr to one of them (in the general case).
In my application, I can guarantee that only one port on a host will be issuing
dhcp discover reque
On 12/04/16 15:04, Maule Mark wrote:
I noticed that. However, dnsmasq only considers client_id (if present)
followed by hwaddr when looking up configs in its hostsfile. I've tried
hacking around that in dnsmasq (by trying to match client_uuid if
present and no client_id match), but the code is
disabling bios serial console redirection did the trick.
Thanks!
From: Sergii Kolisnyk
To: ipxe-devel@lists.ipxe.org
Sent: Monday, April 11, 2016 10:39 PM
Subject: Re: [ipxe-devel] putty and ipxe over serial port
Hi,
have you tried CP437 character set? I think it's what console r
I noticed that. However, dnsmasq only considers client_id (if present)
followed by hwaddr when looking up configs in its hostsfile. I've tried
hacking around that in dnsmasq (by trying to match client_uuid if present and
no client_id match), but the code is pretty tangled and it's not clear to
On 11/04/16 14:00, Michael S. Tsirkin wrote:
On Mon, Apr 11, 2016 at 11:26:55AM +0200, Ladi Prosek wrote:
The goal here is to support booting from modern and transitional
virtio-net devices using the new virtio 1.0 protocol. The code
strives to comply with the virtio 1.0 spec and is heavily insp
On 08/04/16 20:05, Maule Mark wrote:
I have a project where it would be useful for me to set a custom
client_id when using dhcp to configure a network interface.
Specifically, in my case I'd like to pass the SMBIOS uuid as the
client_id for an infiniband port instead of the port GUID. In my
ap
On 04/04/16 10:14, Sergii Kolisnyk wrote:
The clean way is per-target-architecture build directories (for object
files) I think. Then no need to wait.
We have per-target-architecture build directories already.
The problem with multi-architecture targets is that the Makefile
currently spins up
13 matches
Mail list logo
