gre and MONITOR

Chip Marshall chip at 2bithacker.net
Wed May 8 15:54:57 UTC 2013


It appears the MONITOR flag doesn't work on gre interfaces.

I have a GRE tunnel set up between a FreeBSD 8.2-RELEASE box and a
Juniper router.

Config on the FreeBSD end:

gre0: flags=4b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST,MONITOR> metric 0 mtu 1476
	tunnel inet 10.162.163.133 --> 10.162.163.131
	inet6 fe80::20c:29ff:fe9f:de64%gre0 prefixlen 64 scopeid 0x6
	inet 10.200.0.2 --> 10.200.0.1 netmask 0xfffffffc
	nd6 options=3<PERFORMNUD,ACCEPT_RTADV>

Config on the Juniper end:

tunnel {
    source 10.162.163.131;
    destination 10.162.163.133;
}
family inet {
    address 10.200.0.1/30;
}

And from the Juniper, I am able to ping the 10.200.0.2 IP on the
FreeBSD end of the GRE tunnel. As I understand it, this shouldn't
happen with the MONITOR flag there, right?

> ping 10.200.0.2 rapid
PING 10.200.0.2 (10.200.0.2): 56 data bytes
!!!!!
--- 10.200.0.2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.265/0.297/0.382/0.043 ms

-- 
Chip Marshall <chip at 2bithacker.net>
http://2bithacker.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20130508/af96bdd4/attachment.sig>


More information about the freebsd-net mailing list