Re: dhclient No DHCPOFFERS received
On 8/7/2013 4:53 PM, Sean Alexandre wrote: On Wed, Aug 07, 2013 at 09:29:57PM +0200, Slavko wrote: is your network like this, please: - |ISP| - | | - | modem | - | -- | | | - - - | Debian I | | Debian II | | TP-Link | - - - or like this? - |ISP| - | | - | modem | - | | - | TP-Link | - | -- || - - | Debian I | | Debian II | - - My network is like your first diagram, but with only one machine connected to the modem at a time. Getting a public address from a private DHCP server is not wrong. The DHCP server may have been given those addresses by the upstream server for allocation. That takes a load off the upstream server. One thought. Just because there is only one machine connected at a time does NOT mean the previous DHCP lease has been released. It may still be considered active by the DHCP server. For instance - if you hook up one machine and get a least, that lease may be good for an hour to a week (or more). If you hook a second one up, that may also get a lease for the same amount of time. Then if you disconnect the first two (or even disconnect the first machine before connecting the second machine) and only have two leases available, you will see this problem. The cable company was not necessarily incorrect when telling you to power off the cable modem then powering it back on. This will probably reset all leases. What happens if you do power the cable modem off like they said then power it back on, followed by connecting only the failing machine? And BTW - you said all of the computers have different MAC addresses. I would hope so! Hardware MAC addresses for a port are unique in the entire world - every one HAS to be different. Of course some OS's allow you to override the hardware MAC address, but that's another story. -- 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/52043a5b.5060...@attglobal.net
Re: dhclient No DHCPOFFERS received
Hi, In article 20130807133856.GA6733@tuzo, Sean Alexandres...@alexan.org wrote: I've got two Debian Wheezy machines. One can connect to my cable modem fine, and gets an IP address. The other can't. They're both configured the same. Any ideas why this might be? Apologies for suggesting something obvious you might already have thought of, but I seem to recall my Cable provider's modem will only provide DHCP addresses to a single MAC unless it's been correctly release (or perhaps the Cable Modem re-powered). Could it be as simple as that? Andy -- 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/slrnl04o3m.1kp.a...@xcp-mailnews.gently.org.uk
Re: dhclient No DHCPOFFERS received
On Wed, Aug 07, 2013 at 02:57:58PM +, Andy Hawkins wrote: Sean Alexandres...@alexan.org wrote: I've got two Debian Wheezy machines. One can connect to my cable modem fine, and gets an IP address. The other can't. They're both configured the same. Any ideas why this might be? Apologies for suggesting something obvious you might already have thought of, but I seem to recall my Cable provider's modem will only provide DHCP addresses to a single MAC unless it's been correctly release (or perhaps the Cable Modem re-powered). Could it be as simple as that? 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. -- 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/20130807164822.GA7727@tuzo
Re: dhclient No DHCPOFFERS received
Hi, In article 20130807164822.GA7727@tuzo, Sean Alexandres...@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 -- 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/slrnl050n9.53b.a...@xcp-mailnews.gently.org.uk
Re: dhclient No DHCPOFFERS received
On 07/08/13 18:24, Andy Hawkins wrote: Hi, In article 20130807164822.GA7727@tuzo, Sean Alexandres...@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? -- Klaus -- 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/52028f0d.6090...@gmail.com
Re: dhclient No DHCPOFFERS received
On Wed, Aug 07, 2013 at 05:24:57PM +, Andy Hawkins wrote: In article 20130807164822.GA7727@tuzo, Sean Alexandres...@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. OK, thanks, that's where I was headed, but was hoping it was something more obvious. I can get a tcpdump, but don't know DHCP very well. I'll take a look, though, and see what I can figure out. -- 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/20130807191154.GA8969@tuzo
Re: dhclient No DHCPOFFERS received
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 Alexandres...@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. -- 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/20130807191905.GB8969@tuzo
Re: dhclient No DHCPOFFERS received
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 Alexandres...@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 -- Klaus -- 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/5202a031.7010...@gmail.com
Re: dhclient No DHCPOFFERS received
Dňa 07.08.2013 21:19 Sean Alexandre wrote / napísal(a): 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 Alexandres...@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. is your network like this, please: - |ISP| - | | - | modem | - | -- | | | - - - | Debian I | | Debian II | | TP-Link | - - - or like this? - |ISP| - | | - | modem | - | | - | TP-Link | - | -- || - - | Debian I | | Debian II | - - regards -- Slavko http://slavino.sk signature.asc Description: OpenPGP digital signature
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 Alexandres...@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
Re: dhclient No DHCPOFFERS received
On Wed, Aug 07, 2013 at 09:29:57PM +0200, Slavko wrote: is your network like this, please: - |ISP| - | | - | modem | - | -- | | | - - - | Debian I | | Debian II | | TP-Link | - - - or like this? - |ISP| - | | - | modem | - | | - | TP-Link | - | -- || - - | Debian I | | Debian II | - - My network is like your first diagram, but with only one machine connected to the modem at a time. -- 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/20130807205320.GB9875@tuzo
Re: dhclient No DHCPOFFERS received
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 signature.asc Description: OpenPGP digital signature
Re: dhclient No DHCPOFFERS received
Sean Alexandre wrote: OK, thanks, that's where I was headed, but was hoping it was something more obvious. I can get a tcpdump, but don't know DHCP very well. I'll take a look, though, and see what I can figure out. The 'dhcpdump' package is useful for debugging dhcp issues. Easier than wireshark because it is specific to the dhcp protocol. $ apt-cache show dhcpdump Description-en: Parse DHCP packets from tcpdump This package provides a tool for visualization of DHCP packets as recorded and output by tcpdump to analyze DHCP server responses. Use it like this: # dhcpdump -i eth0 It will dump the decoded frames to standard output. Bob signature.asc Description: Digital signature
