27 Apr
2017
27 Apr
'17
1:42 p.m.
I'm running FreeBSD 10.3 as well, but I am using the kernel IPIP
encapsulation courtesy of gif(4) interfaces. Here's my tunnel to amprgw:
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
options=80000<LINKSTATE>
tunnel inet 75.101.96.109 --> 169.228.66.251
inet 44.4.39.8 --> 44.0.0.1 netmask 0x0
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
Ignore the inner netmask (0x0); the routing table on my host is set up so
that these interfaces basically run unnumbered. Here's a small snippet of
the 958 lines of my netstat -rn -f inet:
Destination Gateway Flags Netif Expire
default 75.101.96.1 UGS vlan0
44.0.0.1 link#8 UH gif0
44.2.2.0 link#430 UH gif421
44.2.2.0/24 gif421 U gif421
44.2.7.0 link#429 UH gif420
44.2.7.0/30 gif420 U gif420
44.2.10.0 link#428 UH gif419
44.2.10.0/29 gif419 U gif419
44.2.50.0 link#427 UH gif418
44.2.50.0/29 gif418 U gif418
44.4.2.152 link#426 UH gif417
44.4.2.152/29 gif417 U gif417
44.4.4.64 link#425 UH gif416
On Thu, 27 Apr 2017, Brian Kantor wrote:
I'm curious, what version of FreeBSD are you
running? Amprgw is a FreeBSD
10.3 host and it doesn't do this as far as I can tell. It does not use
the in-kernel IPIP encapsulation though.