Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
client identifier
2012-03-20, 19:39
Post: #3
RE: client identifier
I've encountered this in a different context.

One easy way to stop iPXE from doing UID-present DHCP call is to 'skip' it entirely. Use undionly.kkpxe, and use the use-cache 1 flag in your .ipxe script to keep the IP info from the PXE stack DHCP response packet instead of making a new request. PXE doesn't support UID, so will have the MAC-only lease assigned to it, which the linux install will then re-use.

More linux distros are including UID now, so if this matters in a lab with many reboots it can be helpful to know that you can disable UID (Client Identifier) support in all the common dhcpc implementations.

E.g. udhcpc has ' -C ' to disable client identifier.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
client identifier - mafalb - 2012-01-26, 17:11
RE: client identifier - robinsmidsrod - 2012-01-26, 21:20
RE: client identifier - tekgnosis - 2012-03-20 19:39



User(s) browsing this thread: 2 Guest(s)