I have a machine that's not acquiring a DHCP lease from my ISP. I can see that dhclient is sending DHCPDISCOVER messages. My system log has:
Aug 25 17:36:41 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 7 Aug 25 17:36:48 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 13 Aug 25 17:37:01 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 12 Aug 25 17:37:13 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 12 Aug 25 17:37:25 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 5 Aug 25 17:37:30 athabasca dhclient: No DHCPOFFERS received. Aug 25 17:37:30 athabasca dhclient: No working leases in persistent database - sleeping. But for some reason the DHCPDISCOVER messages aren't making it out over the NIC. I'm running dhcpdump and see no traffic. This is with no firewall rules. All tables and chains are set to ACCEPT. The odd thing is if I do the exact same thing with this machine connected to a local TP-LINK router instead of my ISP cable modem, dhcpdump sees the DHCPDISCOVER, and the machine acquires a DHCP lease. Any ideas why would dhclient be sending a DHCPDISCOVER, but dhcpdump not see it? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130826083131.GA6922@tuzo
