From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 11:34:50 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98D4437B401 for ; Tue, 27 May 2003 11:34:50 -0700 (PDT) Received: from maeko.hayai.de (denver038.server4free.de [217.172.178.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 353B643F75 for ; Tue, 27 May 2003 11:34:47 -0700 (PDT) (envelope-from mail@maeko.hayai.de) Received: from maeko.hayai.de (localhost [127.0.0.1]) by maeko.hayai.de (8.12.7/8.12.7) with ESMTP id h4RIYko3025413 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 27 May 2003 20:34:46 +0200 Received: (from mail@localhost) by maeko.hayai.de (8.12.7/8.12.7/Submit) id h4RIYjja025412; Tue, 27 May 2003 20:34:45 +0200 Date: Tue, 27 May 2003 20:34:45 +0200 From: Marco Wertejuk To: Maxim Konovalov Message-ID: <20030527183445.GA25234@maeko> Mail-Followup-To: Maxim Konovalov , freebsd-hackers@freebsd.org References: <20030514184845.GA7573@maeko> <20030515114239.Y95792@news1.macomnet.ru> <20030516153333.GA29165@maeko> <20030520190746.P6042@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030520190746.P6042@news1.macomnet.ru> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org Subject: Re: vlan/bridging broken in 4.8-release? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 18:34:50 -0000 Hello Maxim, today I've tried your hack and it works, at least it seems so. It was not exactly the same setup but nearly the same. The bridge has two interfaces (fxp0, fxp1) and one host is connected to each interface (using crosslink cables, no other networking devices such as broken HP ProCurve switches). The host on fxp1 (10.10.10.16) does not use vlans, the host on fxp0 (10.10.10.18) is in vlan id 1. tcpdump -tni fxp0, fxp1, vlan0: (yes 10.10.10.18 has a strange mac address, because of a broken fxp0 card I guess ;) 6:0:ff:1:6:0 ff:ff:ff:ff:ff:ff 0806 56: arp who-has 10.10.10.16 tell 10.10.10.18 0:d0:b7:17:5:78 6:0:ff:1:6:0 0806 60: arp reply 10.10.10.16 is-at 0:d0:b7:17:5:78 6:0:ff:1:6:0 0:d0:b7:17:5:78 0800 98: 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 0800 98: 10.10.10.16 > 10.10.10.18: icmp: echo reply 6:0:ff:1:6:0 ff:ff:ff:ff:ff:ff 8100 60: 802.1Q vlan#1 P0 arp who-has 10.10.10.16 tell 10.10.10.18 0:d0:b7:17:5:78 6:0:ff:1:6:0 8100 64: 802.1Q vlan#1 P0 arp reply 10.10.10.16 is-at 0:d0:b7:17:5:78 6:0:ff:1:6:0 0:d0:b7:17:5:78 8100 102: 802.1Q vlan#1 P0 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 8100 102: 802.1Q vlan#1 P0 10.10.10.16 > 10.10.10.18: icmp: echo reply 6:0:ff:1:6:0 0:d0:b7:17:5:78 0800 98: 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 0800 98: 10.10.10.16 > 10.10.10.18: icmp: echo reply 6:0:ff:1:6:0 0:d0:b7:17:5:78 8100 102: 802.1Q vlan#1 P0 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 8100 102: 802.1Q vlan#1 P0 10.10.10.16 > 10.10.10.18: icmp: echo reply Two pings were send successfully with your hack and I guess everything else would work too, but I have no time for further testing, maybe the people who wrote the PR have more time ... Please make a real patch out of your hack and get it commited into -stable because I still want to use it for one of my customers :) Hopefully I did not forget anything in this email :) -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting & Internet Solutions