Date: Wed, 19 Dec 2012 14:44:18 +0100 From: =?UTF-8?Q?G=C3=B6ran_L=C3=B6wkrantz?= <goran.lowkrantz@ismobile.com> To: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> Cc: freebsd-stable@freebsd.org Subject: Re: FIB and jail regression [Was: can't reach jails own ipv4 from inside anymore] Message-ID: <7CCE5A5478927C3E39258898@[172.16.2.50]> In-Reply-To: <50D1B7A2.5090909@omnilan.de> References: <50D1A2B2.6040204@omnilan.de> <50D1AB6A.402@omnilan.de> <50D1B7A2.5090909@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--On December 19, 2012 13:48:34 +0100 Harald Schmalzbauer <h.schmalzbauer@omnilan.de> wrote: > schrieb Harald Schmalzbauer am 19.12.2012 12:56 (localtime): >> ... >>> >>> I have more oddities I wanted to check with jails and lagg-interfaces >>> together with VLANs, but I have no idea why I can't connect from one >>> jail to it's own IP(v4) anymore! >> Found out that defining a different FIB causes that behaviour in 9.1. >> But using a different FIB doesn't caus the same in 8.2! > > Easiest way to reproduce: > > Just do a ping on the host (not jail) > > setfib 0 ping anyLocalIP -> works > setfib 1 ping anyLocalIP -> doesn't work > > Anybody with 9.1 and ROUTINGTABLES in custom kernel out there who can't > confirm that? > > Turned out that 9.0-stable from Feb. 2012 doesn't show that problem. > So this problem seems to be introdued between 9.0 and 9.1. > Thanks, > > -Harry > > Works for me: # uname -a FreeBSD 9.1-PRERELEASE r243951: Fri Dec 7 02:29:14 CET 2012 # sysctl -a | grep fib net.my_fibnum: 0 net.add_addr_allfibs: 1 net.fibs: 2 # ifconfig sis1 sis1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=83808<VLAN_MTU,WOL_UCAST,WOL_MCAST,WOL_MAGIC,LINKSTATE> ... inet 176.57.193.193 netmask 0xfffffff0 broadcast 176.57.193.207 .... media: Ethernet autoselect (100baseTX <full-duplex>) status: active # setfib 0 ping 176.57.193.193 PING 176.57.193.193 (176.57.193.193): 56 data bytes 64 bytes from 176.57.193.193: icmp_seq=0 ttl=64 time=0.497 ms 64 bytes from 176.57.193.193: icmp_seq=1 ttl=64 time=0.481 ms ^C --- 176.57.193.193 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.481/0.489/0.497/0.008 ms # setfib 1 ping 176.57.193.193 PING 176.57.193.193 (176.57.193.193): 56 data bytes 64 bytes from 176.57.193.193: icmp_seq=0 ttl=64 time=0.912 ms 64 bytes from 176.57.193.193: icmp_seq=1 ttl=64 time=0.650 ms ^C --- 176.57.193.193 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.650/0.781/0.912/0.131 ms I have no kernel with both VIMAGE and ROUTINGTABLES so can test that, this has ROUTINGTABLES 2 /glz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7CCE5A5478927C3E39258898>