Hello!
Recently my home network got additional network connection, so I
decided to try using Zebra to see if the whole set-up would be simpler
and easier to maintain. During the test period I've noticed that
Netfilter "sees" locally originated multicast traffic as
external-incoming one:
[125488.045542] RAW: M: IN=eth3 OUT= MAC= SRC=172.19.20.2
DST=224.0.0.9 LEN=512 TOS=0x10 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP
SPT=520 DPT=520 LEN=492
(Caught with such set-up:
*raw
-A PREROUTING -d 224.0.0.9/32 -i eth3 -m pkttype --pkt-type multicast
-j LOG --log-prefix "RAW: M: " --log-ip-options)
IP-addr. "172.19.20.2" is a local one; it's assigned to interface "eth3".
I dug a bit more and can suppose that Zebra's RIPv2 uses
IP_MULTICAST_LOOP flag. But then another question arises: is there a
good/proper way to detect such kind a traffic with Netfilter? I mean
such a way that would exclude possibilities for bogus traffic being
treated as IP_MULTICAST_LOOP, i.e., how to unambiguously classify own
multicast-loop traffic with Netfilter?
--
End of message. Next message?
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
