Bug 178986 - [ath] Change mac address of ath(4) is not reflected when wlan is brought up
Summary: [ath] Change mac address of ath(4) is not reflected when wlan is brought up
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-26 09:40 UTC by Monthadar Al Jaberi
Modified: 2018-05-28 19:44 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Monthadar Al Jaberi freebsd_committer 2013-05-26 09:40:00 UTC
The mac address of AR5413 wifi chip is not updated after a new 
mac address is assigned to it. Probably all ath(4) devices have same issue.
This results in STAs not discarding to unicast frames address to the new MAC.

Fix: 

Workaround:
Running 'ifconfig ath0 up' just after setting new mac address seems to    
update the STA_ID0 register to the new mac address.
How-To-Repeat: COLD START two RSPRO with FreeBSD HEAD.
RSPRO1# ifconfig ath0 ether 00:01:02:00:00:01
RSPRO1# ifconfig wlan create wlandev ath0 wlanmode mesh channel 1 meshid test
RSPRO1# ifconfig wlan0 192.168.3.1

RSPRO2# ifconfig ath0 ether 00:01:02:00:00:02
RSPRO2# ifconfig wlan create wlandev ath0 wlanmode mesh channel 1 meshid test
RSPRO2# ifconfig wlan0 192.168.3.2

Running 'athregs -i ath0 | grep STA' on both RSPRO reveals that the chip
still has the old mac address registered as it's STA_ID0 (station id).

Pining between the RSPROs does not work.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-05-26 21:50:44 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-wireless

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:00 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.