Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK, that was a nice bit of work on your part and you're right, it is looking good. Right now the things to check are:
lsmod - make sure bcm43xx is NOT loaded, and if it is unload it(modprobe -r bcm43xx). If you have both ndiswrapper and bcm43xx loaded at the same time, you've got trouble.
iwconfig - check that your configurations have taken. Are you using either WEP or WPA encryption?
ifconfig - see if you've gotten and IP address.
Post the outputs of any of those if you've got questions.
lsmod - make sure bcm43xx is NOT loaded, and if it is unload it(modprobe -r bcm43xx). If you have both ndiswrapper and bcm43xx loaded at the same time, you've got trouble.
That is very good. What is extremely unfortunate however is that lsmod also shows no signs of ndiswrapper. Are you loading the module (moprobe ndiswrapper)? Not having ndiswrapper loaded would also explain your lack of a wireless device in the iwconfig output.
So the gaps in my knowledge are beginning to show now I'm not sure how I would load the module. Would I have to enter that command every time or where would I enter it to load itself on boot?
You will have to load ndiswrapper each time you boot, but lets see if we can get it working before we worry about loading it on boot. The command to load it is (you need to be root):
modprobe ndiswrapper
Modprobe only complains if there is an error, so if you just get a command line back, that is a good thing. You can also check lsmod and see if ndiswrapper is loaded. Once it was loaded, you should see a new wireless interface in iwconfig.
This Broadcomm cards are very tricky cards and its a pain to get them to work on Ubuntu. Once you install your ndiswrapper, try these steps:
ndiswrapper -l (Lists all the drivers present)
ndiswrapper -i bcmwl5.inf (This installs the wireless driver)
ndiswrapper -l (You should see ur driver now)
ndiswrapper -m (This is required to start ndiswrapper everytime on startup)
modprobe ndiswrapper (This starts the ndiswrapper module).
Then you have to do some blacklisting stuff in Ubuntu,which im not aware of. I use Mandriva Spring and its a cake walk to configure wireless and other hardware there. Not really sure of how to go about to configure in Ubuntu,once ndiswrapper is loaded.
I beg to disagree, there is joy because now iwconfig shows a functional wireless device (eth1). The only thing left to do is configure it and request an IP address.
So set your SSID with the command iwconfig eth1 essid YourSSID
If you're using a WEP key, you set that:
iwconfig eth1 key YourWEPKeyInHex (if you look at the iwconfig man page, there are also ways of entering the text key if that is what you have).
If you're using WPA encryption, we'll have to work on getting wpa_supplicant to run. In either case (WEP or WPA) you might want turn it off at the router temporarily just to see if the driver is working.
Once you've gotten the SSID entered (and a key if needed) you should see a MAC address appear in the Access Point field of your iwconfig output. That means you've successfully associated with the AP, and all that you need to do is request an IP address. I'm pretty sure Ubuntu uses the ifup command, so try:
ifup eth1
If that is successful, you should see an IP address assigned to eth1 in the ifconfig output and you should be good to go. By the way, both the iwconfig and ifup commands need to be run as root.
looking better! Still no wireless connection though ifup eth1 says
ifup: interface eth1 already configured
No wireless connection listed in the router either.
Heres the routers status page info (refreshed).
Code:
The router is connected to the Internet.
Click the Refresh button at the bottom of the page to display the latest values.
Device
Name: U.S. Robotics Wireless MAXg Router (USR5461)
Firmware: 3.91.37.0.2 (Mar 11 2005)
Boot loader: CFE 3.91.37.0.1
Printer status: Not Ready
Printer location: http://192.168.2.1:1631/printers/My_Printer
Security
Method: None
Encryption: TKIP and AES
Pass phrase: (removed)
Key: (removed)
RADIUS server:
RADIUS port: 1812
RADIUS key:
Wireless MAC filter: Disabled
Wireless
Network name: fortress
Broadcast name: Enabled
MAC address: 00:C0:49:F0:EE:0A
Mode: Access Point
WDS restrictions: Disabled
WAN
Protocol: DHCP
MAC address: 00:C0:49:F0:EE:0B
IP address: 75.70.37.83
Subnet mask: 255.255.248.0
Gateway: 75.70.32.1
DNS server 1: 68.87.85.98
DNS server 2: 68.87.69.146
Lease expires: 40 minutes, 20 seconds
LAN
IP address: 192.168.2.1
Subnet mask: 255.255.255.0
MAC address: 00:C0:49:F0:EE:0B
Clients
Type Name MAC Address IP Address Expiration
wired ubuntu 00:16:D4:39:03:9C 192.168.2.2 55 minutes, 27 seconds
wired Slim 00:16:E3:95:E1:1D 192.168.2.3 21 minutes, 4 seconds
wired doodar 00:14:A5:BD:00:60 192.168.2.4 Expired
Have been googling and tried a few things but not sure if this was the case before but I can connect to my router wirelessly!! I think it was the command
sudo dhclient
that worked.
This is a major step but I still can't connect to the internet wirelessly so it has to be a configuration thing now?
I have a wireless connection to my router (fortress) in System>admin>network
I'd really like to be able to simply boot up and connect wirelessly with wpa and without having to open a terminal every time. Do you think this is going to be possible?
so here's some outputs to let you know whats going on.
Code:
simon@ubuntu:/$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:D4:39:03:9C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:23732 errors:0 dropped:0 overruns:0 frame:0
TX packets:18121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:26336204 (25.1 MiB) TX bytes:1877182 (1.7 MiB)
Interrupt:21 Base address:0x400
eth1 Link encap:Ethernet HWaddr 00:14:A5:BD:00:60
inet addr:192.168.2.4 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::214:a5ff:febd:60/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1678 errors:0 dropped:0 overruns:0 frame:0
TX packets:1646 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:799809 (781.0 KiB) TX bytes:149662 (146.1 KiB)
Interrupt:22 Memory:c0204000-c0206000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:140 errors:0 dropped:0 overruns:0 frame:0
TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12804 (12.5 KiB) TX bytes:12804 (12.5 KiB)
simon@ubuntu:/$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"fortress"
Mode:Managed Frequency:2.462 GHz Access Point: 00:C0:49:F0:EE:0A
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
simon@ubuntu:/$
Congrats! I'm hoping that you've been able to recreate your wireless setup. As far as WPA goes, you'll need to install and run wpa_supplicant. I've got some instructions on doing that on my help site as well as examples of how the configuration needs to look. The good news is that wpa_supplicant will take over the configuration duties, so you'll just need to start it and then if all goes well, request an IP address.
If you hang in there with the console until you get WPA sorted out, it should be easy to either get whatever GUI monstrosity Ubuntu uses for configuring wireless cards or to write a brief script that runs at boot time.
Not sure if it worth sarting a new thread here but I hope someone can help.
It's been a while since posting in this thread because Wubi developed a problem so I've installed edgy (then upgraded to fiesty) to a partition and following this thread I'm back to where is was.
Using ndiswrapper I have a wireless light and can connect wirelessly if I disable security on the router.
I would like to have WPA and WPA2 enabled at the router
simon@simon-laptop:~$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 5485
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:16:d4:39:03:9c
Sending on LPF/eth0/00:16:d4:39:03:9c
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.eth1.pid with pid 5417
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:14:a5:bd:00:60
Sending on LPF/eth1/00:14:a5:bd:00:60
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 6847440
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:16:d4:39:03:9c
Sending on LPF/eth0/00:16:d4:39:03:9c
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.6 -- renewal in 1433 seconds.
Error for wireless request "Set Encode" (8B2A) :
invalid argument "hTvHAivbq1uj2KdPkPWTnHnl8bgTNUdk".
There is already a pid file /var/run/dhclient.eth1.pid with pid 6847440
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:14:a5:bd:00:60
Sending on LPF/eth1/00:14:a5:bd:00:60
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
eth2: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth2.pid with pid 6847440
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.pid with pid 6847440
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
wlan0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6847440
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.
[ OK ]
simon@simon-laptop:~$
You'll need to refresh my memory on how you're starting wpa_supplicant. It looks like it is getting started, but any flags you use might give a clue.
Quote:
Listening on LPF/eth0/00:16:d4:39:03:9c
Sending on LPF/eth0/00:16:d4:39:03:9c
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.6 -- renewal in 1433 seconds.
Error for wireless request "Set Encode" (8B2A) :
invalid argument "hTvHAivbq1uj2KdPkPWTnHnl8bgTNUdk".
There is already a pid file /var/run/dhclient.eth1.pid with pid 6847440
This little exchange is kind of interesting in that it looks to me like DHCP is working, at least for eth0. You might want to double check your settings because one possible interpretation of this is that wpa_supplicant is trying to set a wireless key on eth0, which it obviously can't since eth1 is the wireless card.
It also looks as if it is barfing on the various .pid files. You might try removing them and then starting your network services.
Also, is your WPA key really that long? I don't know if there is a length limit for passphrases, but that does seem a touch overdone.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I'm not sure how I would load the module. Would I have to enter that command every time or where would I enter it to load itself on boot?
