From owner-freebsd-stable@FreeBSD.ORG Wed Aug 29 08:12:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE2A0106566B; Wed, 29 Aug 2012 08:12:07 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from host.omnilan.net (s1.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 71CB28FC14; Wed, 29 Aug 2012 08:12:06 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by host.omnilan.net (8.13.8/8.13.8) with ESMTP id q7T8CVgR044816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Aug 2012 10:12:32 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <503DCEA4.5070305@omnilan.de> Date: Wed, 29 Aug 2012 10:11:16 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Pete French References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC9EB048CDD20BADFA44B3D8A" Cc: freebsd-net@freebsd.org, auryn@zirakzigil.org, freebsd-stable@freebsd.org Subject: Re: Problem with link aggregation + sshd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Aug 2012 08:12:08 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC9EB048CDD20BADFA44B3D8A Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable schrieb Pete French am 28.08.2012 11:48 (localtime): >> No answer, so it seems that link aggregation doesn't really work in fr= eebsd, >> this may help others with the same problem... > I used to use LCAP a lot - this was a few years ago, but the critical > point was that it only worked if all the cables went to the same > logcial switch. Using a pair of switches for redundancy works fine, as > long as they are of the type which stacvk and look like a single physic= al > switch software-wise. Link aggregation can never work with two separate switches! LACP and static trunking require both sides to bundle the same trunk. which is impossible for two separate switches. For redundancy, there is the SpanningTreeProtocol, which FreeBSD supports in bridge (4) (more preferrably RSTP). > Saying "it doesnt really work in freebsd" is, to be honest, not so > far off the mark (if somewhat harshly phrased) - but it can be made to > behave if you do it in a certain way, and when it does it runs very nic= ely. In that case, it's nothing to do with FreeBSD! -Harry --------------enigC9EB048CDD20BADFA44B3D8A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlA9ztAACgkQLDqVQ9VXb8hyUQCeOhhyP5SrY/smTLa8t9+IkzLs D60An25gzXOFipcOL6wMS9wP9AKtjqtt =wKtp -----END PGP SIGNATURE----- --------------enigC9EB048CDD20BADFA44B3D8A--