Re: Upgrading to r297291 LAGG(4) stops working.

2015-12-11 Thread Alexandr Krivulya
01.09.15 11:44, Gleb Smirnoff пишет: > On Mon, Aug 31, 2015 at 09:58:45AM -0700, Adrian Chadd wrote: > A> Hi, > A> > A> +glebius, as he recently messed around with the wifi stack and his > A> changes may have broken how mac addresses are assigned to the > A> hardware. > > I've tested that with

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-07 Thread Gleb Smirnoff
On Sun, Sep 06, 2015 at 11:05:41AM -0400, Daniel Eischen wrote: D> Please add an entry to src/UPDATING to explain the change needed. D> D> Also, my question remains, if wlan now knows how to set the MAC D> address, do we still need to set the MAC address manually and D> can we go back to using

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-07 Thread Sergey Kandaurov
On 4 September 2015 at 17:06, Gleb Smirnoff wrote: > On Fri, Sep 04, 2015 at 04:39:22PM +0300, Sergey Kandaurov wrote: > S> On 1 September 2015 at 04:47, John Baldwin wrote: > S> > On Monday, August 31, 2015 09:58:45 AM Adrian Chadd wrote: > S> >> Hi, > S>

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-06 Thread Daniel Eischen
Please add an entry to src/UPDATING to explain the change needed. Also, my question remains, if wlan now knows how to set the MAC address, do we still need to set the MAC address manually and can we go back to using lagg just like it was 2 non-wireless connections (in the case that the

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-04 Thread Sergey Kandaurov
On 1 September 2015 at 04:47, John Baldwin wrote: > On Monday, August 31, 2015 09:58:45 AM Adrian Chadd wrote: >> Hi, >> >> +glebius, as he recently messed around with the wifi stack and his >> changes may have broken how mac addresses are assigned to the >> hardware. > >

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-04 Thread Gleb Smirnoff
On Fri, Sep 04, 2015 at 04:39:22PM +0300, Sergey Kandaurov wrote: S> On 1 September 2015 at 04:47, John Baldwin wrote: S> > On Monday, August 31, 2015 09:58:45 AM Adrian Chadd wrote: S> >> Hi, S> >> S> >> +glebius, as he recently messed around with the wifi stack and his S> >>

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-04 Thread Daniel Eischen
On Fri, 4 Sep 2015, Sergey Kandaurov wrote: On 1 September 2015 at 04:47, John Baldwin wrote: On Monday, August 31, 2015 09:58:45 AM Adrian Chadd wrote: Hi, +glebius, as he recently messed around with the wifi stack and his changes may have broken how mac addresses are

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-01 Thread John Baldwin
On Monday, August 31, 2015 09:58:45 AM Adrian Chadd wrote: > Hi, > > +glebius, as he recently messed around with the wifi stack and his > changes may have broken how mac addresses are assigned to the > hardware. Glebius did break this, though not because of what you say. It's broken because the

Re: Upgrading to r297291 LAGG(4) stops working.

2015-09-01 Thread Gleb Smirnoff
On Mon, Aug 31, 2015 at 09:58:45AM -0700, Adrian Chadd wrote: A> Hi, A> A> +glebius, as he recently messed around with the wifi stack and his A> changes may have broken how mac addresses are assigned to the A> hardware. I've tested that with new code setting MAC address on wlan0 passed it down

Re: Upgrading to r297291 LAGG(4) stops working.

2015-08-31 Thread Ranjan1018 .
2015-08-30 17:12 GMT+02:00 Adrian Chadd : > 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...) > > > -a

Re: Upgrading to r297291 LAGG(4) stops working.

2015-08-31 Thread Adrian Chadd
Hi, +glebius, as he recently messed around with the wifi stack and his changes may have broken how mac addresses are assigned to the hardware. -adrian On 31 August 2015 at 09:28, Ranjan1018 . <21474...@gmail.com> wrote: > 2015-08-31 10:53 GMT+02:00 Adrian Chadd : >>

Re: Upgrading to r297291 LAGG(4) stops working.

2015-08-31 Thread Adrian Chadd
Hi, 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. -adrian On 31 August

Re: Upgrading to r297291 LAGG(4) stops working.

2015-08-31 Thread Daniel Eischen
On Mon, 31 Aug 2015, Adrian Chadd wrote: Hi, 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. As long as an attempt to set the MAC address returns an error that is meaningful (ENOTSUP?), that is fine. I still

Re: Upgrading to r297291 LAGG(4) stops working.

2015-08-31 Thread Adrian Chadd
ok, so this used to work before? And you're running -HEAD? -a On 31 August 2015 at 00:23, Ranjan1018 . <21474...@gmail.com> wrote: > 2015-08-30 17:12 GMT+02:00 Adrian Chadd : >> >> hi, >> >> don'tr set ath0 to the MAC of your ethernet device, set your ethernet >> MAC to

Re: Upgrading to r297291 LAGG(4) stops working.

2015-08-31 Thread Daniel Eischen
On Mon, 31 Aug 2015, Ranjan1018 . wrote: 2015-08-30 17:12 GMT+02:00 Adrian Chadd : 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

Upgrading to r297291 LAGG(4) stops working.

2015-08-30 Thread Ranjan1018 .
On my laptop I am using LAGG(4) as explained in Example 30.3. Failover Mode Between Ethernet and Wireless Interfaces in the Handbook. In rc.conf i have: # LAGG ifconfig_re0=up ifconfig_ath0=ether 18:67:b0:39:bd:23 wlans_ath0=wlan0 ifconfig_wlan0=WPA cloned_interfaces=lagg0 ifconfig_lagg0=laggproto

Re: Upgrading to r297291 LAGG(4) stops working.

2015-08-30 Thread Adrian Chadd
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...) -a On 30 August 2015 at 05:52, Ranjan1018 . 21474...@gmail.com wrote: On my laptop