OK, I've been puzzling this one for a while now... and still can't quite figure it out. I have a cable modem connected to a router, and my router does DHCP for the machines in my home network - a desktop, and a laptop. Both computers run SUSE9.0 with the SUSEFirewall enabled. If (for whatever reason) I do an 'ifdown eth0' and an 'ifup eth0' on the desktop computer, it asks for an IP and gets one, but then cannot communicate with any computer in the internal network, and cannot access the web. I cannot ping and get a reply on any internet address at all. Same goes for internal IPs. I cannot find anything in the message log that seems related. If I do the same thing on the laptop, it gets an IP assigned and immediately has access to both the internal network, and the internet. The only way I've found to get the desktop communicating with the network after I do an 'ifdown eth0' is to do a reboot. So... any ideas of what to look for? Why would doing an ifdown followed by an ifup on this one machine block all future network access until a restart? C.
On Sat, 2003-11-22 at 23:22, Clayton wrote:
OK, I've been puzzling this one for a while now... and still can't quite figure it out.
I have a cable modem connected to a router, and my router does DHCP for the machines in my home network - a desktop, and a laptop. Both computers run SUSE9.0 with the SUSEFirewall enabled.
If (for whatever reason) I do an 'ifdown eth0' and an 'ifup eth0' on the desktop computer, it asks for an IP and gets one, but then cannot communicate with any computer in the internal network, and cannot access the web. I cannot ping and get a reply on any internet address at all. Same goes for internal IPs. I cannot find anything in the message log that seems related.
If I do the same thing on the laptop, it gets an IP assigned and immediately has access to both the internal network, and the internet.
The only way I've found to get the desktop communicating with the network after I do an 'ifdown eth0' is to do a reboot.
So... any ideas of what to look for? Why would doing an ifdown followed by an ifup on this one machine block all future network access until a restart?
C.
I am running SuSE Linux 8.2 but if you use # /etc/inet.d/network stop/start Wouldn't that be better and work for you ? Dee -- W.D.McKinney (Dee) | Affordable E-Mail and Internet Solutions Alaska Wireless Systems | for Schools, Libraries, Clinics & Businesses http://www.akwireless.net | Call 1-907-349-4308
On Sunday 23 November 2003 09:36, W.D. McKinney wrote:
If (for whatever reason) I do an 'ifdown eth0' and an 'ifup eth0' on the desktop computer, it asks for an IP and gets one, but then cannot communicate with any computer in the internal network, and cannot access the web. I cannot ping and get a reply on any internet address at all. Same goes for internal IPs.
I am running SuSE Linux 8.2 but if you use # /etc/inet.d/network stop/start
Wouldn't that be better and work for you ?
Tried your suggestion. The network goes down normally, and then I can bring it back up... eth0 requests and gets an IP from the router... and then nothing. I can't even ping the router. If I do the same with my laptop (virtually identical install of SUSE9.0), I have no problems. If I tail /var/log/messages when I try to start the network, I see this (192.168.1.1 is my router): ---------------------------------------------------- Nov 23 14:26:37 linux kernel: eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1. Nov 23 14:26:37 linux kernel: martian source 255.255.255.255 from 192.168.1.1, on dev eth0 Nov 23 14:26:37 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:03:9d:51:1f:3a:08:00 Nov 23 14:26:37 linux modify_resolvconf: Service dhcpcd modified /etc/ resolv.conf. See info block in this file Nov 23 14:26:52 linux kernel: eth0: no IPv6 routers present ----------------------------------------------------- What's puzzling me is that I can get an IP from the router, and that on boot everything works fine... I'm at a loss to explain why I can't simply start/ stop my network on 9.0 like I could on 8.2.... C.
On Sun, 2003-11-23 at 03:22, Clayton wrote:
OK, I've been puzzling this one for a while now... and still can't quite figure it out.
I have a cable modem connected to a router, and my router does DHCP for the machines in my home network - a desktop, and a laptop. Both computers run SUSE9.0 with the SUSEFirewall enabled.
If (for whatever reason) I do an 'ifdown eth0' and an 'ifup eth0' on the desktop computer, it asks for an IP and gets one, but then cannot communicate with any computer in the internal network, and cannot access the web. I cannot ping and get a reply on any internet address at all. Same goes for internal IPs. I cannot find anything in the message log that seems related.
If I do the same thing on the laptop, it gets an IP assigned and immediately has access to both the internal network, and the internet.
The only way I've found to get the desktop communicating with the network after I do an 'ifdown eth0' is to do a reboot.
So... any ideas of what to look for? Why would doing an ifdown followed by an ifup on this one machine block all future network access until a restart?
You can try and do after you tell the card to come back up you can do a dhcpcd eth0 and see then if you can get out of the internet. If not, then it seems like that you are not getting the default route during DHCP. If the above does not help, post the results of the ifconfig and route -n command and someone here will try and help you. -- Marshall "Nothing is impossible, we just do not have all the answers to make the impossible, possible."
If (for whatever reason) I do an 'ifdown eth0' and an 'ifup eth0' on the desktop computer, it asks for an IP and gets one, but then cannot communicate with any computer in the internal network, and cannot access the web. I cannot ping and get a reply on any internet address at all. Same goes for internal IPs. I cannot find anything in the message log that seems related.
If I do the same thing on the laptop, it gets an IP assigned and immediately has access to both the internal network, and the internet.
The only way I've found to get the desktop communicating with the network after I do an 'ifdown eth0' is to do a reboot.
So... any ideas of what to look for? Why would doing an ifdown followed by an ifup on this one machine block all future network access until a restart?
You can try and do after you tell the card to come back up you can do a dhcpcd eth0 and see then if you can get out of the internet. If not, then it seems like that you are not getting the default route during DHCP. If the above does not help, post the results of the ifconfig and route -n command and someone here will try and help you.
Whew, busy week.. this is the first time I've had a chance to get back to this. I'm still having this odd networking problem on my desktop computer... Here's some extra data.. # ifdown eth0 # ifup eth0 Starting DHCP Client Daemon on eth0... . . . . . . . . . . IP/Netmask: 192.168.1.2 / 255.255.255.0 # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 # dhcpcd eth0 **** dhcpcd: already running **** dhcpcd: if not then delete /var/run//dhcpcd-eth0.pid file # ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. --- 192.168.1.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms Now if I compare the settings with my laptop running the same basic install of SUSE9.0 I see the exact same as on the desktop... except the desktop won't connect after I do an ifdown eth0. On the laptop, I have no problems bringing the network down and back up again... the desktop will only reconnect after a reboot. So... Im still looking for ideas here.... C.
If (for whatever reason) I do an 'ifdown eth0' and an 'ifup eth0' on the desktop computer, it asks for an IP and gets one, but then cannot communicate with any computer in the internal network, and cannot access the web. I cannot ping and get a reply on any internet address at all. Same goes for internal IPs. I cannot find anything in the message log that seems related.
If I do the same thing on the laptop, it gets an IP assigned and immediately has access to both the internal network, and the internet.
The only way I've found to get the desktop communicating with the network after I do an 'ifdown eth0' is to do a reboot.
So... any ideas of what to look for? Why would doing an ifdown followed by an ifup on this one machine block all future network access until a restart?
You can try and do after you tell the card to come back up you can do a dhcpcd eth0 and see then if you can get out of the internet. If not, then it seems like that you are not getting the default route during DHCP. If the above does not help, post the results of the ifconfig and route -n command and someone here will try and help you.
Whew, busy week.. this is the first time I've had a chance to get back to this. I'm still having this odd networking problem on my desktop computer... Here's some extra data.. # ifdown eth0 # ifup eth0 Starting DHCP Client Daemon on eth0... . . . . . . . . . . IP/Netmask: 192.168.1.2 / 255.255.255.0 # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 # dhcpcd eth0 **** dhcpcd: already running **** dhcpcd: if not then delete /var/run//dhcpcd-eth0.pid file # ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. --- 192.168.1.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms Now if I compare the settings with my laptop running the same basic install of SUSE9.0 I see the exact same as on the desktop... except the desktop won't connect after I do an ifdown eth0. On the laptop, I have no problems bringing the network down and back up again... the desktop will only reconnect after a reboot. So... Im still looking for ideas here.... C.
participants (3)
-
Clayton -
Marshall Heartley -
W.D. McKinney