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

    IGMP proxy no longer works reliably after 2.7.1 update

    Scheduled Pinned Locked Moved
    Routing and Multi WAN
    15
    80
    11.2k
    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
      Remie2000 @ninin06
      last edited by

      @ninin06 said in IGMP proxy no longer works reliably after 2.7.1 update:

      @vjizzle
      Do you think I can also downgrade to version 2.7.0?
      Because in this version I thought the IGMP proxy still worked without any problems.
      Or were there already problems and I really have to go to 2.6 until this bug is fixed?

      I didn't have any problems prior latest update. But I'm on PF+ instead of CE

      1 Reply Last reply Reply Quote 1
      • V
        vjizzle
        last edited by

        The previous version for me was pf+ 23.05.01 and igmp was functioning fine. With all the changes to the license model I decided to go back to pf CE 2.7. And now back to 2.6 because of igmp bug. If pf+ get's the igmp fix before 2.7 I am jumping the wagon to pf+ again :)

        1 Reply Last reply Reply Quote 1
        • M
          mistergefahrensucher
          last edited by

          Same here in PF+

          will give a try to extract the working version from 2.7.0

          M 1 Reply Last reply Reply Quote 1
          • M
            mistergefahrensucher @mistergefahrensucher
            last edited by

            @mistergefahrensucher sorry i meen PF+ 23.05

            R 2 Replies Last reply Reply Quote 1
            • R
              Remie2000 @mistergefahrensucher
              last edited by

              @mistergefahrensucher said in IGMP proxy no longer works reliably after 2.7.1 update:

              @mistergefahrensucher sorry i meen PF+ 23.05

              Please keep us posted, I'm craving for a solution. I even tought my wife to log into the firewall to reset igmp herself

              1 Reply Last reply Reply Quote 0
              • R
                Remie2000 @mistergefahrensucher
                last edited by Remie2000

                @mistergefahrensucher

                I've also created a separate bug report for the PF+ version to get it on the bug tracker of PFsense+.

                You can find it here (https://redmine.pfsense.org/issues/15065) , there is a big chance it will be merged with the 2.7.1 bug report.

                It would really help to also share your logs and other findings there to help the developers fix this issue.

                M 3 Replies Last reply Reply Quote 1
                • M
                  mistergefahrensucher @Remie2000
                  last edited by

                  @Remie2000

                  i will do my best. But i can't find the log. My knowledge is to small.
                  I have enabled verbose logging in IGMPProxy but i don't know where i can find the results.
                  Are they normally came in system Log -> general ?
                  Just right now i noticed the:
                  /usr/local/etc/igmpproxy.conf
                  is empty (looks like a copy from default). Is this right ?
                  I expected to see the things i have configured on the web GUI

                  1 Reply Last reply Reply Quote 0
                  • M
                    mistergefahrensucher @Remie2000
                    last edited by

                    @Remie2000
                    ok i found my /var/etc/igmpproxy.conf
                    this was working with 23.05 and now after some time it stops on one chanal.
                    Not always the same but when i restart the igmpproxy it work for some time.

                    ##------------------------------------------------------

                    Enable Quickleave mode (Sends Leave instantly)

                    ##------------------------------------------------------
                    quickleave
                    phyint pppoe0 upstream ratelimit 0 threshold 1
                    altnet 87.141.215.251/32
                    altnet 224.0.0.0/4

                    phyint ix0 downstream ratelimit 0 threshold 1
                    altnet 192.168.3.5/32

                    phyint igb0 downstream ratelimit 0 threshold 1
                    altnet 192.168.4.3/32

                    phyint igb1 disabled
                    phyint ix0.30 disabled
                    phyint ix1 disabled
                    phyint ix0.20 disabled

                    1 Reply Last reply Reply Quote 0
                    • M
                      mistergefahrensucher @Remie2000
                      last edited by

                      @Remie2000

                      yeeehaaa i found the LOG:

                      Dec 5 17:55:28 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.4.1 to 224.0.0.1
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.3.1 to 224.0.0.1
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.0.66 to 224.0.0.1
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.99.8 to 224.0.0.1
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.16 to 224.0.0.251
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: Updated route entry for 224.0.0.251 on VIF #1
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.16 to 239.255.255.250
                      Dec 5 17:55:33 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
                      Dec 5 17:55:34 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.2 to 239.255.255.250
                      Dec 5 17:55:34 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
                      Dec 5 17:55:34 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.2 to 224.0.0.252
                      Dec 5 17:55:34 raumgitter igmpproxy[15567]: Updated route entry for 224.0.0.252 on VIF #1
                      Dec 5 17:55:35 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.1 to 224.0.0.22
                      Dec 5 17:55:35 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
                      Dec 5 17:55:35 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.1 to 224.0.0.2
                      Dec 5 17:55:35 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
                      Dec 5 17:55:36 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.1 to 224.0.0.22
                      Dec 5 17:55:36 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
                      Dec 5 17:55:37 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.2
                      Dec 5 17:55:37 raumgitter igmpproxy[15567]: Updated route entry for 232.0.20.2 on VIF #0
                      Dec 5 17:55:37 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.2, InpVIf: 4
                      Dec 5 17:55:38 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.5 to 239.255.255.250
                      Dec 5 17:55:38 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
                      Dec 5 17:55:38 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.1 to 224.0.0.2
                      Dec 5 17:55:38 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
                      Dec 5 17:55:38 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.130 to 239.255.255.250
                      Dec 5 17:55:38 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
                      Dec 5 17:55:40 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 239.255.255.250
                      Dec 5 17:55:40 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #0
                      Dec 5 17:55:45 raumgitter igmpproxy[15567]: RECV Leave message from 192.168.4.3 to 224.0.0.2
                      Dec 5 17:55:45 raumgitter igmpproxy[15567]: Leaving group 232.0.20.2 on interface pppoe0
                      Dec 5 17:55:45 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.4.1 to 232.0.20.2
                      Dec 5 17:55:48 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.4.1 to 232.0.20.2
                      Dec 5 17:55:49 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.234
                      Dec 5 17:55:49 raumgitter igmpproxy[15567]: Inserted route table entry for 232.0.20.234 on VIF #0
                      Dec 5 17:55:49 raumgitter igmpproxy[15567]: Joining group 232.0.20.234 on interface pppoe0
                      Dec 5 17:55:50 raumgitter igmpproxy[15567]: RECV V3 member report from 84.171.92.84 to 224.0.0.22
                      Dec 5 17:55:50 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
                      Dec 5 17:55:50 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
                      Dec 5 17:55:52 raumgitter igmpproxy[15567]: RECV V3 member report from 84.171.92.84 to 224.0.0.22
                      Dec 5 17:55:52 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
                      Dec 5 17:55:55 raumgitter igmpproxy[15567]: Removing MFC: 87.141.215.251 -> 232.0.20.2, InpVIf: 4
                      Dec 5 17:55:55 raumgitter igmpproxy[15567]: Inserted route table entry for 232.0.20.2 on VIF #-1
                      Dec 5 17:55:59 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.234
                      Dec 5 17:55:59 raumgitter igmpproxy[15567]: Updated route entry for 232.0.20.234 on VIF #0
                      Dec 5 17:55:59 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.234
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Updated route entry for 232.0.20.234 on VIF #0
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: select() failure; Errno(4): Interrupted system call
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Got a interrupt signal. Exiting.
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Removing MFC: 87.141.215.251 -> 232.0.20.2, InpVIf: 4
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: MRT_DEL_MFC; Errno(49): Can't assign requested address
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Removing MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 232.0.20.234 on interface pppoe0
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 239.255.255.250 on interface pppoe0
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 224.0.0.251 on interface pppoe0
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 224.0.0.252 on interface pppoe0
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: All routes removed. Routing table is empty.
                      Dec 5 17:56:01 raumgitter igmpproxy[15567]: Shutdown complete....

                      R 1 Reply Last reply Reply Quote 0
                      • R
                        Remie2000 @mistergefahrensucher
                        last edited by

                        @mistergefahrensucher Thanks a lot for your feedback.

                        You can also find the log @ Status > System Logs > Routing

                        1 Reply Last reply Reply Quote 0
                        • N
                          ninin06
                          last edited by ninin06

                          @Remie2000
                          Your ticket has been added to mine and the target version has been set to 2.8.0 and 24.03.
                          https://redmine.pfsense.org/issues/15043

                          I now hope that these versions will be released as soon as possible.

                          V 1 Reply Last reply Reply Quote 1
                          • V
                            vjizzle @ninin06
                            last edited by

                            Release 24.03…wow. So the fix is targeted to be here somewhere in the next 6 months orso?

                            Is it possible to run the igmp proxy package from 2.6 on 2.7? That would be a workaround perhaps for the time being.

                            M M H 4 Replies Last reply Reply Quote 0
                            • M
                              michmoor LAYER 8 Rebel Alliance @vjizzle
                              last edited by michmoor

                              @vjizzle
                              Release fixes are estimations not hard deadlines. It could theoretically be pushed back for months or years so ive seen.
                              My advice, If possible, downgrade back to a working pfsense version. Not great advice i grant you but i dont know another solution.

                              Also i advice people on the following
                              https://www.netgate.com/supported-pfsense-plus-packages

                              Firewall: NetGate,Palo Alto-VM,Juniper SRX
                              Routing: Juniper, Arista, Cisco
                              Switching: Juniper, Arista, Cisco
                              Wireless: Unifi, Aruba IAP
                              JNCIP,CCNP Enterprise

                              V 1 Reply Last reply Reply Quote 0
                              • V
                                vjizzle @michmoor
                                last edited by

                                @michmoor

                                Thanks. I already downgraded tot pfsense 2.6 where everything is working fine. Now I will play the waiting game yes.

                                1 Reply Last reply Reply Quote 1
                                • U
                                  UlfMerbold
                                  last edited by

                                  My Workaround is far more simple

                                  Just set an cronjob for a time in the morning hours and stay at the CE2.7.1

                                  	/usr/local/sbin/pfSsh.php playback svc restart igmpproxy

                                  This fixes it for the day in my setup

                                  M V 2 Replies Last reply Reply Quote 0
                                  • M
                                    mistergefahrensucher @UlfMerbold
                                    last edited by

                                    @UlfMerbold

                                    i have done this but in my case it's doesn't help.
                                    These reason is if you change to often between 2 chanals in short time the proxy get messed up.
                                    I will try to install the older working igmproxy

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      mistergefahrensucher @vjizzle
                                      last edited by

                                      @vjizzle

                                      can you help me please how to install the older package ?

                                      V 1 Reply Last reply Reply Quote 0
                                      • V
                                        vjizzle @UlfMerbold
                                        last edited by

                                        @UlfMerbold said in IGMP proxy no longer works reliably after 2.7.1 update:

                                        My Workaround is far more simple

                                        Just set an cronjob for a time in the morning hours and stay at the CE2.7.1

                                        	/usr/local/sbin/pfSsh.php playback svc restart igmpproxy

                                        This fixes it for the day in my setup

                                        Restarting the igmp proxy works temporarily, but it happens again when changing channels a few times so not really a workable solution here.

                                        1 Reply Last reply Reply Quote 0
                                        • V
                                          vjizzle @mistergefahrensucher
                                          last edited by

                                          @mistergefahrensucher said in IGMP proxy no longer works reliably after 2.7.1 update:

                                          @vjizzle

                                          can you help me please how to install the older package ?

                                          I have not installed the older package, I just downgraded to pfsense 2.6 where igmp works fine. I also would like to know if it is possible to install the igmp package from 2.6 on 2.7.

                                          1 Reply Last reply Reply Quote 0
                                          • U
                                            UlfMerbold
                                            last edited by

                                            Since we are now at FreeBSD 14 i do'nt know if an install from an different Kernelversion works :/

                                            There must be a "newer" Version of igmpproxy (4.1.1), we should be on 4.1 originally on pfsense

                                            But since the versioning is a bit unloved by the maintainer, i dont know it fixes something from our mess...i'm not an programmer and while looking at the changes last two years, i've no clue what the problem is exactly

                                            Link Text Freshports says there is an new version

                                            Link Text FreeBSD Org too..

                                            But dont see any link to the package?

                                            the "normal" way to install would be

                                            pkg add -f "link to the repo"file.txz

                                            But as i sayed, i did'nt find any FreeBSD 14 Repo from

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