Hello fellow penguin lovers.! Have a dual boot xp, suse 11.0 setup. Works awesome but one small problem. Am using Linksys wmp54g v4.1 with a d-link di-624 router for wireless access. made drivers and installed them fine. Configured static ip for card 192.168.0.63, router is 192.168.0.10. I can access my router via wireless but cannot get internet access...what am i missing..? Static ip for card as above...subnet 255.255.255.0, gateway 192.168.0.10, dns 192.168.0.10, same settings as in windoze. Can access router, change settings etc, but no web.....any ideas..? good to be back on LQ..!

i am guessing the problem could be with /etc/resolv.conf or the gateway,
post the output of ifconfig -a and netstat -nr

Can you ping anything outside your network by IP? If so, there's a problem with your DNS.

Otherwise, it might be a routing issue. To check:
- As root, type "route" at the prompt.
- You should see an entry called "default" in the list, with the same interface (IFace) as your wireless device.
- If not, type "route add default 192.168.0.10 <your_wireless_interface>"
- See if you can get out.

If you can access your router, that probably means you're working fine on your end. It sounds like an issue with DNS resolution. Using the network configuration utility in OS11, you should find an option for "resolve DNS via DHCP" or something similar. Check that box, or alternately check your router settings for the nameservers that it is using (there should be two, and they'll be external IPs like 65.333.123.4, not 192.168.X.X). Plug those in to the nameserver fields in the configuration utility, and you should be up and running. (I just did this 5 times this weekend with a bunch of OS11 installs, so I'm going by memory.)

Also, I'm not sure you can use the gateway address as the DNS address, even though you can in Windows. Try using the actual DNS addresses from your router.

if I understand your setup correctly, then
seen from www side
www connects to Linksys wmp54g
your wmp54g connects to dl-624
and your computer to dl-624

hence your route configuration may be faulty

I recently had almost an identical situation

you did NOT write what gateway you have configured in your setting. depending on precise setup of all your boxes/routers it should be the IP of your wmp54g.( NOT the wireless router !)

test by shell command

route add default gw 192.168.x.x

replace th x.x. by the actual IP of your wmp54g
then test your www access / ping a site

also
make sure you have NO OTHER internet access running at the same time ( like another LAN/cable access )
I have sometimes 2 different www access configured and notice that my opensuse can NOT handle mor ethan one at a time. hence if ever you have another network active, you may have to shut that network down

ifconfig

shows what is up

ifconfig eth0 down

would for example DOWN a LAN network to free your PC for wireless access to www

I have internet with dhcp assigned addy, writing this from Suse. But I try and set a static IP and no go. Route at console shows correct info for card, address etc. Looked for dns via dhcp button but is grayed out. I would much rather use static ip's as opposed to dhcp addy. Will try other suggestions shortly..Will post updated info asap.

@hans51: The WMP54G is a wireless adapter. So his connection must be WWW -> Cable/DSL modem -> DL-624 router. Then his computer connects to the router through the wireless WMP54G.

@hippy: You never specified whether or not it works correctly in Windows? If so, it's not a problem with your router/modem/www connection. It will be something in Linux that you need to look at.

The DNS via DHCP option will not be available if you're using a static IP (and, thus, no DHCP info is being sent to you). That's why you'll have to log in to your router's web interface and find the nameservers the router itself is using - those are assigned via DHCP by the ISP. Copy them to the DNS/nameserver fields in your config window and see if that works.

Also, to confirm that this is a DNS problem, you could try to enter a straight external IP address - here's two that work right now for Google.com:

209.85.171.104
72.14.235.104

See if you can get through using those. That circumvents DNS, so you can tell if it's a nameserver issue. Or you could just ping that IP, same idea. If you can't get through using a naked IP like that, it could be another problem altogether.

works fine in windoze....and wonderfully with dhcp assigned addy in suse. It is a linux issue....I just need to read some more..! but dns does sound like the problem. Thanks for the input guys..! Will let you know how I make out.

Gross! Oh, wait . . . sorry, I was thinking of something else. Yeah, let us know how it goes.

Well...tried all suggestions, and nothing so far, so will leave it setup to spit out a dhcp addy. Have to do some more digging around the forum and will hopefully stumble across an answer/idea.

@Silver....I make out just fine dude, one bonus about being a musician. It's one of those "jobs" where you can eat all you want..! Thanx to all for the input people...! Still think it is DNS related... Rock on..!