From owner-freebsd-net@FreeBSD.ORG Wed May 21 17:45:02 2008 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 307941065679 for ; Wed, 21 May 2008 17:45:02 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.freebsd.org (Postfix) with ESMTP id BD06F8FC1D for ; Wed, 21 May 2008 17:45:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-064-185-072.pools.arcor-ip.net [88.64.185.72]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1JysN10Vvw-0004RW; Wed, 21 May 2008 19:44:59 +0200 Received: (qmail 45664 invoked from network); 21 May 2008 17:43:16 -0000 Received: from myhost.laiers.local (192.168.4.151) by laiers.local with SMTP; 21 May 2008 17:43:16 -0000 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Wed, 21 May 2008 19:44:42 +0200 User-Agent: KMail/1.9.9 References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> In-Reply-To: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805211944.42418.max@love2party.net> X-Provags-ID: V01U2FsdGVkX18+6E3Z1+RUAHYEmhOAtiNc9utn9plWa+5dm2J TdF4R/BefC2yAvfnwifZnVySxGtreonGS/TSmpPj1IskmJDDP6 6H4aUyNd1yi5/ceKtXYBA== Cc: Subject: Re: lagg0.2 style vlans on lagg(4) interface 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: Wed, 21 May 2008 17:45:02 -0000 On Wednesday 21 May 2008 19:31:46 Niki Denev wrote: > If one tries to use lagg0.2 style vlans on lagg0 interface configured > from rc.conf it does't work. > The problem is that all of the cloned interfaces (lagg0 , lagg0.2, etc) > are created before any other interface configuration is done, > and in this case lagg0 is created, then lagg0.2 is created. > But because lagg0 does not have any members yet, it's MAC address > is all zeroes, and this is inherited by the vlan interfaces. > At the next step the members are added to the lagg0 interface and it's > mac address gets set, > but the vlan interfaces never see this change and remain with mac > address 00:00:00:00:00:00 and in unusable state. > > Does it sound reasonable for the vlan(4) interfaces to update their > mac address when their parent changes it. > (this should probably look more like the parent telling the vlans > attached to it that it's mac has changed, but > i'm not sure if the parent knows about children interfaces) It doesn't (and shouldn't have to). I'd simply add an EVENTHANDLER_INVOKE(ifaddr_event, ifp) to if_setlladdr() - we do that for INET[6] address already. Then vlan (and any other device interested in LLaddress changes) can simply register to that eventhandler and resync. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News