Hi. I'm familiar with Linux, but this is my first install of SuSE. Everything went fine except I can't ping my LAN. I used the Yast GUI to set up the network DNS host IP and default gateway as 192.168.0.1. If I take the net down and bring it up again with 'ifup eth0' it says it got address 192.168.0.8 / 255.255.255.0. That looks ok. However, I can't ping myself at that address. Can't ping the gateway either. Using 'ifconfig' reports eth0 running in ipv6. Doesn't report anything about 192.168.0.8 at eth0, rather some long inet6 address. I haven't tried ipv6 before. SuSE installed that for me without asking. On a DHCP ipv4 LAN should I run ipv6, and how would I get rid of it? What now? Thanks! Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 29 June 2003 19:59, Robin Rowe wrote:
Hi. I'm familiar with Linux, but this is my first install of SuSE. Everything went fine except I can't ping my LAN.
I used the Yast GUI to set up the network DNS host IP and default gateway as 192.168.0.1. If I take the net down and bring it up again with 'ifup eth0' it says it got address 192.168.0.8 / 255.255.255.0. That looks ok. However, I can't ping myself at that address. Can't ping the gateway either. Using 'ifconfig' reports eth0 running in ipv6. Doesn't report anything about 192.168.0.8 at eth0, rather some long inet6 address. I haven't tried ipv6 before. SuSE installed that for me without asking.
On a DHCP ipv4 LAN should I run ipv6, and how would I get rid of it?
What now?
Thanks!
Robin
--------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
try the loopback - 127.0.0.1 This should tell you if the TCP/IP stack is working correctly. If it works, then your eth0 interface is fragged up. Check for the proper driver for your hardware. I have had the same instance in the past....in version 7.0 though. It turned out that the module loaded for my card was incorrect. So DHCP would not properly broadcast a dhcp_request to the DHCP server. I too got a IPv6 address but no IPv4. If you are utilizing the right driver, then check your cabling. If i were to guess, i'd say it is a driver problem. HTH. - -- Thomas Jones Linux-Howtos Network Administrator OpenGPG Key: 0x6A3DF6E9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+/5NIQT2komo99ukRAtKzAKC/CoHOXe8rxg+M0Wl2HanDOqUsGACgyhbM UlmVJBOT7LpDU+UpoVpog+E= =u37g -----END PGP SIGNATURE-----
Thomas,
try the loopback - 127.0.0.1
That pings ok.
If it works, then your eth0 interface is fragged up. Check for the proper driver for your hardware.
'lspci' reports sis900 and so does 'lsmod'.
If you are utilizing the right driver, then check your cabling.
# ifdown eth0 # rmmod sis900 # modprobe sis900 # ifup eth0 Same as before. Still says 192.168.0.8, but only inet6 address for eth0 reported by 'ifconfig'. Plugged in and has a green light on the back of the NIC. I don't think it would get that DHCP address if it wasn't connecting to the DHCP server. A ping from another box to 192.168.0.8 usually times out, but sometimes gets a reply on just the first packet. By the way, rebooting doesn't help and the NIC works fine running a different distro. More ideas? Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 29 June 2003 22:47, Robin Rowe wrote:
Thomas,
try the loopback - 127.0.0.1
That pings ok.
If it works, then your eth0 interface is fragged up. Check for the proper driver for your hardware.
'lspci' reports sis900 and so does 'lsmod'.
If you are utilizing the right driver, then check your cabling.
# ifdown eth0 # rmmod sis900 # modprobe sis900 # ifup eth0
Same as before. Still says 192.168.0.8, but only inet6 address for eth0 reported by 'ifconfig'.
Plugged in and has a green light on the back of the NIC. I don't think it would get that DHCP address if it wasn't connecting to the DHCP server.
A ping from another box to 192.168.0.8 usually times out, but sometimes gets a reply on just the first packet.
By the way, rebooting doesn't help and the NIC works fine running a different distro.
More ideas?
Robin
If it is in fact completing a successful DHCP request than you should be able to capture the traffic using ethereal or tcpdump. Start either one up using sudo or su and attempt to capture teh "conversation". This will let you determine any RST flags set by the upstream router and/or gateway. - -- Thomas Jones Linux-Howtos Network Administrator OpenGPG Key: 0x6A3DF6E9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+//DTQT2komo99ukRAnU2AJ9rCzWRZnFToT6lB+2QH+A4n3stWgCghp7L 0wKJej6BRJayOqenG3uvfnM= =F6Jz -----END PGP SIGNATURE-----
Hi.
Have you tried route?
route add default gw 192.168.0.1
(will set 192.168.0.1 as default)
Then,
ifconfig eth0 192.168.0.8 netmask 255.255.255.0
ifconfig eth0
<
Hi. I'm familiar with Linux, but this is my first install of SuSE. Everything went fine except I can't ping my LAN.
I used the Yast GUI to set up the network DNS host IP and default gateway as 192.168.0.1. If I take the net down and bring it up again with 'ifup eth0' it says it got address 192.168.0.8 / 255.255.255.0. That looks ok. However, I can't ping myself at that address. Can't ping the gateway either. Using 'ifconfig' reports eth0 running in ipv6. Doesn't report anything about 192.168.0.8 at eth0, rather some long inet6 address. I haven't tried ipv6 before. SuSE installed that for me without asking.
On a DHCP ipv4 LAN should I run ipv6, and how would I get rid of it?
What now?
Thanks!
Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
Robert,
Have you tried route?
route add default gw 192.168.0.1
Responds: 'SIOCADDRT: File exists'.
ifconfig eth0 192.168.0.8 netmask 255.255.255.0
No response. Unchanged, ping still says unreachable. Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
route del default Try and build a new route file. What does ifconfig output look like? It could very well be what Thomas commented. Bad driver. Especally if only v6 is showing. Do you have a fixed # of addresses in Scope on a server or a router? Anyway it's moot till we can look at the output of ifconfig. We need the general setup you have going if were going to get medevil and all :-) On Sunday 29 June 2003 20:53, Robin Rowe wrote:
Robert,
Have you tried route?
route add default gw 192.168.0.1
Responds: 'SIOCADDRT: File exists'.
ifconfig eth0 192.168.0.8 netmask 255.255.255.0
No response.
Unchanged, ping still says unreachable.
Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
Robert,
route del default
Try and build a new route file.
Nothing in route table. Can't add to route table.
What does ifconfig output look like?
# ifconfig eth0 Link encap:Ethernet HWaddr 00:E0:18:53:34:92 inet6 addr: fe80::2e0:18ff:fe53:3492/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14965 errors:0 dropped:0 overruns:0 frame:0 TX packets:14367 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:4184062 (3.9 Mb) TX bytes:3234392 (3.0 Mb) Interrupt:10 Base address:0xd400 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:46 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3112 (3.0 Kb) TX bytes:3112 (3.0 Kb)
Do you have a fixed # of addresses in Scope on a server or a router?
Not sure what you mean. I have an 8-port switch. Nothing special. The indicator for that port on the router is cycling on and off at two second intervals, both link and traffic. Cheers, Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
Hey, sorry I had to go to work. Have you tried editing /etc/sysconfig/network/ifcfg-eth0 ? You could have a look at that and see whats happening. You might even try inserting IPADDR=192.168.0.8 it sounds like the DHCP server is going to just keep handing out that .0.8 for now so it's worth a try unless you plug into another port. It's really strange you can't set a gateway, so while you are poking around /etc/sysconfig/network open up config and have a look. There might be something amiss there.
# ifconfig eth0 Link encap:Ethernet HWaddr 00:E0:18:53:34:92 inet6 addr: fe80::2e0:18ff:fe53:3492/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14965 errors:0 dropped:0 overruns:0 frame:0 TX packets:14367 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:4184062 (3.9 Mb) TX bytes:3234392 (3.0 Mb) Interrupt:10 Base address:0xd400
That is strange there is no v4 in eth0 but there is in localhost. It's almost like it is a software bug. maybe you should uninstall the card and try it in a different slot and reinstall it. Maybe even recompile the driver to the kernel. I read the thread from Thomas and I would definately try a traffic monitor if it will work as crippled as you are.
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:46 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3112 (3.0 Kb) TX bytes:3112 (3.0 Kb) It is sounding like a bizarre dependancy problem to my newbie self. You said
the card worked with another distro but is gunnybag now. Have another card around? You could try it and if it worked it narrows it down some. Maybe hardware SuSE doesn't like (like my old HDD) or it could be the driver. Maybe,maybe,maybe... sorry I'm such a greenhorn. Luck to you, let us know how it turns out.
--------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software
participants (3)
-
Robin Rowe -
Robt. Lount -
Thomas Jones