IGMP proxy joining wrong interface
-
I am trying to get multicast RTP working between a couple of tagged VLANs assigned to the em0 interface. I believe I have correctly set up the IGMP proxy so that the RTP source service (the IGMP proxy upstream) is on "LAN1" (192.168.0.x) and the recipient device (the IGMP proxy downstream) is on "LAN2" (10.0.20.x). Both LAN1 and LAN2 are assigned to em0. And the firewall rules are set to allow IGMP and the RTP stream over UDP.
The IGMP flow looks correct and packet captures show the RTP stream on LAN1 from the source is working. But there's no sign of the RTP stream on LAN2.
When the source starts a stream, the recipient device asks to join the multicast as expected, but I noticed that PFSense appears to join the em1 interface to the multicast instead of em0/LAN2. The logs are as follows:
igmpproxy: Note: RECV V2 member report from 10.0.20.13 to 224.0.0.111 (ip_hl 24, data 8)
igmpproxy: Note: joinMcGroup: 224.0.0.111 on em1
igmpproxy: Note: RECV V2 member report from 10.0.20.13 to 224.0.0.111 (ip_hl 24, data 8)
igmpproxy: Note: RECV V2 member report from 192.168.0.1 to 224.0.0.111 (ip_hl 24, data 8)
igmpproxy: Note: The IGMP message was from myself. Ignoring.
igmpproxy: Note: RECV V2 member report from 192.168.0.1 to 224.0.0.111 (ip_hl 24, data 8)
igmpproxy: Note: The IGMP message was from myself. Ignoring.Am I correct in assuming that the IGMP proxy can only handle proxying between different interfaces, not between VLANs sharing the same network port? Is the only solution to use a separate network interface?
Thanks!
-
bump
-
Which version of pfSense (and and which platform) are you using?
-
We're currently running:
2.1.5-RELEASE (amd64)
built on Mon Aug 25 07:44:45 EDT 2014
FreeBSD 8.3-RELEASE-p16 -
bump
Is it true that the IGMP proxy can only handle proxying between different interfaces, not between VLANs sharing the same network port?
Thanks.