Still cannot ping from fresh 8.1 CD install
Dear kind autoinstallers, I have been unable to connect my newly installed SUSE 8.1 to my local network: no pings in or out. I used YAST2 to set it up and based my setup on another SUSE box that I had previously setup on the same network without a hitch. As an aside, I've been using and admin'ing various unices since the 80's, although I still consider myself to be something of an amateur, given that there are only so many hours in the day. This is an out-of-the-box clean install using the latest SUSE 8.1 cdroms purchased last week. This is a known-good hardware situation. I have a small LAN with a router and switch that connects to broadband. I'm not running DNS or DHCP locally, just static addresses locally and remote DNS. Here's the output of ifstatus: datran6:/etc/sysconfig/network # ifstatus eth0 eth0 is up 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:30:48:12:43:38 brd ff:ff:ff:ff:ff:ff inet 192.168.1.12/24 brd 192.168.1.255 scope global eth0 inet6 fe80::230:48ff:fe12:4338/10 scope link Configured routes for interface eth0: default 192.168.1.1 - - Active routes for interface eth0: 192.168.1.0/24 proto kernel scope link src 192.168.1.12 default via 192.168.1.1 0 of 1 configured routes for interface eth0 up As you can see, the box has a static ip of 192.168.1.12 (this is an ip unique to this machine) and the broadcast looks good. I'm not sure about the inet6 address, as I was under the impression that this wasn't fully implemented yet. The only thing I see that might be fishy is that there are 0 of 1 configured routes up. Here's a look at the interfaces using ifconfig: datran6:/etc/sysconfig/network # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:30:48:12:43:38 inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe12:4338/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:920 errors:0 dropped:0 overruns:0 frame:0 TX packets:338 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:21032 (20.5 Kb) Interrupt:11 Base address:0x3400 Memory:fc222000-fc222038 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:356 errors:0 dropped:0 overruns:0 frame:0 TX packets:356 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:30922 (30.1 Kb) TX bytes:30922 (30.1 Kb) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) That all looks correct to me, again with the caveat that I don't know what inet6 addressing is doing here. So, here's the routing table as reported by route: datran6:/etc/sysconfig/network # 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 Still looks good. What about the routing table as reported by netstat? datran6:/etc/sysconfig/network # netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface ^C Ouch. Nothing. And I had to Ctrl-C to get back to the prompt. That just doesn't make sense to me unless there isn't a daemon running that should be. So I tried adding a line to the /etc/networks file to see how netstat would respond. datran6:/etc/sysconfig/network # cat >> /etc/networks local 192.168.1.0 datran6:/etc/sysconfig/network # netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface local * 255.255.255.0 U 40 0 0 eth0 ^C Still had to Ctrl-C out of netstat, but it at least now reports the correct first line with 192.168.1.0 translated as "local". I just don't understand why netstat can't find the routing table that is correctly reported by route. Is there a daemon that YAST2 isn't starting? I have tried with and without inetd (a long shot, admittedly). What am I missing here? I thank you for your patience and kind attention. Best regards, Steve Boker --------------------------------------------------------------------- Steven M. Boker 574-339-0735 (cell/page/message) sboker@nd.edu 574-631-4941 (office) http://www.nd.edu/~sboker/ 574-631-8883 (fax) Dept. of Psychology, University of Notre Dame, Notre Dame, IN 46556 ---------------------------------------------------------------------
Hi, This is not the right mailing list for such subjects, please post to other lists, i.e. suse-linux-e@suse.de Anas * Steven Boker <sboker@mac.com> [Jan 21. 2003 18:20]:
Dear kind autoinstallers,
I have been unable to connect my newly installed SUSE 8.1 to my local network: no pings in or out. I used YAST2 to set it up and based my setup on another SUSE box that I had previously setup on the same network without a hitch. As an aside, I've been using and admin'ing various unices since the 80's, although I still consider myself to be something of an amateur, given that there are only so many hours in the day.
This is an out-of-the-box clean install using the latest SUSE 8.1 cdroms purchased last week. This is a known-good hardware situation.
I have a small LAN with a router and switch that connects to broadband. I'm not running DNS or DHCP locally, just static addresses locally and remote DNS. Here's the output of ifstatus:
datran6:/etc/sysconfig/network # ifstatus eth0 eth0 is up 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:30:48:12:43:38 brd ff:ff:ff:ff:ff:ff inet 192.168.1.12/24 brd 192.168.1.255 scope global eth0 inet6 fe80::230:48ff:fe12:4338/10 scope link Configured routes for interface eth0: default 192.168.1.1 - - Active routes for interface eth0: 192.168.1.0/24 proto kernel scope link src 192.168.1.12 default via 192.168.1.1 0 of 1 configured routes for interface eth0 up
As you can see, the box has a static ip of 192.168.1.12 (this is an ip unique to this machine) and the broadcast looks good. I'm not sure about the inet6 address, as I was under the impression that this wasn't fully implemented yet. The only thing I see that might be fishy is that there are 0 of 1 configured routes up.
Here's a look at the interfaces using ifconfig:
datran6:/etc/sysconfig/network # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:30:48:12:43:38 inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe12:4338/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:920 errors:0 dropped:0 overruns:0 frame:0 TX packets:338 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:21032 (20.5 Kb) Interrupt:11 Base address:0x3400 Memory:fc222000-fc222038
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:356 errors:0 dropped:0 overruns:0 frame:0 TX packets:356 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:30922 (30.1 Kb) TX bytes:30922 (30.1 Kb)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
That all looks correct to me, again with the caveat that I don't know what inet6 addressing is doing here.
So, here's the routing table as reported by route:
datran6:/etc/sysconfig/network # 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
Still looks good. What about the routing table as reported by netstat?
datran6:/etc/sysconfig/network # netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface ^C
Ouch. Nothing. And I had to Ctrl-C to get back to the prompt. That just doesn't make sense to me unless there isn't a daemon running that should be.
So I tried adding a line to the /etc/networks file to see how netstat would respond.
datran6:/etc/sysconfig/network # cat >> /etc/networks local 192.168.1.0 datran6:/etc/sysconfig/network # netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface local * 255.255.255.0 U 40 0 0 eth0 ^C
Still had to Ctrl-C out of netstat, but it at least now reports the correct first line with 192.168.1.0 translated as "local". I just don't understand why netstat can't find the routing table that is correctly reported by route.
Is there a daemon that YAST2 isn't starting? I have tried with and without inetd (a long shot, admittedly). What am I missing here?
I thank you for your patience and kind attention.
Best regards, Steve Boker
--------------------------------------------------------------------- Steven M. Boker 574-339-0735 (cell/page/message) sboker@nd.edu 574-631-4941 (office) http://www.nd.edu/~sboker/ 574-631-8883 (fax) Dept. of Psychology, University of Notre Dame, Notre Dame, IN 46556 ---------------------------------------------------------------------
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi Steve, You wrote to the [suse-autoinstall] mailing list, which has a bit different focus: Automated installation of SuSE Linux with the tool autoyast. You might get further help on the other suse mailing lists .. (Probably "suse-linux-e") Anyway: I might have some helpfull suggestions, even if I don't see the solution to your problem, yet. I think I can ride out three non-errors. netstat -nr shows the routing *without name resolution* (if you don't have a proper dns working .. or a full /etc/hosts file, you don't get name resolution, and netstat -r will need a very long time ) netstat -nr and route -n should show the same, on this platform, btw. IPv6 shouldn't hurt - even if the most of us don't do IPv6, yet. Suse boxes have it as default since v 7.3 or earlier, IIRC. (Somehow it's possible to disable it - but it's usually not worth the effort.) ifstatus eth0 shows on my boxes the same than on yours in that line:
0 of 1 configured routes for interface eth0 up I don't know what that message really tells us - but my boxes are telling the same and *do* networking just fine. (It might have to do with a new feature: you can create special routing files for routes which are depending on the up or down status of each single network interface. Quite nice for special networking stuff - but not needed in your simple case.)
Your thought that inetd is *not* needed for a ping is of course correct.
datran6:/etc/sysconfig/network # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:30:48:12:43:38 inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe12:4338/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:920 errors:0 dropped:0 overruns:0 frame:0 TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
You've received more bits than you sended, so your network card seems to get some stuff from the network ... (sometimes a hardware-near packet sniffer like tcpdump, snort (commandline-tools) or ethereal (X - gui) might show more about the sort of traffic you network card gets and sends - if you know how to use them / read the output ) Hope this helps for further debugging ... Hella -- -- -- -- -- -- hella.breitkopf@varetis.de unix + network administrator
participants (3)
-
Anas Nashif -
Hella Breitkopf -
Steven Boker