Hi!
Wouldn't it be better to not use the bridge and use (multicast-)routing
and pf to solve your problem?
Multicast routing with "dvrmpd" is tested with pf, does not work. the
same thing happens, if streamX is allowed to pass out on vlanX and
streamY is allowed to pass out on vlanY, result is pretty similar:
vlanX outputs both streams (streamX, streamY) and the same thing with
vlanY. pf is not 100% percent multicast compat.?
Since these days i tried out anyway how multicast routing is and decided
to set up also similar configuration as described in the beginning of
this thread assuming for pf multicast traffic is no different from any
other 'ordinary' traffic.
I believe the reason why with a rule like this
pass out quick on vlan1101 proto udp from any to 239.16.1.1
you see the same traffic on every interface which is set up to multicast
is because how pf decides to pass packets. Default state-policy is
floating and it means that decision to pass traffic is based on packet's
direction and src and dst ip and ports and not on what interface packet
leaves (or enters). Normally this is ok and as i understand this
approach for example saves memory not to keep information which excact
interface is used for passing. But problem arises with multicast traffic
as src ja dst addresses and ports are the same. I tried and adding 'keep
state (if-bound)' seems to solve the problem.
Imre
Actually i experimented with tags, something like this
..
pass in quick on $if_onelan inet to 239.x.x.x keep state (if-bound) tag MC
pass out quick on $if_otherlan keep state (if-bound) tagged MC
...
