New wireless on notebook: can ping my network but can't reach internet
 

Hi, all,
Just got SuSE 9.0 installed on my HP Pavilion zt1000 notebook. I'm using a Linksys WPC54G cardbus card. WinXP is set up for dual boot and the wireless workes great on that system. I've got the latest version of Linuxant Driverloader, the latest Linksys driversl, latest firmware for the WAP. Driverloader appears to be loading fine. I can ping my WAP and bring up it's web-based control panel. I can ping other wired and wireless pc's on my network, but I can't reach the net!!! Web addresses simply return the message"unkown host",and I am unable to connect to any web addresses by their true address, eg. 207.68.171.245, and receive the message "Network is unreachable". The network WAP is set at default and so are the features of the card


Any thoughts on what prevents me from reaching the web? thanks!

Same issue. Please help!
 

I'm having the same issue. As a matter of fact, I have the same setup(with the exception of computer make/model). Any help would be greatly appreciated.

I've submitted the question to support@linuxant.com. Their technical specialist is putting some thought into the issue. I'll keep you abreast. Hopefully a member of this board will have some insight, also. Funny thing is, Version 1.35 with a free license worked fine. At that point SuSE had only issued a couple of on-line updates, neither of which affected networking. I've updated to everything they now offer (one of which references wireless), but "no go". I've even tried a clean install with no updates and can't get beyond the WAP.

You've gotten further...
 

You've gotten further than I. I also posted an e-mail with linuxant support, but never received a reply. Thanks for letting me know!

I didn't get any help from their support when I wrote to support@linuxant.com until I sent the mail to their support group. Try subscribing to their support group listed on their site and sending to that address. It would be good for them to hear that it's not just me. They've kind of given up helping me since I can reach my WAP. They think it is my WAP setup, but the same computer using WinXP performs flawlessly. Now here's the real kicker. When I first installed SuSE 9.0, I installed version 1.35 of Driverloader and it worked flawlessly. The only variable was that I had done an online update of SuSE, and two files were updated. Now there are 9 updates and YaST does not indicate which were the first posted, so I cannot replicate my conditions under ver 1.35. I do note that the current YaST updates include some for wireless issues, so perhaps the SuSE updates have fried the Driverloader function??

I've got to be gone until this evening, but I will put together all the suggestions given by Linuxant support and post them here.

Interesting. I just received an e-mail from linuxant support and they tell me that it's probably something with my access point configuration. However, like you, it works flawlessly under WinXP. Glad I kept that wireless ethernet bridge I bought a while back. :)

Still no-go
 

I verified my AP settings as Linuxant suggested, but still cannot connect to the internet.

Well, somehow, after a thousand reintsalls of driverloader, here is what I tried, for one last time,

(1) reflashed the firmware of the WAP, again,
(2) uninstalled driverloader
(3) uninstalled all network devices
(4) powered down
(5) pulled the wireless card out
(6) rebooted and reinstalled the latest version of driverloader using the freshest Windows drivers I could find.
(7) powered down, rebooted, with card inserted
(8) checked dldrconfig and noted that the device listed was eth0, rather than the wlan0 it had been using. I checked YaST and noted that there were THREE cards configured, eth0, eth1, and wlan0.
(9) Upon reboot I noticed that eth1 and wlan0 fail during install. But who cares? It works.

Beats me. If you want, I'll be glad to send or post the various config files, or share the settings that show up in YaST.

Mike

But does the internal nic work?
 

So, after all of that booting and configuration, does the internal nic still work? Re-installed everything this morning with new drivers and still got no further than being able to ping the local network. Bummer.

Followed the steps...
 

So, I followed your steps above to the letter. Interestingly enough, I still only had wlan0 configured when I opened YaST. Also, it worked! Well, it worked until I restarted the laptop. Then it was back to the same old problem. :P

Question: Do you use KWiFiManager?

I had the same problem. I was getting a assigned IP from my wireless ap dhcp server but I was not getting the route information and dns server info. Here is what I did to get it working. I have not found another way to do it.

First go to your wireless config and verify that you are getting your dns server info. If not enter it manually. If you dont know your dns server info and you have a windows box, bring up a dos window and type, ipconfig /all and write down your dns server info. and go back to your linux box and enter it in your wireless settings. You should only have to do this once.

Then bring up a terminal window and go to superuser mode. Then add a route the default route to your gateway "whatever ip it is".

route add default gw "whatever ip it is without quotes"

That is how I got mine to work.

I have to add this route each time I start up. I am a newbie as well. So if anyone can help me how to do this automatically at boot up . Please do so.

Thanks.

Lee

K,
I'm not sure about Lee's solution, but it does seem simple. I can tell you what I think is going wrong with yours. I had fixed it earlier, and I forgot to mention it. Doh. It is most likely that your services are loading in the wrong order, i.e., the network is loading before pcmcia and hotplugging. Well, I'm not sure about the hotplugging, but here is how I fixed it:

Just log in as root, or open the File Manager - Super User, and browse to /etc/rc.d. Two folders will need to be addressed--"rc3.d" and "rc5.d". There you will find services starting with "k" and "s". The "k" items are for shutdown and you can ignore them. Go to the "s" items and simply assign a number to the network service that is higher than the pcmcia (and in my case I did the hotplugging also, but I'm not sure that it is necessary). What I mean to say is simply rename the network file so that the number is higher than the others. That way the netword card will be detected prior to the network and therefore be configured.

My solution is pure newbie luck. Lee's solution is elegant and I wish that I had seen it earlier! At least I wouldn't have this strange situation of 3 cards installed! Thanks, Lee. I WILL be saving it for my next reinstall. I still think that kclaver might end up with the services loading in incorrect order, though, and have to renumber them. Thanks, Lee, for figuring out what the REAL problem is. At least I understand why the fix works, rather than being baffled by my own.

Mike

Your quite welcome. I hope it helps.

I had noticed...
 

Thanks Mike

I had noticed that the services were loading in the wrong order for a while now, but I guessed that the people that set it up that way knew what they were doing. I'll give what you suggested a try and let you know.