SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Linux tmkd 2.6.29.6-smp #2 SMP Mon Aug 17 00:52:54 CDT 2009 i686 Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz GenuineIntel GNU/Linux
I try to connect to some AP via wpa_supplicant. But i see this errors. Can you help?
Code:
TERMINAL
bash-3.1# wpa_supplicant -D wext -i wlan0 -c wpa_supplicant.conf
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:1e:4a:33:0f:21 (SSID='eduroam' freq=2452 MHz)
Associated with 00:1e:4a:33:0f:21
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWENCODEEXT]: No such file or directory
^CCTRL-EVENT-TERMINATING - signal 2 received
/var/log/messges
Jan 5 17:23:52 tmkd kernel: Registered led device: iwl-phy0:radio
Jan 5 17:23:52 tmkd kernel: Registered led device: iwl-phy0:assoc
Jan 5 17:23:52 tmkd kernel: Registered led device: iwl-phy0:RX
Jan 5 17:23:52 tmkd kernel: Registered led device: iwl-phy0:TX
Jan 5 17:23:52 tmkd vmnetBridge: Adding interface wlan0 index:4
Jan 5 17:23:52 tmkd kernel: bridge-wlan0: is a Wireless Adapter
Jan 5 17:23:52 tmkd kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan
5 17:23:52 tmkd vmnetBridge: Started bridge wlan0 to virtual network 0.
Jan 5 17:23:52 tmkd vmnetBridge: Removing interface wlan0 index:4
Jan 5 17:23:52 tmkd vmnetBridge: Stopped bridge wlan0 to virtual network 0.
Jan 5 17:23:53 tmkd kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 5 17:25:50 tmkd vmnetBridge: Adding interface wlan0 index:4
Jan 5 17:25:50 tmkd kernel: bridge-wlan0: is a Wireless Adapter
Jan 5 17:25:50 tmkd vmnetBridge: Started bridge wlan0 to virtual network 0.
Jan 5 17:25:50 tmkd vmnetBridge: Removing interface wlan0 index:4
Jan 5 17:25:50 tmkd kernel: iwlagn 0000:02:00.0: PCI INT A disabled
Jan 5 17:25:50 tmkd vmnetBridge: Stopped bridge wlan0 to virtual network 0.
^C
/var/log/syslog
Jan 5 16:55:04 tmkd nmbd[3826]: *****
Jan 5 16:55:04 tmkd nmbd[3826]: [2011/01/05 16:55:04, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(395)
Jan 5 16:55:04 tmkd nmbd[3826]: *****
Jan 5 16:55:04 tmkd nmbd[3826]:
Jan 5 16:55:04 tmkd nmbd[3826]: Samba name server TMKD is now a local master browser for workgroup DOM on subnet 172.16.73.1
Jan 5 16:55:04 tmkd nmbd[3826]:
Jan 5 16:55:04 tmkd nmbd[3826]: *****
Jan 5 16:55:41 tmkd kernel: iwlagn: Error sending REPLY_ADD_STA: time out after 500ms.
Jan 5 16:59:09 tmkd dhcpcd[3612]: wlan0: sendto: Network is down
Jan 5 16:59:09 tmkd dhcpcd[3612]: wlan0: poll: Network is down
This doesn't help in anything.(only runs dhcp). I think that problem is with key. Today i saw key errors, but i did not save it. Tomorrow i will try one more time, and post result.
execute iwconfig, then the wpa_supplicant command (from your post #3), and afterwards iwconfig again. iwconfig will show you if you're authenticated to the accesspoint or not.
Please list the output of the commands "lspci -v", "ifconfig -a" and "iwconfig".
It looks like you are also running VMware and VMware is trying to bridge its virtual network to the wireless adapter.
In general it is not possible to add a wireless interface to a bridge.
As stated in earlier threads there are a few things you may need to determine where the problem exactly is.
(you may try to browse linux questions to see whether or not your problem is or could be in any way related to the issues other people have had)
Things that are handy to know up-front:
1) name of your wireless router (this is something you configured yourself most likely)
2) type of security (wpa, wpa2, wep (yuck), etc)
3) security information (preshared key etc)
4) Frequencies (2.5GHz, 5.1GHz, ...)
- Assuming you run KDE on the machine that you try to connect to your wireless router, go to Internet -> wpa_gui (you need your root password as it is kdesu-ed)
- Of note here is: do you see your wlan0 adapter in the list of Adapters. If not: you may not have loaded the correct libraries to use your wireless adapter
- If the adapter is visible, you can go to the second tab and scan for networks. Do you see any access points at all? If not: check which frequencies are supported with your wireless adapter, I've had issues here in the past. Set the right frequency in /etc/rc.d/rc.wireless.conf)
- If you do see your access point: congratulations!
- Try to connect to your accesspoint: click "Add" fill in the fields with the correct connection information (which I made you note earlier)
Please provide as full information as (securely) possible back on issues that you encounter along this road.
Please list the output of the commands "lspci -v", "ifconfig -a" and "iwconfig".
It looks like you are also running VMware and VMware is trying to bridge its virtual network to the wireless adapter.
In general it is not possible to add a wireless interface to a bridge.
Eric
wpa_supplicant is not running, which is why you cannot get a status from it.
Nobody has been stating that your card is faulty here, getting it to work on your Linux is another story.
Go with Alien Bob's request to show the listings. If iwconfig shows wlan0, you can try to start wpa_supplicant manually.
If it doesn't, the right modules for your wireless adapter have not been loaded. You could provide us with
You will need a file /etc/wpa_supplicant.conf for it, with at least the "Plaintext connection" part active:
Also, as stated by Alien Bob: you seem to be running vmware (player); The messages about wlan0 seem (all) to come from vmware, making me believe that your wlan0 adapter is not available at the point the vmware modules are loaded.
If you do not have the "plaintext" connection in wpa_supplicant, it will probably only connect to the access points that you have already configured; If somehow you do not have the correct credentials entered for this access point, you won't be able to connect either.
02:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
Subsystem: Intel Corporation Device 1211
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at de200000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-21-5d-ff-ff-11-d2-f6
Kernel driver in use: iwlagn
Kernel modules: iwlagn
Seems to be your wireless card from lspci
The accesspoint you try to connect to, is it listed in your wpa_supplicant.conf?
What is the authentication mechanism? WPA2 PSK, WPA2 Enterprise (EAP), ...
What is the type of encryption? (TKIP or CCMP or ...)
What is the EAP method (if applicable)
I expect your wpa_supplicant.conf has to be edited to make it work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.