Στις 14-04-2010, ημέρα Τετ, και ώρα 13:56 -0700, ο/η Denys Vlasenko έγραψε: > Use option -C. It is documented in udhcpc --help.
I don't have a "-C" option, is my udhcpc too old (0.9.8cvs20050303-3)? I have this: http://manpages.ubuntu.com/udhcpc.8.html The "-c" option (lowercase) is the same as the "--clientid" that I was talking about in my first mail, and is what's causing my problem. So I'd like to propose a small patch that would allow udhcpc to not send a clientid at all. Would that be OK? If I don't specify the -c option, that still doesn't work for me, because udhcpc then generates a clientid and uses it, causing dhcp3-server (or cisco routers) to assign it a new lease after each PXE boot. >From http://www.ietf.org/rfc/rfc2131.txt: If the client uses a 'client identifier' in one message, it MUST use that same identifier in all subsequent messages, to ensure that all servers correctly identify the client. ==> that's the problem, a netbooted client can't send the same identifier for both the PXE and the udhpc request, so it's better if it doesn't send a client identifier at all in this case. -- Alkis _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
