wlan-interface cannot connect to any AP anymore if it changes its mac address (as a member of a lagg e.g.)...

2016-01-20 Thread Nils Beyer
Hi,

using FreeBSD 11.0-CURRENT r294313M - this example in the manpage of "if_lagg"
doesn't work anymore (it worked in an older 11.0-CURRENT; don't know the exact
revision yet):
==
[...]
 The following example uses an active failover interface to set up roaming
 between wired and wireless networks using two network devices.  Whenever
 the wired master interface is unplugged, the wireless failover device
 will be used:

   # ifconfig em0 up
   # ifconfig ath0 ether 00:11:22:33:44:55
   # ifconfig create wlan0 wlandev ath0 ssid my_net up
   # ifconfig lagg0 create
   # ifconfig lagg0 laggproto failover laggport em0 laggport wlan0 \
   192.168.1.1 netmask 255.255.255.0

 (Note the mac address of the wireless device is forced to match the wired
 device as a workaround.)
==


As soon as the interface "wlan0" changes its mac address, it cannot connect
to any AP anymore.


The problem is that if you put the wired interface to the failover lagg first
(so it becomes master) and after that the "wlan0" interface, the mac address of
the "wlan0" inteface immediately chnages to the mac address of the wired
interface:
==
#ifconfig lagg0 ; ifconfig wlan0
#
lagg0: flags=8843 metric 0 mtu 1500

options=c319a
ether 5c:f9:dd:55:c9:fb
inet 172.18.96.4 netmask 0xff00 broadcast 172.18.96.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto failover lagghash l2,l3,l4
laggport: alc0 flags=5
wlan0: flags=8843 metric 0 mtu 1500
ether a4:17:31:12:29:c3
nd6 options=29
media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11g
status: associated
ssid WendlerZone channel 11 (2462 MHz 11g) bssid 80:1f:02:1c:1a:5f
regdomain ETSI country DE indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7 scanvalid 60
protmode CTS wme burst roaming MANUAL
groups: wlan 
#
#ifconfig lagg0 laggport wlan0
#ifconfig lagg0 ; ifconfig wlan0
#
lagg0: flags=8843 metric 0 mtu 1500
ether 5c:f9:dd:55:c9:fb
inet 172.18.96.4 netmask 0xff00 broadcast 172.18.96.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto failover lagghash l2,l3,l4
laggport: alc0 flags=5
laggport: wlan0 flags=0<>
wlan0: flags=8843 metric 0 mtu 1500
ether 5c:f9:dd:55:c9:fb
nd6 options=29
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
ssid "" channel 8 (2447 MHz 11g)
regdomain ETSI country DE indoor ecm authmode WPA1+WPA2/802.11i
privacy ON deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 protmode CTS
wme burst roaming MANUAL
groups: wlan 
==

After that, the interface "wlan0" cannot connect to any AP anymore.


Any ideas how to solve that?



Regards,
Nils
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


[Bug 194336] AR9300 pci wireless card not working

2016-01-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336

Chris  changed:

   What|Removed |Added

 CC||ch...@tellme3times.com

--- Comment #15 from Chris  ---
Hello, I am experiencing the same issue with a Canadian purchased card D-Link
DWA-566 Wireless N 300 Dual Band PCI Express Desktop Adapter. This card was
purchased in Canada.

Changing the CTRY_DEFAULT, as  Greg Becker states, to CTRY_CANADA or
CTRY_UNITED_STATES resolves the error and allows the card to function properly.

I tried it on 10.1, 10.2 and 11.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


[Bug 194336] AR9300 pci wireless card not working

2016-01-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336

Jung-uk Kim  changed:

   What|Removed |Added

 CC||j...@freebsd.org

--- Comment #16 from Jung-uk Kim  ---
Created attachment 165875
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165875&action=edit
Add a regulatory domain for Canada

This should be more appropriate fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


[Bug 194336] AR9300 pci wireless card not working

2016-01-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336

Jung-uk Kim  changed:

   What|Removed |Added

 Attachment #165875|0   |1
is obsolete||

--- Comment #17 from Jung-uk Kim  ---
Created attachment 165880
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165880&action=edit
Add a regulatory domain for Canada

Adding a patch for ah_rd_domains.h.  Note the new entry is coped from FCC2.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


[Bug 194336] AR9300 pci wireless card not working

2016-01-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336

Jung-uk Kim  changed:

   What|Removed |Added

 Attachment #165875|1   |0
is obsolete||

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


[Bug 194336] AR9300 pci wireless card not working

2016-01-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336

--- Comment #18 from Chris  ---
After applying the 2 patches by  Jung-uk Kim I get the following;

dmesg | grep ath
ath0:  mem 0xfebe-0xfebf irq 17 at device 0.0 on pci4
ath0: RX status length: 48
ath0: RX buffer size: 4096
ath0: TX descriptor length: 128
ath0: TX status length: 36
ath0: TX buffers per descriptor: 4
ath0: ath_edma_setup_rxfifo: type=0, FIFO depth = 16 entries
ath0: ath_edma_setup_rxfifo: type=1, FIFO depth = 128 entries
ath0: [HT] enabling HT modes
ath0: [HT] enabling short-GI in 20MHz mode
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 stream STBC transmit enabled
ath0: [HT] 2 RX streams; 2 TX streams
ath0: AR9380 mac 448.3 RF5110 phy 0.0
ath0: 2GHz radio: 0x; 5GHz radio: 0x
ath0:  mem 0xfebe-0xfebf irq 17 at device 0.0 on pci4
ath0: RX status length: 48
ath0: RX buffer size: 4096
ath0: TX descriptor length: 128
ath0: TX status length: 36
ath0: TX buffers per descriptor: 4
ath0: ath_getchannels: unable to collect channel list from hal, status 12
device_attach: ath0 attach returned 22
ath0:  mem 0xfebe-0xfebf irq 17 at device 0.0 on pci4
ath0: RX status length: 48
ath0: RX buffer size: 4096
ath0: TX descriptor length: 128
ath0: TX status length: 36
ath0: TX buffers per descriptor: 4
ath0: ath_getchannels: unable to collect channel list from hal, status 12
device_attach: ath0 attach returned 22

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: [Bug 194336] AR9300 pci wireless card not working

2016-01-20 Thread Omni$
On Jan 20, 2016 12:52 PM,  wrote:

> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336
>
> --- Comment #18 from Chris  ---
> After applying the 2 patches by  Jung-uk Kim I get the following;
>
> dmesg | grep ath
> ath0:  mem 0xfebe-0xfebf irq 17 at device 0.0 on
> pci4
> ath0: RX status length: 48
> ath0: RX buffer size: 4096
> ath0: TX descriptor length: 128
> ath0: TX status length: 36
> ath0: TX buffers per descriptor: 4
> ath0: ath_edma_setup_rxfifo: type=0, FIFO depth = 16 entries
> ath0: ath_edma_setup_rxfifo: type=1, FIFO depth = 128 entries
> ath0: [HT] enabling HT modes
> ath0: [HT] enabling short-GI in 20MHz mode
> ath0: [HT] 1 stream STBC receive enabled
> ath0: [HT] 1 stream STBC transmit enabled
> ath0: [HT] 2 RX streams; 2 TX streams
> ath0: AR9380 mac 448.3 RF5110 phy 0.0
> ath0: 2GHz radio: 0x; 5GHz radio: 0x
> ath0:  mem 0xfebe-0xfebf irq 17 at device 0.0 on
> pci4
> ath0: RX status length: 48
> ath0: RX buffer size: 4096
> ath0: TX descriptor length: 128
> ath0: TX status length: 36
> ath0: TX buffers per descriptor: 4
> ath0: ath_getchannels: unable to collect channel list from hal, status 12
> device_attach: ath0 attach returned 22
> ath0:  mem 0xfebe-0xfebf irq 17 at device 0.0 on
> pci4
> ath0: RX status length: 48
> ath0: RX buffer size: 4096
> ath0: TX descriptor length: 128
> ath0: TX status length: 36
> ath0: TX buffers per descriptor: 4
> ath0: ath_getchannels: unable to collect channel list from hal, status 12
> device_attach: ath0 attach returned 22
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
> ___
> freebsd-wireless@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org
> "
>
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


[Bug 194336] AR9300 pci wireless card not working

2016-01-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336

--- Comment #19 from Jung-uk Kim  ---
(In reply to Chris from comment #18)
Hmm...  Please recompile kernel with "options AH_DEBUG".

https://wiki.freebsd.org/dev/ath%284%29/Debugging

We need to see "isEepromValid: invalid regulatory domain/country code 0xNN"
like comment #14.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"