Problem with WIFI AP mode

This forum is for all other ARMv5 devices

Problem with WIFI AP mode

Postby baoyingcheng » Tue Nov 20, 2012 3:51 pm

Can anyone use a usb wifi stick with pogoplug?
I read many articles and tried a whole week, and still can't get it work.
I'm using p54usb wifi stick and works fine as a client.
here are some discussions about this:
viewtopic.php?f=6&t=247
I follow the instructions ,install hostapd,dnsmasq,and config them.
when I reboot ,it seems everything work fine,but I can only connect to the ap once, after about 1 minute,the ap can't be connected any more.
here is the debug information:
$this->bbcode_second_pass_code('', '[root@alarm ~]# hostapd -dd /etc/hostapd/hostapd.conf
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
Could not open file /sys/class/net/wlan0/phy80211/name: No such file or directory
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
nl80211: Register frame match - hexdump(len=2): 08 01
nl80211: Failed to register Action frame processing - ignore for now
nl80211: Add own interface ifindex 4
nl80211: Set mode ifindex 4 iftype 3 (AP)
nl80211: Create interface iftype 6 (MONITOR)
nl80211: New interface mon.wlan0 created: ifindex=7
nl80211: Add own interface ifindex 7
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz
nl80211: 2457-2482 @ 20 MHz
nl80211: 2474-2494 @ 20 MHz
nl80211: 5170-5250 @ 40 MHz
nl80211: 5735-5835 @ 40 MHz
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
Completing interface initialization
Mode: IEEE 802.11g Channel: 10 Frequency: 2457 MHz
nl80211: Set freq 2457 (ht_enabled=0 sec_channel_offset=0)
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x1
RATE[3] rate=110 flags=0x1
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
Flushing old station entries
Deauthenticate all stations
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
Using interface wlan0 with hwaddr 00:0b:6b:9b:4b:c8 and ssid 'cheng'
nl80211: Set beacon (beacon_set=0)
wpa_driver_nl80211_set_operstate: operstate 0->1 (UP)
netlink: Operstate: linkmode=-1, operstate=6
wlan0: Setup of interface done.
random: Got 20/20 bytes from /dev/random
nl80211: Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface mon.wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface mon.wlan0 is up
nl80211: Ignore event for foreign ifindex 3
nl80211: Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'mon.wlan0' added
Unknown event 5
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
netlink: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared -')

but if I connect again after that, it shows:
$this->bbcode_second_pass_code('', 'Add randomness: count=173 entropy=172
Add randomness: count=174 entropy=173
Add randomness: count=175 entropy=174
mgmt::auth
authentication: STA=94:63:d1:a8:fb:bf auth_alg=0 auth_transaction=1 status_code=0 wep=0
wlan0: STA 94:63:d1:a8:fb:bf IEEE 802.11: authentication OK (open system)
wlan0: STA 94:63:d1:a8:fb:bf MLME: MLME-AUTHENTICATE.indication(94:63:d1:a8:fb:bf, OPEN_SYSTEM)
wlan0: STA 94:63:d1:a8:fb:bf MLME: MLME-DELETEKEYS.request(94:63:d1:a8:fb:bf)
authentication reply: STA=94:63:d1:a8:fb:bf auth_alg=0 auth_transaction=2 resp=0 (IE len=0)
Add randomness: count=176 entropy=175
mgmt::auth
authentication: STA=94:63:d1:a8:fb:bf auth_alg=0 auth_transaction=1 status_code=0 wep=0
wlan0: STA 94:63:d1:a8:fb:bf IEEE 802.11: authentication OK (open system)
wlan0: STA 94:63:d1:a8:fb:bf MLME: MLME-AUTHENTICATE.indication(94:63:d1:a8:fb:bf, OPEN_SYSTEM)
wlan0: STA 94:63:d1:a8:fb:bf MLME: MLME-DELETEKEYS.request(94:63:d1:a8:fb:bf)
authentication reply: STA=94:63:d1:a8:fb:bf auth_alg=0 auth_transaction=2 resp=0 (IE len=0)
Add randomness: count=177 entropy=176
mgmt::auth
authentication: STA=94:63:d1:a8:fb:bf auth_alg=0 auth_transaction=1 status_code=0 wep=0
wlan0: STA 94:63:d1:a8:fb:bf IEEE 802.11: authentication OK (open system)
wlan0: STA 94:63:d1:a8:fb:bf MLME: MLME-AUTHENTICATE.indication(94:63:d1:a8:fb:bf, OPEN_SYSTEM)
wlan0: STA 94:63:d1:a8:fb:bf MLME: MLME-DELETEKEYS.request(94:63:d1:a8:fb:bf)
authentication reply: STA=94:63:d1:a8:fb:bf auth_alg=0 auth_transaction=2 resp=0 (IE len=0)
Add randomness: count=178 entropy=177
')
and the client shows endless tring...
I guess the problem is in line 2:Could not open file /sys/class/net/wlan0/phy80211/name: No such file or directory
and I googled it,some guys had the same question, but nobody answered.
here is an article talked about this,it seems some issues with the wifi hardware,but I'm not sure:
http://comments.gmane.org/gmane.linux.k ... eral/84192
~~~~~~~~~~~~~~~~~~~~~~~~
I really need this working, coz I don't have a router,I'm now using an ADSL directly.I want my pogoplug works as a router and a web server.
google says a guy installed openwrt and a usb wifi adapter on pogoplug works,thought it should work with archlinux
baoyingcheng
 
Posts: 8
Joined: Wed Oct 17, 2012 1:22 pm

Re: Problem with WIFI AP mode

Postby WarheadsSE » Tue Nov 20, 2012 4:07 pm

1) not all pogoplugs are the same device.
2) verify which kernel version he was running, because that really matters.
3) drivers could be different!
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Problem with WIFI AP mode

Postby pepedog » Tue Nov 20, 2012 4:13 pm

I don't have one of your type of pogoplug, but think you have an old kernel. Check with uname -a
Make sure you have the right firmware. http://wireless.kernel.org/en/users/Drivers/p54
Check dmesg for this
Maybe try this guide https://wiki.archlinux.org/index.php/So ... cess_Point
If you can, kernel version permitting, try bridge mode first
Most common trap is password has to be at least 8 characters
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Problem with WIFI AP mode

Postby baoyingcheng » Wed Nov 21, 2012 2:16 am

1.driver is right,because I can use the wifi adapter as a client
2.firmware is right too,I've been checking on these for at least 10 times
3.I followed the exact instruction -https://wiki.archlinux.org/index.php/Software_Access_Point
4.the problem is not stable,only work for a few minutes. If I'm using a wrong configuration or driver or firmware, it won't work at all.I've tried that before.

I don't know where the problem is,I guess it's line 2:Could not open file /sys/class/net/wlan0/phy80211/name: No such file or directory.I looked into other device,cat /sys/class/net/wlan0/phy80211/name shows "phy0",but on pogo B01 /sys/class/net/wlan0/phy80211/ there are some files,but no file called "name".so maybe it is driver related. I compile the driver myself following the instructions here:http://archlinuxarm.org/forum/viewtopic.php?f=29&t=3980
baoyingcheng
 
Posts: 8
Joined: Wed Oct 17, 2012 1:22 pm

Re: Problem with WIFI AP mode

Postby baoyingcheng » Mon Nov 26, 2012 4:35 pm

anyone tried using pogo as a router?
still can't work in AP mode.
really need help ×_×
baoyingcheng
 
Posts: 8
Joined: Wed Oct 17, 2012 1:22 pm


Return to Community Supported

Who is online

Users browsing this forum: No registered users and 39 guests