Because it works by magic, not works by intent. There's no guarantee
that a STA device will let you re-program its MAC address.

It also confuses people when they believe you can setup things like
bridged VMs and they don't work across wifi but do across ethernet.


On 31 August 2015 at 05:20, Daniel Eischen <deisc...@freebsd.org> wrote:
> On Mon, 31 Aug 2015, Ranjan1018 . wrote:
>> 2015-08-30 17:12 GMT+02:00 Adrian Chadd <adrian.ch...@gmail.com>:
>>> hi,
>>> don'tr set ath0 to the MAC of your ethernet device, set your ethernet
>>> MAC to the MAC of your atheros device.
>>> (But I keep telling people, failover between ethernet/wifi isn't
>>> supported by the wifi code...)
> Why is it not?  I've been using it this way for years.  Switching
> from wired to wireless would seem to be a very common setup.  I think
> the clone interface should be taught how to pass down unsupported
> operations to its underlying device.
> My /etc/rc.conf:
>   # For now, force iwn0 to the same MAC address as re0.
>   # This works around a bug where lagg is unable to set the
>   # MAC address of the underlying WLAN (cloned) interface.
>   ifconfig_iwn0="ether d4:be:d9:50:4b:5c"
>   wlans_iwn0=wlan0
>   ifconfig_wlan0="ssid Scorpio WPA"
>   ifconfig_re0="up"
>   cloned_interfaces="lagg0"
>   ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0"
>   ifconfig_lagg0_alias0="inet netmask 0xffffff00"
> --
> DE
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to