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

    IGMP Proxy bus error (Core dumped)

    Scheduled Pinned Locked Moved pfSense Packages
    9 Posts 4 Posters 3.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.
    • F
      ffx64
      last edited by

      Hi all,

      the default packaged igmpproxy service crash : Bus error (core dumped)
      on my pfsense 2.2.6 when i setup more than 30 vlan networks interfaces on the same
      lagg interface (link aggregation).

      i use 4 physical interfaces for the lagg : em0, em1, em2, em3

      With only 30 vlan networks interfaces igmpproxy works fine.

      But with 31 vlan networks interfaces igmpproxy crash.

      I tried to start the service from the commande line :```
      /usr/local/sbin/igmpproxy -d4 -c /tmp/igmpproxy.conf

      
      It ends with : Bus error (core dumped)
      
      Is it a igmpproxy limitation or may be a kernel limitation ?
      
      Thanks.
      
      ffx64
      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        There are a couple known crashes with the version of igmpproxy on 2.2.x and before. I don't recall seeing that specific one, though. If you can, you might give 2.3 a spin and see if it's better, there is a much newer version of igmpproxy there that didn't get patched up a lot like the old one did.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • F
          ffx64
          last edited by

          Well,

          According to this post https://forum.pfsense.org/index.php?topic=93293.0, i installed the latest version:

          pkg
          pkg update
          pkg install igmpproxy
          

          but now, as mentioned in this thread, https://forum.pfsense.org/index.php?topic=93293.msg543938#msg543938 ,the vlans interfaces is not recognized anymore.

          The next version of pfsense (2.3)do not seem to be a solution with the newer version of igmpproxy.

          Am i wrong ?

          Thanks

          1 Reply Last reply Reply Quote 0
          • C
            Chefkoch009
            last edited by

            Hi @ all,

            same here. After Upgrading to Version 2.3 the igmpproxy wan't start.

            [2.3-RELEASE][admin@pfSense.localhost.local]/root: igmpproxy -vv -d /tmp/igmppr                                                                                                             Searching for config file at '/tmp/igmpproxy.conf'
            Config: Quick leave mode enabled.
            Config: Got a phyint token.
            Config: IF: Config for interface lagg0_vlan50.
            Config: IF: Got downstream token.
            Config: IF: Got ratelimit token '0'.
            Config: IF: Got threshold token '1'.
            Config: IF: Got altnet token 192.168.50.1/24.
            Config: IF: Altnet: Parsed altnet to 192.168.50/24.
            Config: IF: Got altnet token 224.0.0.1/4.
            Config: IF: Altnet: Parsed altnet to 224/4.
            IF name : lagg0_vlan50
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 2
            Allowednet ptr : 1017050
            Config: Got a phyint token.
            Config: IF: Config for interface lagg0_vlan60.
            Config: IF: Got downstream token.
            Config: IF: Got ratelimit token '0'.
            Config: IF: Got threshold token '1'.
            Config: IF: Got altnet token 192.168.60.1/24.
            Config: IF: Altnet: Parsed altnet to 192.168.60/24.
            IF name : lagg0_vlan60
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 2
            Allowednet ptr : 1017080
            Config: Got a phyint token.
            Config: IF: Config for interface re0.
            Config: IF: Got disabled token.
            IF name : re0
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 0
            Allowednet ptr : 0
            Config: Got a phyint token.
            Config: IF: Config for interface lagg0_vlan1.
            Config: IF: Got disabled token.
            IF name : lagg0_vlan1
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 0
            Allowednet ptr : 0
            Config: Got a phyint token.
            Config: IF: Config for interface lagg0_vlan10.
            Config: IF: Got disabled token.
            IF name : lagg0_vlan10
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 0
            Allowednet ptr : 0
            Config: Got a phyint token.
            Config: IF: Config for interface lagg0_vlan20.
            Config: IF: Got disabled token.
            IF name : lagg0_vlan20
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 0
            Allowednet ptr : 0
            Config: Got a phyint token.
            Config: IF: Config for interface lagg0_vlan30.
            Config: IF: Got disabled token.
            IF name : lagg0_vlan30
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 0
            Allowednet ptr : 0
            Config: Got a phyint token.
            Config: IF: Config for interface lagg0_vlan40.
            Config: IF: Got disabled token.
            IF name : lagg0_vlan40
            Next ptr : 0
            Ratelimit : 0
            Threshold : 1
            State : 0
            Allowednet ptr : 0
            buildIfVc: Interface re0 Addr: 31.17.225.215, Flags: 0xffff8843, Network: 31.17.225/24
            buildIfVc: Interface lo0 Addr: 127.0.0.1, Flags: 0xffff8049, Network: 127/8
            buildIfVc: Interface lagg0_vlan1 Addr: 172.16.1.1, Flags: 0xffff8843, Network: 172.16.1/24
            buildIfVc: Interface lagg0_vlan10 Addr: 192.168.10.1, Flags: 0xffff8843, Network: 192.168.10/24
            buildIfVc: Interface lagg0_vlan20 Addr: 192.168.20.1, Flags: 0xffff8843, Network: 192.168.20/24
            Found config for re0
            Found config for lagg0_vlan1
            Found config for lagg0_vlan10
            Found config for lagg0_vlan20
            adding VIF, Ix 0 Fl 0x0 IP 0xd7e1111f re0, Threshold: 1, Ratelimit: 0
                    Network for [re0] : 31.17.225/24
            adding VIF, Ix 1 Fl 0x0 IP 0x010110ac lagg0_vlan1, Threshold: 1, Ratelimit: 0
                    Network for [lagg0_vlan1] : 172.16.1/24
            adding VIF, Ix 2 Fl 0x0 IP 0x010aa8c0 lagg0_vlan10, Threshold: 1, Ratelimit: 0
                    Network for [lagg0_vlan10] : 192.168.10/24
            adding VIF, Ix 3 Fl 0x0 IP 0x0114a8c0 lagg0_vlan20, Threshold: 1, Ratelimit: 0
                    Network for [lagg0_vlan20] : 192.168.20/24
            There must be at least 2 Vif's where one is upstream.
            
            

            Is there an other way for multicast routing?

            1 Reply Last reply Reply Quote 0
            • C
              Chefkoch009
              last edited by

              I use 7 VLAN's but only the first 3 VLAN's seem to be recognized.

              
              adding VIF, Ix 0 Fl 0x0 IP 0xd7e1111f re0, Threshold: 1, Ratelimit: 0
              adding VIF, Ix 1 Fl 0x0 IP 0x010110ac lagg0_vlan1, Threshold: 1, Ratelimit: 0
              adding VIF, Ix 2 Fl 0x0 IP 0x010aa8c0 lagg0_vlan10, Threshold: 1, Ratelimit: 0
              adding VIF, Ix 3 Fl 0x0 IP 0x0114a8c0 lagg0_vlan20, Threshold: 1, Ratelimit: 0
              
              There must be at least 2 Vif's where one is upstream.
              
              

              The Networrk with Tag 50(upstream) and 60 (downstream) are not working, but in prev release of pfsense.

              1 Reply Last reply Reply Quote 0
              • C
                Chefkoch009
                last edited by

                if i change the upstream and downstream down to the first 3 VLAN's, the igmpproxy starts without any problems.

                It seems that in any loop in the igmpproxy package is a problem with counting.

                1 Reply Last reply Reply Quote 0
                • C
                  Chefkoch009
                  last edited by

                  But the same igmpproxy worked well on prev. pf sense release. maybe there is a bug in the new pfsense 2.3 GUI?

                  can anybody confirm that?

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

                    @Chefkoch009:

                    But the same igmpproxy worked well on prev. pf sense release. maybe there is a bug in the new pfsense 2.3 GUI?

                    What do you mean by "same igmpproxy"?

                    AFAIK pfSense 2.3 is based on FreeBSD-10.3 which had some internal changes on the network side and contains a different version igmproxy as was included in 2.2.6.

                    1 Reply Last reply Reply Quote 0
                    • C
                      Chefkoch009
                      last edited by

                      Sorry… I mean the igmpproxy configuration.

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