Modify

Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#10062 closed defect (wontfix)

WZR-HP-AG300H 2.4GHz LED shows incorrect encryption status

Reported by: dimitris@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

I'm running the 2011-09-03 r28151 trunk snapshot. Both radios are enabled with PSK2, hwmode/htmode/capabilities are left to defaults:

root@maytag:~# cat /etc/config/wireless 
config wifi-device  radio0
	option type     mac80211
	option channel  11
	option macaddr	<mac>
	option hwmode	11ng
	option htmode	HT20
	list ht_capab	SHORT-GI-40
	list ht_capab	TX-STBC
	list ht_capab	RX-STBC1
	list ht_capab	DSSS_CCK-40
	option disabled 0

config wifi-iface
	option device   radio0
	option network  lan
	option mode     ap
	option ssid     <ssid1>
	option encryption psk2
	option key	<key1>

config wifi-device  radio1
	option type     mac80211
	option channel  36
	option macaddr	<mac+1>
	option hwmode	11na
	option htmode	HT20
	list ht_capab	SHORT-GI-40
	list ht_capab	TX-STBC
	list ht_capab	RX-STBC1
	list ht_capab	DSSS_CCK-40
	option disabled 0

config wifi-iface
	option device   radio1
	option network  lan
	option mode     ap
	option ssid     <ssid2>
	option encryption psk2
	option key	<key2>

The 2.4GHz LED ligts up amber, while the 5GHz LED is green. Both radios/networks seem to be working without problems, tested so far with two clients: An Ubuntu Lucid laptop with Intel a/b/g adapter, tested on both bands, and an Android tablet with a/b/g/n, tested on the 5GHz band only.

The manual, for the DD-WRT version, states that amber signals an "insecure" WLAN. I'm not sure where in the stack the LED is controlled. Hopefully this is just a case of [not] setting the right LED state in oWRT, and not "missing" encryption. As far as I can tell by the clients, they did require the PSK in order to connect.

Attachments (0)

Change History (7)

comment:1 Changed 6 years ago by dimitris@…

Still present with the r28257 snapshot. I don't see any LED controls other than DIAG under /sys; is this handled by the ath9k driver?

comment:2 Changed 6 years ago by flyn@…

Problem still exists in r29353.

Any tips on where in the code to look for this issue?

-Adam

comment:3 Changed 6 years ago by jow

Nowhere, there is no code at all yet to tie encryption status to the led state. I suppose you have to hook into /lib/wifi/hostapd.sh to toggle the led when the BSS is set up, but then in such a way that its only done on the ag300h etc.

comment:4 Changed 6 years ago by dimitris@…

Hope my questions aren't too silly:

There's only one LED "exposed" under /sys/devices/platform/leds-gpio/leds, and that's buffalo:red:diag. Is there a way other than gpio to manipulate LEDs from userspace?

If, as I understand it, gpio is the only way, then it looks like this depends on first figuring out which gpio lines drive the relevant LEDs on these devices and adding these to the right mach-ar71xx modules. If I haven't gone way too off course yet, any pointers on finding gpio lines?

comment:5 Changed 6 years ago by dimitris@…

For what it's worth, changing both networks above to be open (encryption 'none') makes no difference: It just seems that the 2.4GHz radio's LED defaults to amber and the 5GHz radio's LED defaults to green (r29353 trunk build from downloads.openwrt.org).

comment:6 Changed 6 years ago by nbd

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

openwrt does not use LEDs to display encryption status. the issue of missing leds is tracked in #11191

comment:7 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

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.