Re: dhclient "No DHCPOFFERS received"
On Wed, Aug 07, 2013 at 08:29:53PM +0100, Klaus wrote:
> On 07/08/13 20:19, Sean Alexandre wrote:
> >On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
> >>On 07/08/13 18:24, Andy Hawkins wrote:
> >>>In article <[🔎] 20130807164822.GA7727@tuzo>,
> >>>Sean Alexandre<sean@alexan.org> wrote:
> >>>>No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
> >>>>router and the Debian Wheezy machine that works get DHCP leases without any
> >>>>problems, and have different MAC addresses.
> >>>>
> >>>>I also asked my ISP about this, when I had them on the line to bring up my
> >>>>new cable modem. They said any MAC address is fine. Just power the cable
> >>>>modem down for 30 seconds first.
> >>>
> >>>Ok, I did say I was kind of stating the obvious!
> >>>
> >>>Next thing I'd be doing is using tshark or similar to sniff the traffic
> >>>being seen on the Debian box.
> >>>
> >>>Andy
> >>>
> >>>
> >>Just more of the obvious stuff:
> >>You say it's a new cable modem, there is a home router, and there is
> >>at least one other Debian Wheezy box.
> >>Does your ISP provide you with one, or more than one IP address? If
> >>one, the router probably translates this "public" IP address to your
> >>"private" LAN. Does the router function as a DHCP server, or do you
> >>have a dedicated box on your LAN? Can you check the logs of your LAN
> >>DHCP server for entries matching the non-functioning box?
> >
> >There's no NAT in what I'm doing, no. The boxes in each case get a public
> >IP address from my ISP (or try to.) The different cases are:
> >
> >CASE 1, works:
> >[cable modem]---[TP-LINK router]
> >
> >CASE 2, works:
> >[cable modem]---[wheezy box that works]
> >
> >CASE 3, doesn't work:
> >[cable modem]---[wheezy box that doesn't work]
> >
> >I attach a laptop to the TP-LINK router to see that it got an IP address, so
> >there's NAT there. But, NAT doens't come into play for the larger problem, if
> >that's what you're asking.
> >
> >
> Have you checked for DHCP client entries in /var/log/daemon.log ?
> I'm running the standard dhclient, from the isc-dhcp-client package
> (though my box is running SID), and there are log messages like
>
> /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient:
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient: DHCPREQUEST
> on eth0 to 255.255.255.255 port 67
> /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient: DHCPOFFER
> from 192.168.0.1
> /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient: DHCPACK
> from 192.168.0.1
>
On the wheezy box that works I get:
Aug 6 17:46:13 tuzo dhclient: Internet Systems Consortium DHCP Client 4.2.2
Aug 6 17:46:13 tuzo dhclient: Copyright 2004-2011 Internet Systems Consortium.
Aug 6 17:46:13 tuzo dhclient: All rights reserved.
Aug 6 17:46:13 tuzo dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 6 17:46:13 tuzo dhclient:
Aug 6 17:46:13 tuzo dhclient: Listening on LPF/eth0/10:0b:a9:8b:33:f8
Aug 6 17:46:13 tuzo dhclient: Sending on LPF/eth0/10:0b:a9:8b:33:f8
Aug 6 17:46:13 tuzo dhclient: Sending on Socket/fallback
Aug 6 17:46:13 tuzo dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Aug 6 17:46:20 tuzo dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Aug 6 17:46:20 tuzo dhclient: DHCPNAK from 10.132.192.1
Aug 6 17:46:20 tuzo dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Aug 6 17:46:20 tuzo dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Aug 6 17:46:20 tuzo dhclient: DHCPOFFER from 10.132.192.1
Aug 6 17:46:20 tuzo dhclient: DHCPACK from 10.132.192.1
Aug 6 17:46:21 tuzo dhclient: bound to 66.26.64.22 -- renewal in 1705 seconds.
On the wheezy box that doesn't work I get:
Aug 7 06:28:25 moose dhclient: Internet Systems Consortium DHCP Client 4.2.2
Aug 7 06:28:25 moose dhclient: Copyright 2004-2011 Internet Systems Consortium.
Aug 7 06:28:25 moose dhclient: All rights reserved.
Aug 7 06:28:25 moose dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 7 06:28:25 moose dhclient:
Aug 7 06:28:25 moose kernel: [ 208.409987] ADDRCONF(NETDEV_UP): eth-wan: link is not ready
Aug 7 06:28:25 moose dhclient: Listening on LPF/eth-wan/00:25:90:39:de:08
Aug 7 06:28:25 moose dhclient: Sending on LPF/eth-wan/00:25:90:39:de:08
Aug 7 06:28:25 moose dhclient: Sending on Socket/fallback
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.
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.
Reply to: