Modify

Opened 7 years ago

Closed 7 years ago

Last modified 3 years ago

#7990 closed defect (fixed)

Wi-Fi: scanning for networks does not works (Atheros AR5416 + UBNT RS).

Reported by: User294 <t3st3r@…> Owned by: developers
Priority: normal Milestone: Backfire 10.03.1
Component: base system Version: Backfire 10.03.1 RC2
Keywords: Cc:

Description

Hi. I'm attempted to flash Backfire 10.03.1 RC3 to my Ubiquiti Router Station, I'm using it with AR5416 based Wi-Fi card. One of issues I found: wi-fi interface not seems to support scanning. Scanning in web interface leads to empty result. Attempt to use something like iwlist wlan0 scanning or iwlist mon.wlan0 scanning leads to message that operation is unsupported. Some driver issue I guess?

Attachments (0)

Change History (10)

comment:1 Changed 7 years ago by jow

  • Resolution set to wontfix
  • Status changed from new to closed

Normal.

In client mode use:

# wpa_cli -p /var/run/wpa_supplicant-wlan0 -i wlan0 scan
# wpa_cli -p /var/run/wpa_supplicant-wlan0 -i wlan0 scan_results

In AP mode you need to tear down the AP for a moment:

# ifconfig wlan0 down
# iw phy phy0 interface add scan0 type station
# ifconfig scan0 up
# iwlist scan0 scan
# ifconfig scan0 down
# iw dev scan0 del
# ifconfig wlan up
# killall -HUP hostapd

You could put that into a script.

}}}

comment:2 Changed 7 years ago by jow

If you're using the madwifi driver you can use this command sequence to scan in AP mode:

wlanconfig scan0 create wlandev wifi0 wlanmode sta
ifconfig scan0 up
wilist scan0 scan
ifconfig scan0 down
wlanconfig scan0 destroy

comment:3 follow-up: Changed 7 years ago by ledwards@…

Good info jow. I'm assuming the issue described was while using the ath5k driver? I haven't had any issues scanning while in AP mode using madwifi (either via LuCI or iwlist scan).

Just a thought... could logic be built into the LuCI wifi scan so the correct procedure (as you described above) will be executed to produce results (instead of displaying empty results)? Or perhaps the LuCI wifi scan could display a message explaining that scanning is not supported and what measures can be taken to enable scanning?

comment:4 Changed 7 years ago by User294 <t3st3r@…>

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Nice info, thanks! BUT, there is one issue still exists. There is button to scan networks in default web face and it does not works. So it looks like broken/half working firmware to users. I will reopen this bug for this reason. As for me, you should either warn users that such setup is not yet supported and scanning will not work, or, even better, adjust LuCI logic to allow scanning. As for me, I prefer to see "backfire" as codename only, not as an actual output :P

comment:5 in reply to: ↑ 3 Changed 7 years ago by jow

Just a thought... could logic be built into the LuCI wifi scan so the correct procedure (as you described above) will be executed to produce results (instead of displaying empty results)? Or perhaps the LuCI wifi scan could display a message explaining that scanning is not supported and what measures can be taken to enable scanning?

Yes, I'm working on it.

comment:6 Changed 7 years ago by anonymous

Any progress here?

comment:7 Changed 7 years ago by jow

Yes, its fixed in LuCI trunk (currently in snapshots).

comment:8 Changed 7 years ago by anonymous

Hopefully the patch also gets info Backfire, about which this thread is.

As far as I know, it doesn't work in Backfire branch.

comment:9 Changed 7 years ago by hnyman

This ticket might maybe be closed now that Backfire is using Luci 0.10. (At least for my ar71xx based WNDR3700 the Wifi scan works now nicely in Backfire.)

comment:10 Changed 7 years ago by nbd

  • Resolution set to fixed
  • Status changed from reopened to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.