From owner-freebsd-net@FreeBSD.ORG Sun Feb 1 00:47:01 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 14F621065675; Sun, 1 Feb 2009 00:47:01 +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 B4ECA8FC12; Sun, 1 Feb 2009 00:47:00 +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 n110kwKT026717; Sat, 31 Jan 2009 19:46:58 -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 n110kwg5076330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Jan 2009 19:46:58 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200902010046.n110kwg5076330@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 31 Jan 2009 19:47:02 -0500 To: Andrew Thompson From: Mike Tancsa In-Reply-To: <20090131213354.GA29777@citylink.fud.org.nz> References: <200901271739.n0RHdGd3047497@lava.sentex.ca> <20090131213354.GA29777@citylink.fud.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: freebsd-net@FreeBSD.org Subject: Re: 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: Sun, 01 Feb 2009 00:47:01 -0000 At 04:33 PM 1/31/2009, Andrew Thompson wrote: > > > > 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 > >Can you verify that em2, em3 and all the lagg* interfaces have the same >mac address. > Looks to be from the server side. I dont have them hooked up to the switch right now, but will Monday em2: flags=8843 metric 0 mtu 1500 options=19b ether 00:30:48:90:4c:fe inet 1.1.1.1 netmask 0xffffff00 broadcast 1.1.1.255 media: Ethernet autoselect status: no carrier lagg: laggdev lagg0 em3: flags=8843 metric 0 mtu 1500 options=19b ether 00:30:48:90:4c:fe inet 10.10.1.1 netmask 0xffffff00 broadcast 10.10.1.255 media: Ethernet autoselect status: no carrier lagg: laggdev lagg0 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 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: no carrier laggproto failover laggport: em3 flags=0<> laggport: em2 flags=1 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: no carrier 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: no carrier vlan: 102 parent interface: lagg0 >Andrew