Date: Thu, 28 Jun 2018 22:10:38 +0200 From: Dave Cottlehuber <dch@skunkwerks.at> To: freebsd-net@freebsd.org Subject: Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64 Message-ID: <1530216638.3576018.1423925808.069CD13B@webmail.messagingengine.com> In-Reply-To: <201805311407.w4VE7SpX076936@pdx.rh.CN85.dnsmgr.net> References: <201805311407.w4VE7SpX076936@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > # invalid IP
> > > >
> > > > TLDR 10.241.0.0/16 is technically not a valid host IP but it has
> > > obviously worked in the past.
Just following this up, kmacy@'s recent commits resolved this - thanks!
Finally, I came up with this, as a way of keeping the "symmetry" of the
0.0 and still if I read the RFC correctly, have a valid host IP:
# jail networks
cloned_interfaces="${cloned_interfaces} lo1"
ifconfig_lo1="inet 10.241.0.0/15" --- should be a host mask x.1.0.0
ifconfig_lo1_aliases="inet 10.241.0.1-15/32"
# ifconfig lo1
lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128 tentative
inet 10.241.0.0 netmask 0xfffe0000
inet 10.241.0.1 netmask 0xffffffff
inet 10.241.0.2 netmask 0xffffffff
inet 10.241.0.3 netmask 0xffffffff
inet 10.241.0.4 netmask 0xffffffff
inet 10.241.0.5 netmask 0xffffffff
inet 10.241.0.6 netmask 0xffffffff
...
thanks everybody for the patches and the insight.
FWIW the alternative (original breaking config) also works again:
# jail networks
cloned_interfaces="${cloned_interfaces} lo1"
ifconfig_lo1_aliases="inet 10.241.0.1-15/15"
A+
Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1530216638.3576018.1423925808.069CD13B>