Dňa 07.08.2013 22:50 Sean Alexandre wrote / napísal(a): > Aug 7 06:28:25 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 3 > Aug 7 06:28:28 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 6 > Aug 7 06:28:28 moose kernel: [ 211.369046] e1000e: eth-wan NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None > Aug 7 06:28:28 moose kernel: [ 211.370437] ADDRCONF(NETDEV_CHANGE): eth-wan: link becomes ready > Aug 7 06:28:34 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 12 > Aug 7 06:28:46 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 13 > Aug 7 06:28:59 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 19 > Aug 7 06:29:18 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 8 > Aug 7 06:29:26 moose dhclient: No DHCPOFFERS received. > Aug 7 06:29:26 moose dhclient: No working leases in persistent database - sleeping. Because you don't get any response from DHCP server, there are some more questions... Are you sure, that the network (NIC, cable, etc) is working? Tried you set the static IP or use another DHCP network (for example the one from TP-Link)? Have you firewall enabled? Are you sure, that the firewall is not blocking the response? Try to disable (fllush) the firewall and then run: dhclient eth-wan and check the syslog. Did you some changes in the /etc/dhcp/dhclient.conf? If yes, try revert to default one (you have the backup :-P ). > Something interesting about this is the DHCP offer comes from a private IP > address from my ISP (10.132.192.1), even though the address they give me is > public. Don't worry about this. I have the same situation. My ISP's DHCP server provides for me local (10.0.0.0/8) IPs for DNS servers too, for example, but the interface gets the public IP... regards -- Slavko http://slavino.sk
Attachment:
signature.asc
Description: OpenPGP digital signature