From owner-freebsd-stable@FreeBSD.ORG Wed Aug 29 10:24:52 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 651491065673; Wed, 29 Aug 2012 10:24:52 +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 E3BDD8FC22; Wed, 29 Aug 2012 10:24:50 +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 q7TAPLIK047058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Aug 2012 12:25:21 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <503DEDF1.2020406@omnilan.de> Date: Wed, 29 Aug 2012 12:24:49 +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: <503DEC58.1050609@omnilan.de> In-Reply-To: <503DEC58.1050609@omnilan.de> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF43D9C6B09CD2D4AB4838903" 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 10:24:52 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF43D9C6B09CD2D4AB4838903 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable schrieb Harald Schmalzbauer am 29.08.2012 12:18 (localtime): > schrieb Pete French am 29.08.2012 11:38 (localtime): >>> 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. >> These switches had a port where you could connect them together and >> then configure each to know about the other switch, and to do LACP >> across the pair of them. Or at least thats what it looked like it >> was capable of doing, and it appeared to be doing LACP when configured= >> that way and connected to Windows machines, just not FreeBSD ones. But= I'm Have you checked that Windows really did LACP in your case? Sounds like it was no real hardware stack, so probably Windos just activated RSTP. FreeBSD doesn't detect any LACP/RSTP configuration features, but windows does with some NIC verndor's drivers. -Harry P.S.: Sorry for that additional answer, just forgot it in my last email. --------------enigF43D9C6B09CD2D4AB4838903 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) iEYEARECAAYFAlA97fEACgkQLDqVQ9VXb8gMgACgzrjGi0TNwuxFSZaAp07dGDhA EgEAmwYtrpmvKeSb9EMzoDDLvZK8LjTF =5bB2 -----END PGP SIGNATURE----- --------------enigF43D9C6B09CD2D4AB4838903--