Date: Mon, 09 Apr 2007 20:15:12 +0300 From: Niki Denev <ndenev@totalterror.net> To: Andrew Thompson <thompsa@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: CFT: new trunk(4) Message-ID: <461A74A0.4080201@totalterror.net> In-Reply-To: <20070409085118.GF64415@heff.fud.org.nz> References: <20070329235520.GD97061@heff.fud.org.nz> <460E6536.7060805@totalterror.net> <20070401095618.GA24408@heff.fud.org.nz> <4611F645.5000305@totalterror.net> <20070409085118.GF64415@heff.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew Thompson wrote: > On Tue, Apr 03, 2007 at 09:37:57AM +0300, Niki Denev wrote: >>>> Andrew Thompson wrote: >>>>> Here is a patch to add OpenBSD's trunk(4) interface, and also includes >>>>> LACP support which came from agr(4) on NetBSD. Im interested in anyone >>>>> who wants to test this and in particular lacp mode if you have a switch >>>>> that supports it. >>>>> >> I tried today to do the wireless/wired roaming, almost as given >> in the man page, with the exception that my wireless interface (ath), >> uses WPA, and i'm trying to run dhclient on the trunk interface. >> However it does not work as expected, and i'm not sure why... >> The problem is that if ath0 is a member of the trunk0 interface >> it always deassociates a few seconds after associating. >> If i remove it from the trunk group it associates perfectly, and >> keeps the link up. > > The updated patch here partially fixes the problem, the EAP packets will > be passed now. > > http://people.freebsd.org/~thompsa/if_trunk-20070409.diff > > The remaining issue is that when the wireless interface is added to the > trunk it will get a down/up as part of changing the MAC address. This > causes wpa_supplicant to close and it doesnt get relaunched. Manually > starting wpa_supplicant works but I need to find a way around this. > > > cheers, > Andrew I'm not sure that i didn't mess something up with the cleaning up of the previous patch before applying the new one, but i had to add one line to the trunk_port_output() function, more specifically to initialize the variable "type" to zero, because gcc kept complaining that it could be used uninitialized and failed to compile the module. Other than that if_trunk(4) seems to work pretty well, minus the wpa_supplicant issue. P.S.: what is the correct way to determine the trunkport interface that is currently being used to route traffic in failover mode? I see that the first interface is marked as MASTER, and all interfaces with link are marked as ACTIVE. I guess that "the first active interface in the order that they were added to the trunk group is the one currently sending/receiving traffic" is the answer, but maybe i'm missing something more obvious, like another flag/status? Anyways, thanks for the great work! Regards, Niki -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGGnSgHNAJ/fLbfrkRAtQbAJ4ku+niQ2f75xySkF+EdP5c1/vsAQCffb4T lCkkAhnk21x/C8MnfcW1Ghs= =oRWn -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?461A74A0.4080201>