gre and MONITOR
Hiroki Sato
hrs at FreeBSD.org
Fri May 10 07:29:42 UTC 2013
Chip Marshall <chip at 2bithacker.net> wrote
in <20130508155446.GB95890 at 2bithacker.net>:
ch> It appears the MONITOR flag doesn't work on gre interfaces.
ch>
ch> I have a GRE tunnel set up between a FreeBSD 8.2-RELEASE box and a
ch> Juniper router.
ch>
ch> Config on the FreeBSD end:
ch>
ch> gre0: flags=4b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST,MONITOR> metric 0 mtu 1476
ch> tunnel inet 10.162.163.133 --> 10.162.163.131
ch> inet6 fe80::20c:29ff:fe9f:de64%gre0 prefixlen 64 scopeid 0x6
ch> inet 10.200.0.2 --> 10.200.0.1 netmask 0xfffffffc
ch> nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
ch>
ch> Config on the Juniper end:
ch>
ch> tunnel {
ch> source 10.162.163.131;
ch> destination 10.162.163.133;
ch> }
ch> family inet {
ch> address 10.200.0.1/30;
ch> }
ch>
ch> And from the Juniper, I am able to ping the 10.200.0.2 IP on the
ch> FreeBSD end of the GRE tunnel. As I understand it, this shouldn't
ch> happen with the MONITOR flag there, right?
The attached patch should fix this. Can you try it?
-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gre_monitor-20130510-1.diff
Type: text/x-patch
Size: 1090 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20130510/b4868f5b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20130510/b4868f5b/attachment.sig>
More information about the freebsd-net
mailing list