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<s...@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
