Pascal Hibon wrote: > This so called client I'd is probably a host name but I have never seen > that being used when using network monitors.
Network monitors... I know Wireshark shows a client sending Option 61 (client identifier) when requesting dhcp if you look at the bootp params. (A few Broadband ISP's use it to identify customers. ie. it is used as username/password.) Pascal Hibon wrote: > What I'm trying to say is that the issue is probably not caused by this > 'client id'. Agreed. As I said, I was just thinking out loud. Having used wireshark to see what the client is sending over the wire, a client identifier isn't sent unless 'DHCP_CLIENT_ID=' is explicitly set in the ifcfg-XXXX. Option 12, Host Name, is set (to 'wandboard') and sent for both interfaces in the request. ------------------------------------------------------------------------ JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069 View this thread: http://forums.slimdevices.com/showthread.php?t=98544 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
