On Tue, Dec 17, 2013 at 03:44:31PM -0700, Warren Block wrote: > In recent discussion on the -current mailing list, it was pointed out that > using lagg(4) for failover from wired to wireless networking is not fully > functional: > http://lists.freebsd.org/pipermail/freebsd-current/2013-December/047259.html > > I know that Dru told me she'd always had problems with it back in June, a > surprise to me since it had worked for me before. It didn't work then when > I tried to show her... > > My question is the right way to remove this from the Handbook. It can be > commented out, but that leaves stale contents in the file. Is it better to > remove the code and trust the repository to keep the old version available > for recall when lagg(4) works for that again?
For what it is worth, lagg(4) for wired- and wireless connections works
fine for me.
In my network, wireless and wired setup is done from a FreeBSD firewall
with an em(4) and ath(4) device configured as a bridge(4) interface.
I have the following scripts that handle the lease renewals:
--- /etc/start_if.lagg0 begin ---
#!/bin/sh
/bin/pkill dhclient
/usr/local/sbin/dhclient -6 -lf /var/db/dhclient6.leases -pf \
/var/run/dhclient6.lagg0.pid lagg0 2>&1 >/dev/null &
/usr/local/sbin/dhclient -4 -lf /var/db/dhclient.leases -pf \
/var/run/dhclient.lagg0.pid lagg0 2>&1 >/dev/null &
--- /etc/start_if.lagg0 end ---
--- /etc/start_if.lagg0 begin ---
#!/bin/sh
/bin/pkill dhclient
--- /etc/start_if.lagg0 end ---
When I switch from wired to wireless or the reverse, there is a brief
connection loss (about 3 seconds).
Glen
pgpACnICd2dTM.pgp
Description: PGP signature
