linux: Network=yes Internet=no

[UKMuFFiN]

Hey guys,

Just a quickie, using suse 10.1 32bit and a Buffalo WLI2-PCI-54G(S)

Installed the drivers ok with ndiswrapper and it kinda works as in i can 'see' and get into windows shared folders on the network, and i can log onto the router. However, I cant get onto the Internet(?) whats up with that?

I reset the router to default settings with no encryption and it still doesnt work, any quick ideas? If you want more info I'll try and get my 'ifstatus wlan0' and 'iwconfig' results up when i get home but basically they say, im connected to the router, encryption is off and theres a good signal.

Cheers.

[directhex]

try "ping 72.14.207.99"

if that works, your /etc/resolv.conf file doesn't have correct DNS servers in it (for some reason)

[UKMuFFiN]

ok, would pinging 'google.com' test for the same thing? I tried that and it couldn't get anything. Are you saying i need to change my resolv.conf file? should the DNS addresses be my router (192.168.0.1)?

Cheers

[directhex]

ok, would pinging 'google.com' test for the same thing? I tried that and it couldn't get anything. Are you saying i need to change my resolv.conf file? should the DNS addresses be my router (192.168.0.1)?

Cheers

pinging google.com forces your machine to look for an IP address to match up to google.com, then pings that IP after a successful lookup. on a standard linux system, it first looks in /etc/hosts for machine name mappings, then asks each DNS server in turn specified in /etc/resolv.conf

if you have a working internet connection but no valid DNS entries, then pinging an external, internet-based IP like 72.14.207.99 will work, but "google.com" will not. i suspect this is the case, but can't be sure until you test it.

if it is indeed a resolv.conf issue, then the actual problem might be caused either by your router not sending complete information with its DHCP leases, or your client system not writing resolv.conf with valid data when it should. either way, i suspect you're right, in that "nameserver 192.168.0.1" should be a valid resolv.conf - but check that this is the problem first by pinging an external IP address

[mike_w]

I personally find it rather annoying that my router doesn't work with Linux. Rather than using DHCP, and the router as the nameserver, I have to set the nameserver myself. Otherwise, I can't do anything with apt, or FTP. That's with a D-Link. It could be that your router is the same, although pinging an IP will find out for sure, as said.

[UKMuFFiN]

cheers directhex, once again you have shown your great wisdom of all things linux
after a lot of playing all it needed was the "nameserver 192.168.0.1" you suggested.
Top man.

Mike> I thought the D-link routers used opensource firmware and so were linux friendly? or was that linksys? Anyway, im using a netgear WG84M iirc and its working fine now!


out.