Unable to get suse 6.2 to connect to internet

qbazic · 05-13-2009, 01:04 AM

I'm running an old emachine 300 mhz with 256 k ram and have installed suse 6.2 on it using a 3com 3c59x/3c90x. It is trying to get to the net using Verizon DSL. I checked lspci and the nic shows up as ethernet controller: 3com Corporation: Unknown device 9200 rev 78. I also run ifconfig running in the promisc mode and get the mac addy and the ip addy and Bcast addy and also the mask addy. It also states that UP BROADCAST RUNNING PROMISC MUTICAST MTU:1500 METRIC:1 I have no RX packets, drops, overuns, or frames. I do have TX packets of 4360 with 0 erorrs 0 drops 0 overuns and a carrier of 4360 there are no collisions and a txqueuelen of 100 interupts are 10 and base addy:0xee00 I try running ping and get the Unknown Host message. I also get the same message with traceroute. Host cmd says can't find host I also ran dhclient and get "No working leases in persistent database-sleeping". When I run the route cmd my 255.255.255.255 destination has a * under gateway and the genmask is same as destination 255.255.etc with the flag UH, 0 Metric, 0 Ref, 0 Use, iface eth0 The ip addy has a gateway * genmask 255.255.255.0 and a U flag rest=0 The loopback is gateway * genmask 255.0.0.0, flag is U and the rest 0's When I ping my IP addy packets are transmitted and recieved and 0 packet loss same for loopback 127.0.0.1. I consider myself a newbie to linux but I can this machine out to the net with live cd's of freebsd, xubuntu, DSL-N, DSL, Puppy and winblows. This older version of Suse 6.2 has got me stumped. I'm sure I've got something configured wrong. I also don't know thw equivalent "ifup" cmd in suse. Any suggestions would be greatly appreciated.

thanks Q

rylan76 · 05-13-2009, 05:37 AM

Have you tried doing

Code:

/sbin/route add default gw 169.254.255.100 netmask 0.0.0.0 eth0

as the last step in the process?

I. e. replace

Code:

169.254.255.100

with the IP of your router / gateway.

Also, have you configured static DNS by entering your preferred DNS server IPs in /etc/resolv.conf?

Here's my resolv.conf for example:

Code:

#options timeout:5
nameserver 169.25.255.3
nameserver 169.25.255.34
nameserver 169.7.147.235
nameserver 169.7.150.34

Or at least, the above two steps (after doing all that you have done) did get me the last bit of the way and I was then able to surf with Linux.