On Fri, 24 Mar 2006 10:11:18 +1200 Roger Searle wrote: > > > Nick Rout wrote: > > On Wed, March 22, 2006 10:35 pm, Roger Searle wrote: > > > >> Nick Rout wrote: > >> > >>> On Wed, March 22, 2006 9:36 pm, Nick Rout wrote: > >>> > >>> > >>>> On Wed, March 22, 2006 9:32 pm, Roger Searle wrote: > >>>> > >>>> > >>>>> Hi, on my main work machine I have a fresh install of Suse 10 with no > >>>>> connection to the network. I can ping localhost and 127.0.0.1 but not > >>>>> to the router - which is > >>>>> reachable from another machine. > >>>>> > >>>>> I have set (in yast) the network card to obtain an address via dhcp and > >>>>> set the default gateway to be the router (10.1.1.1). I have turned off > >>>>> the > >>>>> firewall. > >>>>> Restarting the network gives: > >>>>> eth0 (DHCP) . . . . no IP address yet.... backgrounding > >>>>> > >>>>> And still can not ping beyond localhost. ping 10.1.1.1 gives "network > >>>>> is unreachable". > >>>>> > >>>>> "/var/log/messages | grep eth0" shows numerous lines of "no IPv6 > >>>>> routers present" and 2 instances of "no link during initialisation" and > >>>>> "link > >>>>> up". > >>>>> > >>>>> What should I look for now? > >>>>> > >>>>> Cheers, > >>>>> Roger > >>>>> > >>>>> > >>>>> > >>>>> > >>>> ifconfig -a > >>>> > >>>> will tell you if the card has been detected at all. > >>>> > >>>> > >> When I'm next at the machine on Friday I could post ifconfig -a. Today > >> I ran it earlier without the -a, it showed output for lo and eth0 - mac > >> address was there, there were a few TX bytes, zero RX bytes. I forget > >> what else... > >> > > > > was there an IP address? > > > > > >>>> is there some support for ipv6 that you included? It can give problems > >>>> if > >>>> you don't have an ipv6 network. > >>>> > >>>> > >> I did not do anything to add support for ipv6. I simply did the > >> install, noted that the network test failed, as did trying to get up a > >> web page and the simple pings. All I did then was go to Yast to look at > >> the network card settings and the firewall as above. > >> > >>>> > >>>> > >>> Oh and by the way your DHCP server should hand out the default gateway - > >>> if it doesn't then get whoever runs it to fix it! > >>> > >>> > >> Yes, it does give out gateway info to the other machines on the > >> network. I specified the gateway after knowing there was no network > >> connectivity in an attempt to get it functioning. > >> > >>> And are you sure the network card still works? I have seen them fried. > >>> > >>> > >> Yes is functioning fine in Windows. > >> > >>> PITA if its a laptop. > >>> > >>> > >> Is a desktop. > >> > >> > >> > > > > ahhh well the card works then. > > > > You could try giving it a network address manually: choose the address it > > had while u were in windows (as this is unlikely to have been given out to > > anyone else in the meantime) > > > > ifconfig eth0 10.1.1.20 up > > route add default gw 10.1.1.1 > > > > then some pinging. > > > > Other things to look for in the logs are the string DHCP (usually in all > > caps). > > > > errrr - you are sure it is plugged in to the cable - believe me it is > > bloody easy to miss! While you are round the back there, are the little > > lights going on and off? Are they going on and off on the network switch? > > > > > OK still no success with this card. The arrival of this email proves > the card is OK (dual booting)... > > NINE:/home/roger # ifconfig eth0 10.1.1.20 up > NINE:/home/roger # route add default gw 10.1.1.1 > NINE:/home/roger # ifconfig eth0 > > eth0 Link encap:Ethernet HWaddr 00:0A:48:1D:B7:5A > inet addr:10.1.1.20 Bcast:10.255.255.255 Mask:255.0.0.0 > inet6 addr: fe80::20a:48ff:fe1d:b75a/64 Scope:Link > UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:72 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:4734 (4.6 Kb) TX bytes:0 (0.0 b) > Interrupt:11 > > NINE:/home/roger # ping 10.1.1.1 > PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data. > From 10.1.1.20: icmp_seq=1 Destination Host Unreachable > > Any ideas? I'm totally lost when it comes to drivers and modules in > linux so no idea what to do from here. > >
its possible that the router has ping responses turned off, it stops some DOS attack. Have you pinged anything else on the network? If there are other linux machines on the lan try pinging to broadcast: ping 10.255.255.255 -b windows machines do not rerspond to broadcast pings though. If you have eth0 then you have a driver - whether it is the right one is another matter I guess. What does lspci and lspci -n say about the card? what does lsmod tell you about the module that is loaded? can you boot with knoppix or similar and see what driver it uses, and if it connects? once again lspci and lsmod are your friends. tcpdump (dunno if it is installed by default on suse) may help. -- Nick Rout <[EMAIL PROTECTED]>
