From owner-freebsd-net@FreeBSD.ORG Tue Jan 27 18:22:41 2009 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 BA3EB106564A; Tue, 27 Jan 2009 18:22:41 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 93F128FC08; Tue, 27 Jan 2009 18:22:41 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0RHdHau019625; Tue, 27 Jan 2009 12:39:17 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id n0RHdGd3047497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Jan 2009 12:39:16 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200901271739.n0RHdGd3047497@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 27 Jan 2009 12:39:26 -0500 To: freebsd-net@freebsd.org From: Mike Tancsa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Subject: lagg failover mode and vlans 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: Tue, 27 Jan 2009 18:22:42 -0000 Hi, I noticed a small issue with the way VLANs work and the lagg0 interface in failover mode. I have a simple config of ifconfig lagg0 create up laggproto failover laggport em2 laggport em3 192.168.44.99/24 ifconfig lagg0.100 create 192.168.100.1/24 ifconfig lagg0.102 create 192.168.102.1/24 with em2 on one cisco 3500 and em3 on another cisco 3500 (primary and secondary) on port 32 of each switch interface FastEthernet0/32 switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-200,1002-1005 switchport mode trunk spanning-tree portfast ! interface FastEthernet0/32 switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-200,1002-1005 switchport mode trunk spanning-tree portfast ! and the switches are linked together with interface GigabitEthernet0/2 switchport trunk encapsulation dot1q switchport mode trunk ! On the freebsd RELENG_7 box lagg0: flags=8843 metric 0 mtu 1500 options=19b ether 00:30:48:90:4c:fe inet 192.168.44.99 netmask 0xffffff00 broadcast 192.168.44.255 media: Ethernet autoselect status: active laggproto failover laggport: em3 flags=0<> laggport: em2 flags=5 For the native vlan of 1, if I pull the cable on the master port fa0/32, it works automatically and I barely miss a packet lagg0: flags=8843 metric 0 mtu 1500 options=19b ether 00:30:48:90:4c:fe inet 192.168.44.99 netmask 0xffffff00 broadcast 192.168.44.255 media: Ethernet autoselect status: active laggproto failover laggport: em3 flags=4 laggport: em2 flags=1 but if I create some vlan interfaces off lagg0 lagg0.100: flags=8843 metric 0 mtu 1500 options=3 ether 00:30:48:90:4c:fe inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 media: Ethernet autoselect status: active vlan: 100 parent interface: lagg0 lagg0.102: flags=8843 metric 0 mtu 1500 options=3 ether 00:30:48:90:4c:fe inet 192.168.102.1 netmask 0xffffff00 broadcast 192.168.102.255 media: Ethernet autoselect status: active vlan: 102 parent interface: lagg0 and do the same pulling of the cable, it does not work. BUT, if I do an arp -nda on a machine that is part of vlan102 which is doing the pinging (so an arp-who has gets sent out and a reply answered), it works. The other option is if I send a packet out on the vlan's broadcast address from the server Apart from making a script to watch for interface up/down events on the machine with the lagg0 interface and vlans to do ping to each of the broadcast addresses, is there a way around this ? There was a discussion sort of around this in http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2008-05/msg00283.html ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike