From owner-freebsd-net@FreeBSD.ORG Mon Mar 2 11:37:00 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8179628C; Mon, 2 Mar 2015 11:37:00 +0000 (UTC) Received: from smtp.unix-experience.fr (195-154-176-227.rev.poneytelecom.eu [195.154.176.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1A3897DB; Mon, 2 Mar 2015 11:36:59 +0000 (UTC) Received: from smtp.unix-experience.fr (unknown [192.168.200.21]) by smtp.unix-experience.fr (Postfix) with ESMTP id D5C303252E; Mon, 2 Mar 2015 11:36:53 +0000 (UTC) X-Virus-Scanned: scanned by unix-experience.fr Received: from smtp.unix-experience.fr ([192.168.200.21]) by smtp.unix-experience.fr (smtp.unix-experience.fr [192.168.200.21]) (amavisd-new, port 10024) with ESMTP id YBul55PNskNq; Mon, 2 Mar 2015 11:36:51 +0000 (UTC) Received: from mail.unix-experience.fr (repo.unix-experience.fr [192.168.200.30]) by smtp.unix-experience.fr (Postfix) with ESMTPSA id 516F832521; Mon, 2 Mar 2015 11:36:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unix-experience.fr; s=uxselect; t=1425296211; bh=Xm2ZVLdq2BEo8FCbSjMSU6poMQD/OrFFrORklLiXKEo=; h=Date:From:Subject:To:In-Reply-To:References; b=QVqnmCa+ccCzXpA2O9JfpZA1Sn/QCwqLN4QE+7hKXR0sls3xSasUZh9rMyaTeyozs uhCVaheMbG9zHiYVPicyX80aP5/8HOVVhO7pmD1tkEJoU+NbpZKQCKJ2Rw4Hnc1SMh jk5fPOJwc3P268Gq8A4FsRltopRo9JdfdwbBnEpw= Mime-Version: 1.0 Date: Mon, 02 Mar 2015 11:36:51 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-ID: <5756f4ab845cd5bb738f6b87d497b9d0@mail.unix-experience.fr> X-Mailer: RainLoop/1.8.0.250 From: "=?utf-8?B?TG/Dr2MgQmxvdA==?=" Subject: Re: fib issue with jails. To: "Julian Elischer" , freebsd-net@freebsd.org In-Reply-To: <54F432B4.7050602@freebsd.org> References: <54F432B4.7050602@freebsd.org> <54F427EA.2010406@freebsd.org> <54F4205D.1030405@freebsd.org> <4aadb320a6608ae86ffe4b28fb747b0e@mail.unix-experience.fr> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2015 11:37:00 -0000 Hmmm sorry Julian,=0Ain fact everything works perfect... somebody has cha= nged by F5 master/slave and the current master wasn't synced for network = and doesn't route ... This is solved. No problem with Fib + Vlan + Lagg := )=0A=0ASorry for the inconvenience=0ARegards,=0A=0ALo=C3=AFc Blot,=0AUNIX= Systems, Network and Security Engineer=0Ahttp://www.unix-experience.fr= =0A=0A2 mars 2015 10:52 "Julian Elischer" a =C3=A9cr= it:=0A> On 3/2/15 1:37 AM, Lo=C3=AFc Blot wrote:=0A> =0A>> In fact, if i = use setfib on the host, not in the jail and i do a setfib ping 192.168.1.= 1 it's not=0A>> working. The mac address is correct in the packet (defaul= t router) but the packet stays on VLAN=0A>> inteface and doesn't use lag= =0A> =0A> confirming from your other email,=0A> if you set the same route= in fib0 (or maybe just a very specific one=0A> to 192 168.1.1 so that yo= u don't break your system),=0A> then you see identical packets on the vla= n, and they do go to the lagg,=0A> where ones done with a setfib at the s= ame time, do not.=0A> but before the reboot both would have worked.=0A> = =0A> Do the packets turn up somewhere else? or do they just disappear?=0A= > I'm assuming you have tried multiple reboots and also doing the set up= =0A> sequence by hand slowly?=0A> =0A> Unfortunatly, while I do understan= d the fib code generally, I know=0A> nothing about lagg.=0A> =0A> If you = set this up by hand, what is the full list of commands you=0A> would have= to do to get to this state?=0A> =0A> does it make a difference if the or= der is not the same?=0A> (e.g. if you set up the fib before or after the = lagg?)=0A> it might be that the lag doesn't set itself up for multiple fi= bs if=0A> there is only one at the time=0A> that it is started, or maybe = it's the other way around, and that the=0A> fibs are not set onto interfa= ces=0A> that do not exist when their routes are set...=0A> =0A> try both = ways..=0A> =0A> (I'll look in the morning.. it's late here now)=0A> =0A>>= Regards,=0A>> =0A>> Lo=C3=AFc Blot,=0A>> UNIX Systems, Network and Secur= ity Engineer=0A>> http://www.unix-experience.fr=0A>> =0A>> 2 mars 2015 10= :06 "Julian Elischer" a =C3=A9crit:=0A>>> On 3/2/15 = 12:44 AM, Lo=C3=AFc Blot wrote:=0A>>> =0A>>>> Hi Julian,=0A>>>> =0A>>>> w= ith tcpdump i see the packet on vlan136 but i don't see it on lagg0, wher= eas it must appear.=0A>>>> =0A>>>> it was working without vnet/vimage bef= ore the reboot.=0A>>> =0A>>> so my guess is that it is independent of the= fib part..=0A>>> =0A>>> If you make a jail with normal fib, but set rout= es to use vlan136=0A>>> where do the packets go?=0A>>>> Regards,=0A>>> = =0A>>> _______________________________________________=0A>>> freebsd-net@= freebsd.org mailing list=0A>>> http://lists.freebsd.org/mailman/listinfo/= freebsd-net=0A>>> To unsubscribe, send any mail to "freebsd-net-unsubscri= be@freebsd.org"=0A> =0A> _______________________________________________= =0A> freebsd-net@freebsd.org mailing list=0A> http://lists.freebsd.org/ma= ilman/listinfo/freebsd-net=0A> To unsubscribe, send any mail to "freebsd-= net-unsubscribe@freebsd.org"