From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 21:31:49 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F4971065672 for ; Sat, 19 Feb 2011 21:31:49 +0000 (UTC) (envelope-from k@kevinkevin.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6E89E8FC13 for ; Sat, 19 Feb 2011 21:31:49 +0000 (UTC) Received: by iwn39 with SMTP id 39so4897823iwn.13 for ; Sat, 19 Feb 2011 13:31:48 -0800 (PST) Received: by 10.42.239.136 with SMTP id kw8mr2748811icb.502.1298151108679; Sat, 19 Feb 2011 13:31:48 -0800 (PST) Received: from kkPC (not.enough.unixsluts.com [76.10.166.187]) by mx.google.com with ESMTPS id 8sm3225763iba.10.2011.02.19.13.31.45 (version=SSLv3 cipher=OTHER); Sat, 19 Feb 2011 13:31:47 -0800 (PST) From: "kevin" To: "'Tom Judge'" References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> <4D5FDCF1.6050909@gmx.com> <00a501cbd04f$2276b5b0$67642110$@com> <4D5FFE9C.30005@tomjudge.com> In-Reply-To: <4D5FFE9C.30005@tomjudge.com> Date: Sat, 19 Feb 2011 16:31:26 -0500 Message-ID: <00c901cbd07c$5ec03cd0$1c40b670$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: AcvQWvebJ/t04wk6Qr+mKJ8/6bZOlgAIO5oA Cc: freebsd-net@freebsd.org, 'Nikos Vassiliadis' Subject: RE: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2011 21:31:49 -0000 >There is a also the caveat: The switch will probably _not_ forward the STP BPDU's from one port to another. This is because if the switch is a properly >compliant bridge it will not forwards the frames as they are marked as link local ethernet multicast frame which is not allowed to forwarded by a bridge >per the ethernet spec. If this is indeed the case you will make an instant forwarding loop in your network when you try to make it work. >From the user manual of my switch, I have the following options to set for BPDU handling : BPDU Handling - Determines how BPDU packets are managed when STP is disabled on the port device. BPDUs are used to transmit spanning tree information. The possible field values are:\ - Filtering - Filters BPDU packets when spanning tree is disabled on an interface. - Flooding - Floods BPDU packets when spanning tree is disabled on an interface. This is the default value. I believe the 'flooding' option will blood BPDU packets to all ports on the switch device. Is that something that would forward the STP BPDU's from the disabled ports you think? Implementing another switch isn't really an option right now so if I cannot get this to work with my existing equiptment I will have to redesign the network without bridging , unfortunately (pf + carp + pfsense + multiple gateways). Thanks, Kevin