@michmoor said in Just installed the release; Something wrong with multicast !!!:
Generally speaking this isnt really an issue
Unless the user has on purpose setup something to send multicast across L2 segments, then it is an issue. Because they don't actually have the isolation they think they do.
If they for some reason want to circumvent the L2 barrier by design, then sure its not really an issue in the fact they are doing it on purpose. But if they have not done it on purpose, then yes it is a issue.
What I am trying to determine is this by design, or by accident. But I agree if I am sending multicast across L2 boundaries then yeah I would expect to see multicast hit a interface with a different source IP.. Just disable logging of that noise..
But if pfsense is the forwarder of this multicast, its interfaces should be seeing it..
X -- pfsense -- Y
If pfsense forwards multicast on X to Y.. Where how would pfsense be seeing multicast to its own interface from a different source network? So if X is seeing multicast from Y, points to the L2 barrier being circumvented elsewhere in the network.