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.
for you guys struggling with setting up the wireless oldskool, I suggest using wicd to take care of the wireless stuff. I set up a nice package that takes care of making the changes in rc.inet1.conf and such, so you only need to reboot your computer, and set up your wireless settings in the wicd tray in your selected WM/DE.
Please post your SlackBuild script for that wicd package.
Edit: Otherwise, why would we trust you and install your package,
without knowing how you built it or having any experience with
packages you've built.
Last edited by Bruce Hill; 07-23-2008 at 07:11 PM.
for you guys struggling with setting up the wireless oldskool, I suggest using wicd to take care of the wireless stuff. I set up a nice package that takes care of making the changes in rc.inet1.conf and such, so you only need to reboot your computer, and set up your wireless settings in the wicd tray in your selected WM/DE.
Thanks for the offer, but I really want to know where I've gone wrong - otherwise how will I learn?!
Everything that I modified is done in the post install script mainly makes a backup of rc.inet1.conf so it doesn't scew up wicd's dhcp work with inet1s, and the patches are already taken care of on networking.py to work with dhcpcd. if you need a SlackBuild you can look here where Workman applied the main fix i pointed out. http://rlworkman.net/pkgs/sources/12...icd.SlackBuild Sorry if I caused any issues which where credit is due.
I'm updating slack-desc to make sure original credit goes to the slacky.eu man Again it is my mistake and apologize.
For SlackBuilds, I prefer Alien Bob's. Here's his for wicd.
Looks like I missed out on the 1.5 release, thanks for the link to Bob's, I'll be sure and update. I know the person who wrote it planned on adding support for older dhclient, pump, and dcpcd support to the next major release, so hopefully this does it.
resaguk - is that for the ath5k kernel driver, or the madwifi driver? If you're using -iwlan0, I'll believe you're using the ath5k driver
There's been several notes that -Wext is still having problems with the madwifi driver.
Also, it looks like you have "scan ssid=0" set in the wpa_supplicant.conf file. Since scanning is off for that interface, it looks like it's not looking for the beacon of the AP you're trying to connect to.
Last edited by alisonken1; 07-24-2008 at 06:20 PM.
Reason: Added "scan ssid" paragraph
resaguk - is that for the ath5k kernel driver, or the madwifi driver? If you're using -iwlan0, I'll believe you're using the ath5k driver
None of the above - I'm using windows drivers via ndiswrapper.
Quote:
Originally Posted by alisonken1
Also, it looks like you have "scan ssid=0" set in the wpa_supplicant.conf file. Since scanning is off for that interface, it looks like it's not looking for the beacon of the AP you're trying to connect to.
Ok, this is the output with scanning enabled - I also checked status from another session and did a "/etc/rc.d/rc.inet1 wlan0_start" to try and force things along...
Code:
# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0' (DEPRECATED)
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 14 - start of a new network block
scan_ssid=1 (0x1)
ssid - hexdump_ascii(len=8):
{removed} {removed}
proto: 0x1
mode=0 (0x0)
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK - hexdump(len=32): [REMOVED]
Line: 27 - start of a new network block
key_mgmt: 0x4
priority=0 (0x0)
Priority group 0
id=0 ssid='{removed}'
id=1 ssid=''
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: {removed}
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
ctrl_interface_group=0
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
{removed} {removed}
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
{removed} {removed}
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
RX ctrl_iface - hexdump_ascii(len=6):
53 54 41 54 55 53 STATUS
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
{removed} {removed}
Scan requested (ret=0) - scan timeout 5 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
l2_packet_receive - recvfrom: Network is down
RTM_NEWLINK: operstate=0 ifi_flags=0x1023 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1023 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Scan timeout - try to get results
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
l2_packet_receive - recvfrom: Network is down
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Scan timeout - try to get results
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
{removed} {removed}
Scan requested (ret=0) - scan timeout 5 seconds
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6
I know you're trying a lot, but you're in somewhat of the place I was/am. Two questions, do you have a wired connection on this box (whether you're using it or not doesn't necessarily matter yet)? Have you tried to use wifi on the Linux box while the notepad you mentioned is also connected?
You'll remember I mentioned that I have a WPC100 (Linksys - w/ Atheros 5416). I've built (using Alien Bob's build scripts) the madwifi-current (which has the 5416 support) package and then (re)built and installed the wpa_supplicant package (which has to know about the driver, that's why it's built again).
I have similar results to yours (except for the ndiswrapper stuff) when trying to associate and have come up with the following bizarre behavior (which you should try to duplicate, _really_). If I leave the BSSID enabled on my router, I can connect wirelessly if, and only if, I first boot up with a wired connection, then invoke wpa_supplicant (first I try the non-daemonized method, just to see the output (-dd) and know that it will connect). When I see that it will, I exit the routine and daemonize (-Bw) wpa_supplicant. Once it's connected that way I can run dhcpcd on 'ath0' (wlan0 with the madwifi driver attached) and check the result with iwconfig (there's also hardly a timeout waiting for a prompt after invoking the DHCP client daemon). Once I know I have an address, I take 'eth0' down and use the wifi connection. Clunky, I know, but I haven't had time to tweak rc.inet1 so that it won't time out trying to get an IP addy for eth0 when there's no wired connection.
Also, when I disable BSSID, I have the added wrinkle of having to have another wifi connection up and running in order for wpa_supplicant to locate the AP. I've read that there are problems with non-broadcast SSIDs, but I'm not about to have my router broadcast to the neighborhood that it's up and running.
That's the weirdness I face with wifi, it smells a lot like what you seem to be going through. Since you're still using ndiswrapper, I can't be certain, but you might want to give the above a try. Also, I would strongly urge you to go to Alien Bob's build script site and get the '-current' package build script for madwifi. It has support for the Atheros 5416, and you should then be able to use -Dmadwifi when invoking supplicant.
I know you're trying a lot, but you're in somewhat of the place I was/am. Two questions, do you have a wired connection on this box (whether you're using it or not doesn't necessarily matter yet)? Have you tried to use wifi on the Linux box while the notepad you mentioned is also connected?
Do I have a wired connection for the box? No, unfortunately.
Wifi while connected on notepad? Yes, so far all the times I've been posting here I've had my notepad up and running when I've been trying to get my box to connect.
Quote:
Originally Posted by wheelsg
That's the weirdness I face with wifi, it smells a lot like what you seem to be going through. Since you're still using ndiswrapper, I can't be certain, but you might want to give the above a try. Also, I would strongly urge you to go to Alien Bob's build script site and get the '-current' package build script for madwifi.
But isn't Madwifi for Atheros chipsets? As far as I can tell my wifi card is not Atheros based - I *think* it's Realtek 8185 - but this is from memory and I'm not near my box right now to be able to open it up and physically check. (I definitely tried Realtek's drivers, both Windows and Linux with 12.0 but neither worked, perhaps I'll try them again tomorrow...)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
