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

    DLNA across VLAN subnets with IGMP Proxy not working

    Scheduled Pinned Locked Moved pfSense Packages
    14 Posts 3 Posters 7.4k 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.
    • R
      Rai80
      last edited by

      Try rules

      On int VLAN A:
      Source VLAN B subnet Dest Any Allow with IP options

      On int VLAN B:
      Source VLAN A subnet Dest Any Allow with IP options

      If that's working you can narrow down your rules

      S 1 Reply Last reply Reply Quote 1
      • S
        snow @Rai80
        last edited by snow

        @rai80

        Unfortunately no difference.
        I already placed a rule on both interfaces to allow all IP4 traffic from any to any with no luck.
        Seems to be there is anything wrong with the IGMP Proxy.

        1 Reply Last reply Reply Quote 0
        • R
          Rai80
          last edited by Rai80

          Hmm, your configuration seems right. Online I see more people having trouble getting DLNA to work between Vlans's with Igmpproxy. See https://forum.netgate.com/topic/114743/dlna-over-subnets-igmp-proxy-multicast-routing/8

          1 Reply Last reply Reply Quote 0
          • R
            Rai80
            last edited by

            You can try pimd instead of igmpproxy. See:
            https://freebsd.pkgs.org/11/freebsd-ports-quarterly-amd64/pimd-2.3.2.txz.html
            https://github.com/troglobit/pimd

            Install with pkg add http://pkg.freebsd.org/FreeBSD:11:amd64/quarterly/All/pimd-2.3.2.txz

            S 1 Reply Last reply Reply Quote 0
            • S
              snow @Rai80
              last edited by

              @rai80

              Thanks dude, with pimd it's working fine.
              Perfect solution ☺

              R 1 Reply Last reply Reply Quote 0
              • R
                Rai80 @snow
                last edited by

                @snow Nice!

                Can u post your pimd.conf? I tried earlier about the same without succes. Maybe I give it another try :)

                S 1 Reply Last reply Reply Quote 0
                • S
                  snow @Rai80
                  last edited by snow

                  @rai80

                  Currently I'm using an unmodified pimd.conf with one exception concerning the interface section:

                  phyint re0 disable
                  phyint em0.30 enable
                  phyint em0.31 enable
                  phyint em0.32 disable
                  phyint em0.33 disable
                  phyint em0.34 disable
                  phyint em0.35 disable
                  phyint em0.36 enable
                  phyint pppoe0 disable
                  phyint ovpns1 disable

                  As shown above it's only enabled on Vlan interface em0.30, em0.31 and em0.36.
                  Because all non-loopback multicast capable interfaces are enabled by default, you also need to disable the interfaces which are not required for multicast explicitly.

                  The only thing I noticed, it takes currently 20 - 30 seconds until the DLNA server will be found on the clients.
                  For an example:

                  Android with BubbleUPnP: 20 sec
                  IPad with VLC: 30 sec

                  I think this behaviour can be optimized in pimd.conf.

                  1 Reply Last reply Reply Quote 0
                  • R
                    Rai80
                    last edited by

                    Thx.

                    I think it has something to do with the default timers.

                    QinnQ 1 Reply Last reply Reply Quote 0
                    • QinnQ
                      Qinn @Rai80
                      last edited by

                      Maybe a long shot, but I'm having problems using IGMPproxy. I am getting

                      The IGMP message was local multicast. Ignoring. 
                      

                      did a

                      igmpproxy --vv 
                      

                      but I still can't figure this error message out. So I "think" that the discovery (239.255.255.250 SSDP ) of the devices won't traverse over the IGMP proxy and thus they cannot connect across VLAN's. I tried PIMD, but alas no avail.

                      Can someone help or point me in the right direction.

                      Cheers Qinn

                      1 Reply Last reply Reply Quote 0
                      • R
                        Rai80
                        last edited by Rai80

                        Can you post your igmpproxy.conf and pimd.conf ?

                        And your network overview.

                        QinnQ 1 Reply Last reply Reply Quote 1
                        • QinnQ
                          Qinn @Rai80
                          last edited by

                          @rai80 Thanks for your reply, I added the conf files

                          In the pimd config I only added the devices I wanted disabled. So there remains phyint igb1.1005 and phyint igb1.1010 ( there is no 1006 and 1009 VLAN)

                          I copied pimd.conf to

                          /var/etc
                          

                          and started pimd with

                           pimd -d -c /var/etc/pimd.conf
                          

                          I hope it helps, thanks in advance for your time

                          Cheers Qinn

                          [0_1546340228249_igmpproxy.conf](Uploading 100%) 0_1546340265865_igmp.zip

                          1 Reply Last reply Reply Quote 0
                          • QinnQ
                            Qinn
                            last edited by Qinn

                            Update....I was far too quick in my judgement, after say 25 sec it worked 👍 . Pimd did it, with the above conf, but now I would like to know why, for instance what I don't understand is why don't I have to define an up- or downstream. Could you give me some insight how and why this works.

                            Cheers Qinn

                            QinnQ 1 Reply Last reply Reply Quote 0
                            • QinnQ
                              Qinn @Qinn
                              last edited by

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