@louis2 said in Just installed the release; Something wrong with multicast !!!:
192.168.100.x arriving on
If your seeing source IPs of .100 on your .200 interface then you do not have isolation at L2.. plan an simple... There is no way for interface 192.168.100 to see traffic a device that is 192.168.200 and on a different L2 network... The only way you could see such traffic is if your not isolated at layer 2.
Or as mentioned you got something forwarding multicast traffic in your network.
Or you have something multihomed in your network, ie a leg in both networks and its sending traffic out the wrong interface. Which again would be lack of isolation at L2 ;) Anything that has legs in multiple networks better be a "router" or clearly know what your doing so it is not a security issue. And that it handles routing of its own traffic correctly.
My pc has legs in 2 networks.. But the 2nd leg is a SAN network between it and NAS.. There are only those 2 devices on that network, and that network is completely isolated from the rest of the network... Now it is possible that one of those devices for example might throw traffic out its normal LAN connection with a source IP of the SAN network.. But yup pfsense would not like that traffic, and prob throw up some logs about it.