On 12/17/13 12:34, Allan Jude wrote:
> On 2013-12-17 10:54, Adrian Chadd wrote:
>> The MAC of the lagg needs to be the same as the wireless interface.
>> I'm going to just state right now that using lagg as the failover
>> method for doing wireless/wired integration isn't supported by me. If
>> someone wants to make it supported then they need to claim it. :)
>> On 17 December 2013 05:06, dan_partelly <dan_parte...@rdsor.ro> wrote:
>>> Hi all,
>>> I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as
>>> described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop.
>>> What happens is:
>>> If I boot the system with the Ethernet cable attached, I correctly get
>>> lagg0 active port on master- bg0- and the network is working correctly.
>>> (I mainly test pinging my gateway). When I pull the cable out, lagg0
>>> device correctly switches to wlan0 as shown by ifconfig (wlan0 is created
>>> from wpi0), but at the same time I get no more ping replies from my
>>> gateway. I can leave the system in this state for several minutes as an
>>> and no replies are coming through. A simple list of interfaces with
>>> ifconfig with no parameters brigs the network back to life, and I start to
>>> get back the due ping replyes, this time thrugh wireless link.
>>> Please, if possible en-light me on tis problem. I sat at your disposition
>>> with any info you may deem necessary to get this fixed (if it needs a fix).
>>> email@example.com mailing list
>>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>> firstname.lastname@example.org mailing list
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> If I am am understanding correctly, Dan and Nikolai say that just
> running 'ifconfig' brings the lagg back to life. Why would that make a
> difference at all? Running ifconfig with no parameters shouldn't be
> changing anything.
I see the same lagg behavior change going from 9.2->10.0, but for me the
test is slightly different. My wired and wireless networks use different
IP address ranges, so I need to re-run dhclient on lagg0, but I can't
get an address on it. In fact, dhclient doesn't work at all with a lagg
interface when it is only backed by my wireless card.
Without a lagg interface, I can get addresses on both wired and wireless
cards individually and act dual-homed just fine.
- Nikolai Lifanov
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"