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

    IGMP Unstable on 2.3.x

    Scheduled Pinned Locked Moved
    2.3.3 Development Snapshots
    4
    9
    5.0k
    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.
    • T
      tohil
      last edited by

      Hi

      I'm using IGMP Proxy for IP-TV (Swisscom TV, Switzerland) it worked nearly like charm on 2.2.x but since upgrade (no im not using a VLAN Interface) the TV Stream stopps all few minutes.
      I have to switch the channel then, or watch TV with a 10 second jump to the past -> No Mulitcast stream anymore when watchin "recorded" content.

      somebody else expierncing that?

      Now  I had to connect the IP TV Bos direclty to the ISP router.

      thats what i have in the logs.

      Aug 4 22:55:42 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:55:40 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:55:38 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:47:50 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:47:47 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:47:45 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:47:43 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:38:42 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.
      Aug 4 22:38:41 igmpproxy 77036 The source address 192.168.5.130 for group 239.255.255.250, is not in any valid net for upstream VIF.

      but 192.168.5.0/24 is not the subnet for the proxy. i use 192.168.151.0/24 as TV DMZ. See screenshot

      regards tohil
      Unbenannt.PNG
      Unbenannt.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • E
        Eniqmatic
        last edited by

        Can you post your full settings and interface addresses? Are you using any VLAN's to do it?

        There is a bug located here: https://redmine.pfsense.org/issues/6099

        Having said that, I have IP TV for some channels and successfully use it on 2.3. I spent about 3 days getting it working though.

        1 Reply Last reply Reply Quote 0
        • T
          tohil
          last edited by

          Running pfsense on APU board.

          re0 is WAN Interface, without VLAN Tag
          re1 is used for internal Networks with tags
          re2 is used for IP-TV Subnet without VLAN Tag

          WAN is 192.168.199.2 and ISP Router in Front, which is not bridgeable
          re2 is 192.168.151.0/24

          regards tohil

          1 Reply Last reply Reply Quote 0
          • S
            sphillips
            last edited by

            i have successfully configured IPTV on pfsense 2.3.2 (took me a long time giving my very poor knowledge on networks)
            with that being said…

            i also have messages

            Aug 28 16:59:24  igmpproxy  90149  The source address 192.168.0.90 for group 239.255.255.250, is not in any valid net for upstream VIF.

            like it says on post above 192.168.0.90 is not part of igmp (its the ip of my personal computer) which is also connected on a diferent pfsense interface

            also if i turn on WIFI interface, igmp will fail to boot (if pfsense reboots) with the given error. reported https://redmine.pfsense.org/issues/6099 .

            There must be at least 2 Vif's where one is upstream.

            Edit: forgot to mention that i am using vlans
            wan is on vlan10
            Wan_iptv is on vlan20

            interfaces.jpg
            interfaces.jpg_thumb
            IGMP.jpg
            IGMP.jpg_thumb

            1 Reply Last reply Reply Quote 0
            • Raul RamosR
              Raul Ramos
              last edited by

              Hi

              @sphillips c'mon we appreciate you configuration details Interfaces, rules and IGMP for the IPTV stuff. Thnaks

              pfSense:
              ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
              Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
              NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

              1 Reply Last reply Reply Quote 0
              • S
                sphillips
                last edited by

                right.. i put in some prints but they're not there for some reason.

                i posted on here so i might give some usefull information about the querks happening with IGMP.
                for example the issue reported here https://redmine.pfsense.org/issues/6099 does not seem consistent since i have a working IGMP proxy on pfsense 2.3.2 configured with vlans but the problem does happen when i enable my wifi interface.

                And there are alot of spams like this

                Aug 29 09:43:24 igmpproxy 82930 The source address 192.168.0.90 for group 239.255.255.250, is not in any valid net for upstream VIF.
                Aug 29 09:44:17 igmpproxy 82930 The source address 192.168.0.90 for group 239.255.255.250, is not in any valid net for upstream VIF.
                Aug 29 09:45:11 igmpproxy 82930 The source address 192.168.0.90 for group 239.255.255.250, is not in any valid net for upstream VIF.
                Aug 29 09:46:05 igmpproxy 82930 The source address 192.168.0.90 for group 239.255.255.250, is not in any valid net for upstream VIF.
                Aug 29 09:46:59 igmpproxy 82930 The source address 192.168.0.90 for group 239.255.255.250, is not in any valid net for upstream VIF.

                re0_vlan10 - WAN interface
                re0_vlan20 - WAN_IPTV interface
                rl0 - LAN interface
                rl1 - LAN_IPTV interface

                @mais_um if youre looking to set up your own pfsense feel free to pm me i will help if i can.

                IGMP.jpg
                IGMP.jpg_thumb
                interfaces.jpg
                interfaces.jpg_thumb
                LAN_IPTV.jpg
                LAN_IPTV.jpg_thumb
                WAN.jpg
                WAN.jpg_thumb
                WAN_IPTV.jpg
                WAN_IPTV.jpg_thumb

                1 Reply Last reply Reply Quote 0
                • Raul RamosR
                  Raul Ramos
                  last edited by

                  Hi

                  Thanks @sphillips - is not for me (for now. I hope have a working config when fiber came in house ) a client on a cybercafe have fiber with IPTV i couldn't put pfsense working he use the ISP router that is a garbage.

                  Have you make some rules to pass traffic on any interface with or without advanced option "Allow IP options", "Allow packets with IP options to pass. Otherwise they are blocked by default. This is usually only seen with multicast traffic."? gateway changes?

                  Thanks again.

                  pfSense:
                  ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                  Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                  NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                  1 Reply Last reply Reply Quote 0
                  • S
                    sphillips
                    last edited by

                    WAN_IPTV start with everything open or with only protocols IGMP and UDP open, but enable logging so u can make better rules.
                    LAN_IPTV i am only using the default rule made by default from LAN (Default allow LAN to any rule) but changed to LAN_IPTV

                    both LAN_IPTV and WAN_IPTV have "allow IP options" enabled

                    and you might have to make static routes for the apps and on-demand stuff. what i did to find was leave WAN_IPTV on DHCP, let it grap an ip, check for all the routes in pfsense and take note of them to compare it, when i put it back to static.

                    but ill say it again im not savy on the subject im only curious about it, im sure there are better ways of doing it. drop me a pm on subject if needed i dont think this topic is for stuff like this.

                    1 Reply Last reply Reply Quote 0
                    • Raul RamosR
                      Raul Ramos
                      last edited by

                      No, this topic is not for that but i catch very few people with this version and working.

                      I believe i'm not very far from successfully put IPTV working with pFsense seeing your config. If I had IPTV at home i would test to exhaustion.
                      I'm putting this together for when i have the opportunity to test with some good intel.

                      Thanks, leaving and out.

                      pfSense:
                      ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                      Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                      NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post