No Internet But Wlan0 Connected
 

Hello i used Ndiswrapper to install my broadcom card and its up running and conected to my Netgear router, i can login to 192.168.0.1 (router admin) fine but i cannot access any webpage or ping google.com. I have set all services to allow in the firewall options as well as turning it off. On boot i watched the services load and after it loaded wlan0 i got the following error RTNETLINK answers :invalid argument. I have stoped eth0 booting and i still have this problem?

I am currently using FC4 on my Acer Aspire 3003lmi can any one point me in the right direction.

-Trev

did you add the router as default gateway? `route add default gw 192.168.0.1`

How exactly did you connect? Does your internet work through a standard ethernet card or another os? Is your netgear router set up to act as a dhcp server? are you configuring wlan0 to use dhcp or static IP? how many of the following commands did you execute?
iwconfig wlan0 essid <ESSID>
iwconfig wlan0 mode <MODE
iwconfig wlan0 key <TYPE> <KEY>
dhclient wlan0
ifconfig wlan0 up

If all that is correct, have you had any power outages on anything or disconnects on anything? When my broadband modem goes out, I typically have to disconnect the power on my router, bring the modem back up, and then bring the router up. Does your modem or router have an option to block outside internet that accidentally got activated? does your modem have a "sleep" button that accidentally got pushed? The biggest "can't connect to the internet" culprit I've seen in the broadband world is the motorola modem's "sleep" button.

If you're using cable modem and the sleep button isn't the issue, try turning all equipment off. unscrew the cable from the modem, unplug it, disconnect and reconnect all ethernet cables, screw the cable back in, plug the power back in, after it comes back up, power up the router again, power up the machines, run whatever scripts you have to connect the wireless to the router and try that.

With out knowing your setup and what's been tested on another machine or os to make sure it's working, there could be a ton of non-linux related issues affecting it. If this is your only machine and if it's only Linux it would be hard to tell whether or not it's some of the junk I've mentioned.

Hope some of this helps you some how.

Do you have your nameserver in /etc/resolv.conf?