From owner-freebsd-net@FreeBSD.ORG Mon Mar 2 09:51:56 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 8A09CB4 for ; Mon, 2 Mar 2015 09:51:56 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 58E809EC for ; Mon, 2 Mar 2015 09:51:56 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t229prQ5003547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Mar 2015 01:51:54 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54F432B4.7050602@freebsd.org> Date: Mon, 02 Mar 2015 01:51:48 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: =?UTF-8?B?TG/Dr2MgQmxvdA==?= , freebsd-net@freebsd.org Subject: Re: fib issue with jails. References: <54F427EA.2010406@freebsd.org> <54F4205D.1030405@freebsd.org> <4aadb320a6608ae86ffe4b28fb747b0e@mail.unix-experience.fr> In-Reply-To: <4aadb320a6608ae86ffe4b28fb747b0e@mail.unix-experience.fr> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 09:51:56 -0000 On 3/2/15 1:37 AM, Loïc Blot wrote: > 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 working. The mac address is correct in the packet (default router) but the packet stays on VLAN inteface and doesn't use lag confirming from your other email, if you set the same route in fib0 (or maybe just a very specific one to 192 168.1.1 so that you don't break your system), then you see identical packets on the vlan, and they do go to the lagg, where ones done with a setfib at the same time, do not. but before the reboot both would have worked. Do the packets turn up somewhere else? or do they just disappear? I'm assuming you have tried multiple reboots and also doing the set up sequence by hand slowly? Unfortunatly, while I do understand the fib code generally, I know nothing about lagg. If you set this up by hand, what is the full list of commands you would have to do to get to this state? does it make a difference if the order is not the same? (e.g. if you set up the fib before or after the lagg?) it might be that the lag doesn't set itself up for multiple fibs if there is only one at the time that it is started, or maybe it's the other way around, and that the fibs are not set onto interfaces that do not exist when their routes are set... try both ways.. (I'll look in the morning.. it's late here now) > Regards, > > Loïc Blot, > UNIX Systems, Network and Security Engineer > http://www.unix-experience.fr > > 2 mars 2015 10:06 "Julian Elischer" a écrit: >> On 3/2/15 12:44 AM, Loïc Blot wrote: >> >>> Hi Julian, >>> >>> with tcpdump i see the packet on vlan136 but i don't see it on lagg0, whereas it must appear. >>> >>> it was working without vnet/vimage before the reboot. >> so my guess is that it is independent of the fib part.. >> >> If you make a jail with normal fib, but set routes to use vlan136 >> where do the packets go? >>> Regards, >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >