Wireless
in [Slackware]
|
From: Handover Phist on 7 Oct 2009 18:52 Howdy folks! Got some wireless wiggyness here, and it's the first time I've played with wireless in Slack. I've read a few man pages and have come up with the following: in /etc/rc.d/rc.inet1.conf: IFNAME[4]="wlan0" USE_DHCP[4]="yes"DHCP_HOSTNAME[4]="Jason-wireless" WLAN_ESSID[4]="Correct" WLAN_MODE[4]="Managed" WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=Correct" WLAN_WPA[4]="wpa_supplicant" WLAN_WPADRIVER[4]="ralink" WLAN_WPACONF[4]="/etc/wpa_supplicant.conf" in /etc/wpa_supplicant.conf network={ scan_ssid=0 ssid="Correct" proto=WPA key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP WEP104 WEP40 #psk="correct" psk=string_generated_by_wpa_passphrase" } Result: Wed Oct 07 /etc/rc.d $./rc.inet1 wlan0 restart ../rc.inet1: wlan0 information: 'Any ESSID' Error for wireless request "Set Nickname" (8B1C) : SET failed on device wlan0 ; Operation not supported. wlan0 no private ioctls. wlan0 no private ioctls. wlan0 no private ioctls. /usr/sbin/wpa_supplicant: invalid option -- 'w' So it would seem that this wireless dongle cant set an SSID? Would that be what is causing wpa_supplicant to toss an error? Everything seems to be quoted properly and I dont see where it's being called or what the command it's sending is, so what is passing a 'w' option to the command? Hm! -- Look DEEP into the OPENINGS!! Do you see any ELVES or EDSELS ... or a HIGHBALL?? ... www.websterscafe.com
From: Andy on 7 Oct 2009 20:07 Handover Phist wrote: > Howdy folks! Got some wireless wiggyness here, and it's the first time > I've played with wireless in Slack. I've read a few man pages and have > come up with the following: > > in /etc/rc.d/rc.inet1.conf: > > IFNAME[4]="wlan0" > USE_DHCP[4]="yes" > DHCP_HOSTNAME[4]="Jason-wireless" Make sure the above two lines are split. Looks like a problem pasting. > WLAN_ESSID[4]="Correct" You shouldn't need these here: > WLAN_MODE[4]="Managed" > WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set > WPAPSK=Correct" Your post wrapped the following line with the above, make sure it's OK in the file (another join/wrap/paste problem): > WLAN_WPA[4]="wpa_supplicant" > WLAN_WPADRIVER[4]="ralink" Try changing this to WLAN_WPADRIVER[4]="wext". There is no reference to a ralink driver in the wpa_supplicant man page. > WLAN_WPACONF[4]="/etc/wpa_supplicant.conf" I don't have this in my file, but probably OK. > > in /etc/wpa_supplicant.conf > > network={ > scan_ssid=0 > ssid="Correct" > proto=WPA > key_mgmt=WPA-PSK > pairwise=CCMP TKIP > group=CCMP TKIP WEP104 WEP40 You should be able to drop the WEP104 and WEP40 from the group. > #psk="correct" > psk=string_generated_by_wpa_passphrase" > } > > > Result: > > Wed Oct 07 /etc/rc.d $./rc.inet1 wlan0 restart > ./rc.inet1: wlan0 information: 'Any ESSID' > Error for wireless request "Set Nickname" (8B1C) : > SET failed on device wlan0 ; Operation not supported. > wlan0 no private ioctls. > > wlan0 no private ioctls. > > wlan0 no private ioctls. > > /usr/sbin/wpa_supplicant: invalid option -- 'w' > > So it would seem that this wireless dongle cant set an SSID? Would that > be what is causing wpa_supplicant to toss an error? Everything seems to > be quoted properly and I dont see where it's being called or what the > command it's sending is, so what is passing a 'w' option to the > command? Hm! > This is how I have it set up on my home box. For my laptop I use wicd from the extra directory. Andy Johnson Luling, Louisiana
From: Handover Phist on 7 Oct 2009 21:41 Andy : > Handover Phist wrote: > >> Howdy folks! Got some wireless wiggyness here, and it's the first time >> I've played with wireless in Slack. I've read a few man pages and have >> come up with the following: >> >> in /etc/rc.d/rc.inet1.conf: >> >> IFNAME[4]="wlan0" >> USE_DHCP[4]="yes" >> DHCP_HOSTNAME[4]="Jason-wireless" > > Make sure the above two lines are split. Looks like a problem pasting. They're split properly. There are lines in between those that are commented out. >> WLAN_ESSID[4]="Correct" > > You shouldn't need these here: > >> WLAN_MODE[4]="Managed" >> WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set >> WPAPSK=Correct" I dont need the passkey? I can understand the rest. > Your post wrapped the following line with the above, make sure it's OK in > the file (another join/wrap/paste problem): > >> WLAN_WPA[4]="wpa_supplicant" > >> WLAN_WPADRIVER[4]="ralink" All good. > Try changing this to WLAN_WPADRIVER[4]="wext". There is no reference to a > ralink driver in the wpa_supplicant man page. I did try that at one point. Wed Oct 07 /etc/rc.d $lsusb Bus 001 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter Wed Oct 07 /etc/rc.d $wpa_supplicant -h drivers: wext = Linux wireless extensions (generic) nl80211 = Linux nl80211/cfg80211 hostap = Host AP driver (Intersil Prism2/2.5/3) atmel = ATMEL AT76C5XXx (USB, PCMCIA) ndiswrapper = Linux ndiswrapper ipw = Intel ipw2100/2200 driver (old; use wext with Linux 2.6.13 or newer) wired = wpa_supplicant wired Ethernet driver ralink = Ralink Wireless Client driver OK, there's some snippage there, but the adapter is a Ralink sorta thing, and wpa_supplicant, in the rear, tossed a ralink driver. Seems pretty cricket, but I'm know to be wrong occasionally. >> WLAN_WPACONF[4]="/etc/wpa_supplicant.conf" > > I don't have this in my file, but probably OK. > I'm thinking that that may be producing errors. Why throw the options twice? >> >> in /etc/wpa_supplicant.conf >> >> network={ >> scan_ssid=0 >> ssid="Correct" >> proto=WPA >> key_mgmt=WPA-PSK >> pairwise=CCMP TKIP >> group=CCMP TKIP WEP104 WEP40 > > You should be able to drop the WEP104 and WEP40 from the group. OK. Will try. -- NATURE IS PISSED www.websterscafe.com
From: Andy on 8 Oct 2009 00:55 Handover Phist wrote: > Andy : >> Handover Phist wrote: >> >>> Howdy folks! Got some wireless wiggyness here, and it's the first time >>> I've played with wireless in Slack. I've read a few man pages and have >>> come up with the following: >>> >>> in /etc/rc.d/rc.inet1.conf: >>> >>> IFNAME[4]="wlan0" >>> USE_DHCP[4]="yes" >>> DHCP_HOSTNAME[4]="Jason-wireless" >> >> Make sure the above two lines are split. Looks like a problem pasting. > > They're split properly. There are lines in between those that are > commented out. > >>> WLAN_ESSID[4]="Correct" >> >> You shouldn't need these here: >> >>> WLAN_MODE[4]="Managed" >>> WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set >>> WPAPSK=Correct" > > I dont need the passkey? I can understand the rest. It might be easier to think of wpa_supplicant handling the link layer and rc.inet.conf as handling the transport layer. Even if we weren't using IP, we would still need to have all the settings in wpa_supplicant.conf to set up the link. Don't define stuff twice if you don't have to. It's probably the source of your "w" error, since rc.inet is trying to pass this stuff to wpa_supplicant. This is all I have in my rc.inet1.conf: GATEWAY="192.168.1.1" DEBUG_ETH_UP="no" IFNAME[4]="wlan0" IPADDR[4]="192.168.1.3" NETMASK[4]="255.255.255.0" USE_DHCP[4]="no" WLAN_ESSID[4]="myrouternamehere" WLAN_WPA[4]="wpa_supplicant" WLAN_WPADRIVER[4]="wext" >> Your post wrapped the following line with the above, make sure it's OK in >> the file (another join/wrap/paste problem): >> >>> WLAN_WPA[4]="wpa_supplicant" >> >>> WLAN_WPADRIVER[4]="ralink" > > All good. > >> Try changing this to WLAN_WPADRIVER[4]="wext". There is no reference to >> a ralink driver in the wpa_supplicant man page. > > I did try that at one point. It might be that the ralink is somehow special, in which case you'd just have to keep experimenting. Since I have a Broadcom card, I can't help but think that any other card would have to be easier. The bitterness of low quality remains long after the sweetness of the low price is gone. > Wed Oct 07 /etc/rc.d $lsusb > Bus 001 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501USB > Wireless Adapter > > > Wed Oct 07 /etc/rc.d $wpa_supplicant -h > drivers: > wext = Linux wireless extensions (generic) > nl80211 = Linux nl80211/cfg80211 > hostap = Host AP driver (Intersil Prism2/2.5/3) > atmel = ATMEL AT76C5XXx (USB, PCMCIA) > ndiswrapper = Linux ndiswrapper > ipw = Intel ipw2100/2200 driver (old; use wext with Linux 2.6.13 or > newer) > wired = wpa_supplicant wired Ethernet driver > ralink = Ralink Wireless Client driver Well, the man page doesn't match the program. Who'da thunk it? > > > OK, there's some snippage there, but the adapter is a Ralink sorta > thing, and wpa_supplicant, in the rear, tossed a ralink driver. Seems > pretty cricket, but I'm know to be wrong occasionally. > > >>> WLAN_WPACONF[4]="/etc/wpa_supplicant.conf" >> >> I don't have this in my file, but probably OK. >> > > I'm thinking that that may be producing errors. Why throw the options > twice? > > >>> >>> in /etc/wpa_supplicant.conf >>> >>> network={ >>> scan_ssid=0 >>> ssid="Correct" >>> proto=WPA Maybe change to proto=RSN WPA to add wpa2 support. >>> key_mgmt=WPA-PSK >>> pairwise=CCMP TKIP >>> group=CCMP TKIP WEP104 WEP40 >> >> You should be able to drop the WEP104 and WEP40 from the group. > > OK. Will try. > Also, does this card work without wpa_supplicant on an open network? Sorry, but I have to ask. Andy
From: Handover Phist on 8 Oct 2009 10:50 Andy : > Handover Phist wrote: >> > > Also, does this card work without wpa_supplicant on an open network? Sorry, > but I have to ask. > > Andy Thanks for your help Andy. After setting up all the options in what looked to be the right fashion, I went through /etc/rc.d/rc.wireless. This is the file that calls wpa_supplicant. I found the lines: echo "$0: wpa_supplicant -Bw -c${WPACONF} ${WPA_OPTIONS} -i$INTERFACE" | $LOGGER ${SUPPATH}/wpa_supplicant -Bw -c${WPACONF} ${WPA_OPTIONS} -i$INTERFACE and removed the w option being passed to wpa_supplicant. Badabing! Everything now works peachy. Is this a problem on anyone elses boxen? After all, your wireless is working, are you using Slack 13.0? -- Linux! Guerrilla UNIX Development Venimus, Vidimus, Dolavimus. -- Mark A. Horton KA4YBR, mah(a)ka4ybr.com www.websterscafe.com
|
Next
|
Last
Pages: 1 2 Prev: Audacious - libmp3lame Next: What will Slack 13 give me that Slack 11 doesn't have? |