• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1316
  • Last Modified:

Linux Wireless on Ubuntu (rausb0)

I'm trying to connect to an access point using a Linksys WUSB54G using Linux (Ubuntu 7.04 amd64)

I downloaded the driver, compiled and installed the driver, following the installation instructions.  The driver is installed successfully and the system recognizes the driver.  The problem is that when I type ifup rausb0, the dhclient attempts to connect, but no DHCPOFFERS are received.

I've ruled out the usual problems:

1. The access point itself is definitely working because a computer 2 feet away running WinXP has no problem connecting.
2. This problem is not related to encryption because the network is unsecure.
3. The access point is being detected.  If I type "iwlist rausb0 scanning" the access point shows up
4. I've correctly configured the /etc/network/interfaces file.  It is configured like:

iface rausb0 inet dhcp
pre-up ifconfig rausb0 up
wireless-essid belkin54g
auto rausb0

So basically everything seems to be in working order - but dhclient gets no DHCPOFFERS.  Any ideas, thoughts, suggestions as to what might be happening here?  Something I overlooked?

  • 2
2 Solutions
I had a whole lot of problems with wireless and Ubuntu.  My solution was to uninstall all network managers and use WICD.

My posts elsewhere here:


I also noticed that moving closer/away from the router/access point can help for some reason.

Good Luck!
Hmm, weird...
I haven't had much trouble with Ubuntu and wireless, with one exception involving an Apple access point. In that case I got the exact same symptoms as you have here.

We have also had a very odd issue with ACER laptops and a HP access point at work; all but ACERs can connect.

My conclusion is that this is beyond normal troubleshooting, unless you can monitor the negotiations that take place before the dhcp failure is manifest and you should try another access point or another client WiFi adapter. It seems some magic is involved.
I didn't see it at first, but the device name suggest an USB- WiFi thingy... Not a good idea and probable cause of the failure. A proper wireless card would likely prove to be working better.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now