Timeline for Why does dhclient fail with my ISP's DHCP server on a virtual interface?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2013 at 2:09 | comment | added | Andrew B |
I should also add that the VM host's interface was not configured with an address or boot time parameters, was not rebooted during the troubleshooting, and could not obtain an IP address via dhclient. I think it's pretty safe to say that it was not binding to the MAC address of the VM host, particularly since many cable modem reboots did nothing to fix the problem until the MAC was changed.
|
|
| Feb 3, 2013 at 2:42 | comment | added | Andrew B |
I'm not sure "you do the DHCP request to the modem itself" is accurate in this case. Based on the tcpdump traffic I was sniffing, I was seeing DHCP responses being broadcast to machines that were not on my network, and a great deal of ARP traffic for hosts not on my network. My impression based on this was that I was being bridged into the cable provider's network after the modem finished initializing. In either case, your suggestion that the cable modem was binding to the VM host's MAC doesn't seem fit given the repeatedly reproducible 192.168.100.0/24 leases during initialization.
|
|
| Feb 3, 2013 at 1:48 | history | answered | Aaron D. Marasco | CC BY-SA 3.0 |