Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Another IGMP proxy post

    Scheduled Pinned Locked Moved General pfSense Questions
    23 Posts 3 Posters 3.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      pr3dict
      last edited by

      Yeah I'm a little perplexed myself...

      I checked did a pcap for the other interface and didnt see any IGMP traffic.

      I could put them in the same subnet and see whats going on but I don't know if it'll make it past the switch as the switch will probably just route the traffic no?

      1 Reply Last reply Reply Quote 0
      • P
        pr3dict
        last edited by

        on another note I did another pcap but had medium details shown. It looks like the "server" is sending out upnp ssdp packets

        11:29:31.344213 IP (tos 0x0, ttl 4, id 7976, offset 0, flags [none], proto UDP (17), length 301)
    192.168.55.125.1900 > 239.255.255.250.1900: UDP, length 273
11:29:31.365150 IP (tos 0x0, ttl 4, id 7977, offset 0, flags [none], proto UDP (17), length 292)
    192.168.55.125.1900 > 239.255.255.250.1900: UDP, length 264
11:29:31.386168 IP (tos 0x0, ttl 4, id 7978, offset 0, flags [none], proto UDP (17), length 362)
    192.168.55.125.1900 > 239.255.255.250.1900: UDP, length 334
11:29:31.407139 IP (tos 0x0, ttl 4, id 7979, offset 0, flags [none], proto UDP (17), length 356)
    192.168.55.125.1900 > 239.255.255.250.1900: UDP, length 328
11:29:31.428197 IP (tos 0x0, ttl 4, id 7980, offset 0, flags [none], proto UDP (17), length 301)
    192.168.55.125.1900 > 239.255.255.250.1900: UDP, length 273
11:29:31.449146 IP (tos 0x0, ttl 4, id 7981, offset 0, flags [none], proto UDP (17), length 344)
    192.168.55.125.1900 > 239.255.255.250.1900: UDP, length 316
11:29:31.470155 IP (tos 0x0, ttl 4, id 7982, offset 0, flags [none], proto UDP (17), length 346)
    192.168.55.125.1900 > 239.255.255.250.1900: UDP, length 318
        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Just to be clear 55.125 is the TV here right?

          And is it in someway interactive or more like an advertising screen? It looks for video source and plays it as sooin as it;s powered up?

          Steve

          1 Reply Last reply Reply Quote 0
          • P
            pr3dict
            last edited by pr3dict

            55.125 is the video server. https://www.silicondust.com/images/hdhomerun/QS_HDHomeRun_PRIME.pdf

            The TV/client is on a separate subnet.

            https://www.silicondust.com/support/hdhomerun/testfail/upnp_multicast_recv/

            "HDHomeRun Setup triggers the HDHomeRun to send a series of SSDP NOTIFY packets to the 239.255.255.250 multicast group."

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Ah I see. It is the opposite way around to how I would usually expect. OK.

              There have been issues with the IGMP proxy on VLANs in the past but I thought they were mostly resolved.
              Do you see any errors in the system log when you start it?

              You might try stopping the service in the GUI and then starting it in debug mode at the command line:
              igmpproxy -d -vv /var/etc/igmpproxy.conf

              That will give you a lot of output. It will show if the groups are being joined correctly though.

              Steve

              1 Reply Last reply Reply Quote 0
              • P
                pr3dict
                last edited by

                So I did that. I don't know where it is outputting to but this is what happens when I do a pcap on full for the interface that the server is on.

                10:17:44.128444 00:18:dd:32:28:1b > 01:00:5e:00:00:16, ethertype IPv4 (0x0800), length 60: (tos 0xc0, ttl 1, id 0, offset 0, flags [DF], proto IGMP (2), length 40, options (RA))
    192.168.10.142 > 224.0.0.22: igmp v3 report, 1 group record(s) [gaddr 239.255.255.250 is_ex { }]
10:17:44.377428 00:18:dd:32:28:1b > 01:00:5e:00:00:16, ethertype IPv4 (0x0800), length 60: (tos 0xc0, ttl 1, id 0, offset 0, flags [DF], proto IGMP (2), length 40, options (RA))
    192.168.10.142 > 224.0.0.22: igmp v3 report, 1 group record(s) [gaddr 239.255.255.250 is_ex { }]

                Is the TTL being "1" going to cause an issue with forwarding it to the interface/vlan with the client on it?

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  It should be outputting the debug stuff at the command line where you started it. That should tell us if it's doing anything useful at all.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • P
                    pr3dict
                    last edited by

                    The only output is what is below:

                    Searching for config file at '/var/etc/igmpproxy.conf'
Config: Quick leave mode enabled.
Config: Got a phyint token.
Config: IF: Config for interface igb1.10.
Config: IF: Got upstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
Config: IF: Got altnet token 192.168.10.0/24.
Config: IF: Altnet: Parsed altnet to 192.168.10/24.
Config: IF: Got altnet token xxxxxxxxxx.
Config: IF: Altnet: Parsed altnet to xxxxxxxxx.
IF name : igb1.10
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 1
Allowednet ptr : e25000
Config: Got a phyint token.
Config: IF: Config for interface igb1.90.
Config: IF: Got downstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
Config: IF: Got altnet token 192.168.90.0/24.
Config: IF: Altnet: Parsed altnet to 192.168.90/24.
IF name : igb1.90
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : e25020
Config: Got a phyint token.
Config: IF: Config for interface igb0.
Config: IF: Got disabled token.
IF name : igb0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface igb1.
Config: IF: Got disabled token.
IF name : igb1
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface igb1.99.
Config: IF: Got disabled token.
IF name : igb1.99
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface ovpnc2.
Config: IF: Got disabled token.
IF name : ovpnc2
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface ovpns1.
Config: IF: Got disabled token.
IF name : ovpns1
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface vmx0.
Config: IF: Got disabled token.
IF name : vmx0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface igb1.60.
Config: IF: Got disabled token.
IF name : igb1.60
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface igb1.55.
Config: IF: Got disabled token.
IF name : igb1.55
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
buildIfVc: Interface igb0 Addr: xxxxx, Flags: 0xffff8843, Network: xxxxxxx
buildIfVc: Interface igb1 Addr: 192.168.1.177, Flags: 0xffff8a43, Network: 192.168.1/24
buildIfVc: Interface vmx0 Addr: 192.168.66.1, Flags: 0xffff8843, Network: 192.168.66/24
buildIfVc: Interface lo0 Addr: 127.0.0.1, Flags: 0xffff8049, Network: 127/8
buildIfVc: Interface igb1.99 Addr: 192.168.99.1, Flags: 0xffff8843, Network: 192.168.99/24
buildIfVc: Interface igb1.10 Addr: 192.168.10.1, Flags: 0xffff8a43, Network: 192.168.10/24
buildIfVc: Interface igb1.90 Addr: 192.168.90.1, Flags: 0xffff8a43, Network: 192.168.90/24
buildIfVc: Interface igb1.60 Addr: 192.168.60.1, Flags: 0xffff8843, Network: 192.168.60/24
buildIfVc: Interface igb1.55 Addr: 192.168.55.1, Flags: 0xffff8843, Network: 192.168.55/24
buildIfVc: Interface ovpns1 Addr: 192.168.91.1, Flags: 0xffff8051, Network: 192.168.91/24
buildIfVc: Interface ovpnc2 Addr: xxxxxxx, Flags: 0xffff8051, Network: xxxxxxxx
Found config for igb0
Found config for igb1
Found config for vmx0
Found config for igb1.99
Found config for igb1.10
Found config for igb1.90
Found config for igb1.60
Found config for igb1.55
Found config for ovpns1
Found config for ovpnc2
MC-Router API already in use; Errno(48): Address already in use
                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      @pr3dict said in Another IGMP proxy post:

                      Errno(48): Address already in use

                      Doesn't look good.

                      So you have a whole number of interfaces besides what you mentioned initially. You should try to get this working just on those interfaces initially before adding anything further.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • P
                        pr3dict
                        last edited by

                        I have a bunch of interfaces but I only have 1 of them listed for downstream and upstream...

                        f9a4d30b-800c-4a66-afe7-1b5d863f6f90-image.png

                        1 Reply Last reply Reply Quote 0
                        • P
                          pr3dict
                          last edited by pr3dict

                          I restarted the router and was able to start it up.

                          but i cant give the output because the site thinks its spam...

                          About to call timeout 4 (#0)
SENT Membership query   from 192.168.90.1    to 224.0.0.1
Sent membership query from 192.168.90.1 to 224.0.0.1. Delay: 10
Created timeout 5 (#0) - delay 10 secs
(Id:5, Time:10)
Created timeout 6 (#1) - delay 115 secs
(Id:5, Time:10)
(Id:6, Time:115)
RECV Membership query   from 192.168.90.1    to 224.0.0.1
The IGMP message was local multicast. Ignoring.
RECV V2 member report   from 192.168.90.100  to 224.0.0.252
Should insert group 224.0.0.252 (from: 192.168.90.100) to route table. Vif Ix : 1
Updated route entry for 224.0.0.252 o
```n VIF #1

                          Current routing table (Insert Route):
-----------------------------------------------------
#0: Dst: 224.0.0.251, Age:2, St: I, OutVifs: 0x00000002
#1: Dst: 224.0.0.252, Age:2, St: I, OutVifs: 0x00000002
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Post it on pastebin or similar and link to it.

                            1 Reply Last reply Reply Quote 0
                            • P
                              pr3dict
                              last edited by

                              Gooood idea!

                              https://pastebin.com/2j8MGRRF

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                Ok, so you moved the server from 192.168.55.125? Where is it now exactly?

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  pr3dict @stephenw10
                                  last edited by

                                  @stephenw10 Yeah sorry about that. The .10 subnet is where a lot of other clients are so while I was testing this I didnt want to have ot keep switching between .55 and .10...

                                  The server is now at 192.168.10.142

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    pr3dict
                                    last edited by

                                    Also if I flip the downstream and upstream interfaces this is the output for that...

                                    https://pastebin.com/uBpRFH9H

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      simon.lock @pr3dict
                                      last edited by

                                      @pr3dict

                                      Your set up of igmp proxy and firewall rules seem to be the similar to mine. Nothing is blocked in my logs between these subnets and advanced ip options are enabled.on the igmp firewall rules. The guys on the unifi forum have installed and used socat on their edge router to get hdhomerun recognised across subnets.

                                      https://community.ubnt.com/t5/EdgeRouter/Howto-HDHomerun-discovery-on-different-LAN-segment/m-p/2733241#M246671

                                      I'm watching this thread in the hope you discover an answer that will also help me. If I find a solution to this problem I'll post it here too. Good luck.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        simon.lock @pr3dict
                                        last edited by

                                        @pr3dict
                                        Thanks to meckhert on the unifi forum I've now managed to solve my hdhr problem by installing socat on a raspberry-pi that I already had on my private LAN. On the raspberry-pi I created and enabled a simple systemd service for socat so that it auto starts using the command meckhert listed.

                                        192.168.100.17 is the IP of my hdhr on my IoT network.

                                        socathdhr.service:

                                        [Unit]
                                        Description=socat hdhr
                                        After=network.target

                                        [Service]
                                        Type=simple
                                        User=root
                                        ExecStart= /usr/bin/socat -d -d -v udp4-recvfrom:65001,broadcast,fork udp4-sendto:192.168.100.17:65001
                                        Restart=on-failure
                                        RestartSec=10

                                        [Install]
                                        WantedBy=multi-user.target

                                        I hope this helps.

                                        1 Reply Last reply Reply Quote 1
                                        • First post
                                          Last post
                                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.