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

    multicast inconsistant

    Scheduled Pinned Locked Moved General pfSense Questions
    49 Posts 6 Posters 5.8k 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.
    • M
      maximushugus
      last edited by

      Also if it can help, here is netstat -g results at different moment during the problem :

      Before lauching igmpproxy :

      netstat -g
      
      IPv4 Virtual Interface Table is empty
      
      IPv4 Multicast Forwarding Table is empty
      
      
      IPv6 Multicast Interface Table is empty
      
      IPv6 Multicast Forwarding Table is empty
      

      After starting igmpproxy but before asking for the stream on my PC :

      netstat -g
      
      IPv4 Virtual Interface Table
       Vif   Thresh   Local-Address   Remote-Address    Pkts-In   Pkts-Out
        0         1   192.168.3.1                             0          0
        1         1   192.168.99.1                            0          0
        2         1   109.11.243.7                            0          0
        3         1   192.168.4.253                           0          0
      
      IPv4 Multicast Forwarding Table
       Origin          Group             Packets In-Vif  Out-Vifs:Ttls
       192.168.3.31    224.2.127.254           0    2    0:1
       192.168.3.4     239.255.255.250         0    2    0:1
      
      

      After asking for the multicast stream on my PC and receiving the stream :

      netstat -g
      
      IPv4 Virtual Interface Table
       Vif   Thresh   Local-Address   Remote-Address    Pkts-In   Pkts-Out
        0         1   192.168.3.1                             0      16716
        1         1   192.168.99.1                            0          0
        2         1   109.11.243.7                        16716          0
        3         1   192.168.4.253                           0          0
      
      IPv4 Multicast Forwarding Table
       Origin          Group             Packets In-Vif  Out-Vifs:Ttls
       192.168.3.31    224.2.127.254           0    2    0:1
       77.130.48.82    233.136.0.202       16716    2    0:1
       192.168.3.18    239.255.255.250         0    2    0:1
       192.168.3.4     239.255.255.250         0    2    0:1
      
      
      IPv6 Multicast Interface Table is empty
      
      IPv6 Multicast Forwarding Table is empty
      
      

      After stopping the stream on my PC :

      netstat -g
      
      IPv4 Virtual Interface Table
       Vif   Thresh   Local-Address   Remote-Address    Pkts-In   Pkts-Out
        0         1   192.168.3.1                             0      16716
        1         1   192.168.99.1                            0          0
        2         1   109.11.243.7                        16716          0
        3         1   192.168.4.253                           0          0
      
      IPv4 Multicast Forwarding Table
       Origin          Group             Packets In-Vif  Out-Vifs:Ttls
       192.168.3.31    224.2.127.254           0    2    0:1
       77.130.48.82    233.136.0.202       16716    2    0:1
       192.168.3.18    239.255.255.250         0    2    0:1
       192.168.3.4     239.255.255.250         0    2    0:1
      
      
      IPv6 Multicast Interface Table is empty
      
      IPv6 Multicast Forwarding Table is empty
      
      

      And if I try again to ask for the multicast stream on my PC :

      netstat -g
      
      IPv4 Virtual Interface Table
       Vif   Thresh   Local-Address   Remote-Address    Pkts-In   Pkts-Out
        0         1   192.168.3.1                             0      16716
        1         1   192.168.99.1                            0          0
        2         1   109.11.243.7                        16716          0
        3         1   192.168.4.253                           0          0
      
      IPv4 Multicast Forwarding Table
       Origin          Group             Packets In-Vif  Out-Vifs:Ttls
       192.168.3.31    224.2.127.254           0    2    0:1
       77.130.48.82    233.136.0.202       16716    2    0:1
       192.168.3.18    239.255.255.250         0    2    0:1
       192.168.3.4     239.255.255.250         0    2    0:1
      
      
      IPv6 Multicast Interface Table is empty
      
      IPv6 Multicast Forwarding Table is empty
      
      
      1 Reply Last reply Reply Quote 0
      • M
        maximushugus
        last edited by

        Just to update, I still have the problem.
        But I installed and properly configured PIMD, disabling IGMP proxy.

        With this configuration I have the exact same problem : I only see multicast with IPv4 source of my pfSense, and MDNS, (224.0.0.251) from my lan and multicast leave group but not multicast join group from my lan.

        So I this the problem is in pfSense itself and not in IGMPproxy nor PIMD

        Also if from a PC on my lan I ping a multicast 224.0.0.2, I can see this on a capture on pfSense.

        That's really weird

        1 Reply Last reply Reply Quote 0
        • M
          maximushugus
          last edited by

          I found I have the same problem as discribed here

          I have the same configuration with a LAGG of ixl0 and ixl1
          I suspect this is the problem.
          I get a lot of those errors

          pfSense kernel: ixl1: Disabled multicast promiscuous mode
          

          when enabling or disabling any multicast program (avahi, igmpproxy or pimd), even if I disable every program

          1 Reply Last reply Reply Quote 0
          • M
            maximushugus
            last edited by

            Ok I think I found the problem : it looks as a freebsd kernel bug with Intel x710 NIC.

            Here is the same problem in OPNsense : link

            Here is the Github OPNsense problem : link

            In OPNsense by reverting this freebsd commit it resolve the problem (see here)

            Can someone open an issue for next pfsense ?
            Does someone have skills to compile a pfsense kernel without the faulty commit ?

            Thanks ?

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Hmm, surprised you can't disable that kind of hardware offloading.🤔

              Since it can only handle 128 addresses and has a mode where it stops filtering in hardware when it goes above that anyway.....

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by stephenw10

                Seems to be setup with vlan hw filtering. Did you try disabling that?

                Like: ifconfig ixl0 -vlanhwfilter

                M 1 Reply Last reply Reply Quote 0
                • M
                  maximushugus @stephenw10
                  last edited by

                  @stephenw10 It looks as if I cannot disable vlan hw filtering because if I run this command the interface doesn't go up anymore until I restart

                  1 Reply Last reply Reply Quote 0
                  • M
                    maximushugus
                    last edited by

                    I created the bug in pfSense bugtracker : here

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Hmm, that's odd. Are you using VLANs on that? Do they all fail if so?

                      1 Reply Last reply Reply Quote 0
                      • M
                        maximushugus
                        last edited by

                        I have a LAG with both ixl0 and ixl1.
                        And on top of this LAG if have multiple VLANs.
                        As far as I entered this command for ixl0, every VLANs was inaccessible. I had to restart pfSense.
                        Then for ixl0 in ifconfig I had "satus : no carrier".
                        I entered :

                        ifconfig ixl0 vlanhwfilter
                        

                        and everything came back normal

                        dennypageD 1 Reply Last reply Reply Quote 0
                        • dennypageD
                          dennypage @maximushugus
                          last edited by

                          @maximushugus The very first step in testing / problem isolation should be removing the lag. Most especially when looking at hardware filtering.

                          1 Reply Last reply Reply Quote 1
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Mmm, I had my device in a lagg when I tested it but I was accessing over it directly not using a VLAN

                            1 Reply Last reply Reply Quote 0
                            • M
                              maximushugus
                              last edited by

                              To update on this problem, it is solved with the CE 2.8 version

                              1 Reply Last reply Reply Quote 1
                              • M maximushugus referenced this topic on
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.