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
    10.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.
    • V
      vjizzle
      last edited by

      Same problem here. Restarting igmp service fixes it temporarily.

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

        same here :(

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

          I encounter the same problems with IGMP proxy.
          This happens since 23.09 and no configuration change has been done for months except the upgrade to 23.09.

          Seems IGMP proxy package has some problems

          Nov 30 17:37:53	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 08:01:41	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 06:52:27	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 06:51:55	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 06:09:22	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 20:13:24	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 20:12:44	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 12:16:30	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 12:16:30	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 06:36:26	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 06:35:52	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 19:48:36	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 19:31:57	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:37:00	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:22:51	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:22:11	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:11:43	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:11:43	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:10:50	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:10:50	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 10:34:55	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 08:33:22	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 08:32:48	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 08:18:17	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 07:14:32	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address

          I also see the same behavious when switching channels.

          alt text

          R 1 Reply Last reply Reply Quote 3
          • R
            Rai80 @Remie2000
            last edited by

            @Remie2000 Same problem here. Seems igmpproxy quickleave is not working anymore.

            1 Reply Last reply Reply Quote 1
            • R
              Remie2000
              last edited by Remie2000

              There is a bug report here: https://redmine.pfsense.org/issues/15043

              I think it's best to report it there aswell

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

                I know it takes time to solve this, in the meantime watching tv is nearly impossible. If I go back to version 2.6, will I still get the igmp proxy version which was working then and there or will it just pull the current igmp proxy version?

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

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

                  I know it takes time to solve this, in the meantime watching tv is nearly impossible. If I go back to version 2.6, will I still get the igmp proxy version which was working then and there or will it just pull the current igmp proxy version?

                  If you export your current configuration in Diagnostics > Backup & Restore (with extra data, and without skip RRD data) you can clean install 2.6.x on your box and import the 2.7.x config on it.

                  It will run as usual again. Perhaps it is wise to set your DHCP back to ISC DHCP (Deprecated) before exporting to prevent possible errors because the new Kea DHCP is in your config. You can find this on System > Advanced > Networking

                  Hope this helps you

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

                    @Remie2000
                    I downgraded to pfsense 2.6, made sure the dhcp server was the ISC again. But importing an 2.7 config on 2.6 version of pfsense messed up the firewall config. Luckily I had backups from when I was running 23.05 plus and I was able to import that succesfully. IGMP works as expected again. I will wait for a proper fix for IGMP in version 2.7. Thank you.

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

                      @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?

                      R 1 Reply Last reply Reply Quote 1
                      • 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
                                            • First post
                                              Last post