Can't get DHCP address from cable modem
Hello, I'm trying to upgrade my cable-modem firewall -- I'm currently running SuSE 8.2 on an old P5 box, and I'm upgrading to 9.3 on a K6-2/400. SuSE installed ok, I've verified that both NICs function properly when connected to my local LAN, etc. The problem is that when I connect the external NIC to the cable-modem hub, it doesn't seem to get a DHCP address back, and I'm at a loss to understand what's going wrong. Here's what I've been able to learn... eth0 is the external and eth1 is the internal (I wish that I could switch them, but that's how it seems to assign them no matter what I do). dhcpcd from eth1 (internal) works fine, gets an address from my internal DHCP server correctly, etc. At boot time, it give a message (I didn't write it down, but from memory) "no address... backgrounding" [for eth0]. After booting, when I run "ifup eth0", I get something like this: eth0 device: Realtek Semiconductor Co, Ltd. RTL-8029(AS) eth0 configuration: eth-id-00:40:33:52:4e:4e Running "dhcpcd -d" by hand gives me: dhcpcd: MAC address = 00:40:33:57:4e:4e From the logs, I see a lot of entries like these: Martian source 255.255.255.255 from 10.40.32.1, on dev eth0 ll header: ff ff ff ff ff ff 00 04 9b eb c4 54 08 00 Finally, from ifconfig, I get this: eth0 Link encap:Ethernet HWaddr 00:40:33:57:4E:4E inet6 addr: fe80::240:33ff:fe57:4e:4e/64 Scope:Link Does anybody have any clues as to what could be going wrong here, and, hopefully, a solution? I really need to get this working soon because my old firewall box is dying rapidly, and I'm having a difficult time keeping it running. I greatly appreciate any help! -Nick -- <<< Welcome to the real world. >>> /`-_ Nicholas R. LeRoy The Condor Project { }/ http://www.cs.wisc.edu/~nleroy http://www.cs.wisc.edu/condor \ / nleroy@cs.wisc.edu The University of Wisconsin |_*_| 608-265-5761 Department of Computer Sciences
Nick LeRoy zei:
Hello,
I'm trying to upgrade my cable-modem firewall -- I'm currently running SuSE 8.2 on an old P5 box, and I'm upgrading to 9.3 on a K6-2/400. SuSE installed ok, I've verified that both NICs function properly when connected to my local LAN, etc.
The problem is that when I connect the external NIC to the cable-modem hub, it doesn't seem to get a DHCP address back, and I'm at a loss to understand what's going wrong.
<<>>
Does anybody have any clues as to what could be going wrong here, and, hopefully, a solution? I really need to get this working soon because my old firewall box is dying rapidly, and I'm having a difficult time keeping it running.
Is your ISP checking the MAC_address (and you have a different one now?)
I greatly appreciate any help!
-Nick
-- <<< Welcome to the real world. >>> /`-_ Nicholas R. LeRoy The Condor Project { }/ http://www.cs.wisc.edu/~nleroy http://www.cs.wisc.edu/condor \ / nleroy@cs.wisc.edu The University of Wisconsin |_*_| 608-265-5761 Department of Computer Sciences
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- L. de Braal BraHa Systems NL Terneuzen T +31 115 649333 F +31 115 649444
On Wed May 4 2005 10:33 am, Leen de Braal wrote:
Nick LeRoy zei:
Hello, Does anybody have any clues as to what could be going wrong here, and, hopefully, a solution? I really need to get this working soon because my old firewall box is dying rapidly, and I'm having a difficult time keeping it running.
Is your ISP checking the MAC_address (and you have a different one now?)
That's what I'd assumed at first, but.... I've been running 2 boxes connected to the hub at a time for quite a while -- a self contained Linux box and the firewall box, and both were getting valid IP address from DHCP. Now, with my old firewall (it's been dead for over 2 days now), the DHCP lease should that it held should have expired, shouldn't it have? I don't think that I've ever given Charter (the ISP) the MAC address of any of the machines that I've connected in the past. Perhaps I should contact them? -Nick -- <<< There is no spoon. >>> /`-_ Nicholas R. LeRoy The Condor Project { }/ http://www.cs.wisc.edu/~nleroy http://www.cs.wisc.edu/condor \ / nleroy@cs.wisc.edu The University of Wisconsin |_*_| 608-265-5761 Department of Computer Sciences
On Wednesday 04 May 2005 11:45 am, Nick LeRoy wrote:
On Wed May 4 2005 10:33 am, Leen de Braal wrote:
Nick LeRoy zei:
Hello, Does anybody have any clues as to what could be going wrong here, and, hopefully, a solution? I really need to get this working soon because my old firewall box is dying rapidly, and I'm having a difficult time keeping it running.
Is your ISP checking the MAC_address (and you have a different one now?)
That's what I'd assumed at first, but.... I've been running 2 boxes connected to the hub at a time for quite a while -- a self contained Linux box and the firewall box, and both were getting valid IP address from DHCP. Now, with my old firewall (it's been dead for over 2 days now), the DHCP lease should that it held should have expired, shouldn't it have? I don't think that I've ever given Charter (the ISP) the MAC address of any of the machines that I've connected in the past. Perhaps I should contact them?
Nope.......probably don't need to. 'Sounds like it all needs to be reset. Shut down the 'puter. Then, kill the power to the HUB AND the cable modem. Leave them OFF for 5 mins. Then, turn on the modem, once up, turn on the HUB, then the 'puter. All should be well. Fred -- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
On Wednesday 04 May 2005 6:17 pm, Fred A. Miller wrote:
Nope.......probably don't need to. 'Sounds like it all needs to be reset. Shut down the 'puter. Then, kill the power to the HUB AND the cable modem. Leave them OFF for 5 mins. Then, turn on the modem, once up, turn on the HUB, then the 'puter. All should be well.
Fred, You hit the nail on the head. Actually, I didn't need to reset the hub or the computer, but power cycling the cable modem did the trick. :=) Thanks much to all, -Nick -- <<< Why, oh, why, didn't I take the blue pill? >>> /`-_ Nicholas R. LeRoy The Condor Project { }/ http://www.cs.wisc.edu/~nleroy http://www.cs.wisc.edu/condor \ / nleroy@cs.wisc.edu The University of Wisconsin |_*_| 608-265-5761 Department of Computer Sciences
On 5/4/05, Nick LeRoy <nleroy@cs.wisc.edu> wrote:
Hello,
I'm trying to upgrade my cable-modem firewall -- I'm currently running SuSE 8.2 on an old P5 box, and I'm upgrading to 9.3 on a K6-2/400. SuSE installed ok, I've verified that both NICs function properly when connected to my local LAN, etc.
The problem is that when I connect the external NIC to the cable-modem hub, it doesn't seem to get a DHCP address back, and I'm at a loss to understand what's going wrong.
Here's what I've been able to learn... eth0 is the external and eth1 is the internal (I wish that I could switch them, but that's how it seems to assign them no matter what I do). dhcpcd from eth1 (internal) works fine, gets an address from my internal DHCP server correctly, etc.
At boot time, it give a message (I didn't write it down, but from memory) "no address... backgrounding" [for eth0].
Hi Nick, did I understand correctly that you have one internal dhcpd on another machine to assign the internal IP to eth1? Can it be a conflict between the dhcp servers than. Try setting eth1 with static IP. Saying "cable-modem hub", does it mean that you have a hub between the modem and the machine? Is it possible something else connected to that hub (or it by itself) be running another dhcp server? I had such a problem, connecting a wireless router (D-Link) between my machine and the modem, and I got the same problems as you. I solved it bu turning off the dhcp server of the modem, and letting the router to assign addresses. Also, make sure that you get always the same name for each card. I read your system does not switch them, but who knows, reassurance is not so bad :) Cheers Sunny
On Wed May 4 2005 10:45 am, Sunny wrote:
On 5/4/05, Nick LeRoy <nleroy@cs.wisc.edu> wrote: Hi Nick, did I understand correctly that you have one internal dhcpd on another machine to assign the internal IP to eth1?
Yes, My network looks something like this (ASCII art sucks, I know, but...) Pretty standard setup, actually. [cable-modem] | [External hub] ------------------[Internal switch] | |eth0 |eth1 | | | | [other-Linux] [firewall] [File-Server] | | | | | [pc1] [pc2] ...
Can it be a conflict between the dhcp servers than. Try setting eth1 with static IP.
That seems unlikely -- the networks are physically separate. But, it's certainly worth trying, if nothing else to verify that the dhcpcd daemons aren't somehow conflicting with each other.
Saying "cable-modem hub", does it mean that you have a hub between the modem and the machine? Is it possible something else connected to that hub (or it by itself) be running another dhcp server? I had such a problem, connecting a wireless router (D-Link) between my machine and the modem, and I got the same problems as you. I solved it bu turning off the dhcp server of the modem, and letting the router to assign addresses.
I'm quite certain that they're not, but I'll check again when I get home. The hub in question is just a dumb-old 8 port 10-base-T hub.
Also, make sure that you get always the same name for each card. I read your system does not switch them, but who knows, reassurance is not so bad :)
I'll play around some more. Thanks! -Nick -- <<< The Matrix is everywhere. >>> /`-_ Nicholas R. LeRoy The Condor Project { }/ http://www.cs.wisc.edu/~nleroy http://www.cs.wisc.edu/condor \ / nleroy@cs.wisc.edu The University of Wisconsin |_*_| 608-265-5761 Department of Computer Sciences
participants (4)
-
Fred A. Miller -
Leen de Braal -
Nick LeRoy -
Sunny