Wireless adapter is a USB device using rt2800usb driver. Think the chipset is rt2870 to be exact but not sure.

Forgot to mention I'm indeed using dhcpcd-6.2.x . Used -noipv6rs in /etc/dhcpcd.conf but didn't change. Going to try ipv4only to see what happens. This is a wireless LAN (ipv4 VPN) in a home BTW (for desktop users).

By any chance are you using a firewall on your OS?

1 members found this post helpful.

Try:

and

If you can ping to 8.8.8.8 and not to google.com then is a DNS/dhcp issue. If both pings give you error then investigate firmware issues (or firewall like ReaperX7 said).

1 members found this post helpful.

Most lap tops nowadys include built-in wireless but you've indicated that you're using a plug-in USB wireless device? I would suspect that one may be interfering with the other. Dell lap tops, for example (you haven't said what your equipment is) have a function key that turns the wireless on and off (the key it has a antenna tower with transmitting arcs symbol). Are you sure that the built-in transceiver is off?

A USB wireless device typically has nothing to do with your network card and, most likely, requires software to be able to use it (USB modems do and a USB wireless device is essentially a modem).

So, what is the make and model of your USB device?

What is the make and model of your lap top? Does it have (as most do) built-in wireless?

1 members found this post helpful.

Still haven't solved the problem... For the record, the internet does work but only after issuing dhclient wlan0 (as stated in previous posts).

Think dmesg shows the Problem as . Only trying IPV6 connections. No wonder I don't get automagic internet like I should. Guess because I don't have IPV6 hostname set (only ipv4). Will have to double check why wicd and nm-applet only make an IPV6 connection.

EDIT:
/etc/hosts file had loopback address (127.0.0.1) set to machine name so it was actually set to two host names (localhost and machine name). Changed machine name to something else, rebooted, and internet connected just fine! Now I know what happens when the loopback address is set twice for one local machine.

Going to wait a little bit before I mark this thread as solved. Thanks much for the help!

EDIT:
Yup still works. Seems that was the problem.

EDIT:
Okay actually not... It still happens. Could it be firmware related?

By any means, don't invoke lspci as suggested in two previous posts, so you can still be unsure about the exact chipset.

1 members found this post helpful.

Maybe the power management isn't set correctly and wireless going to sleep. Add this to rc.local and see if it helps

1 members found this post helpful.

lsusb shows my device as I'm marking this thread as solved since using WICD isn't causing problems. Thanks