multicast inconsistant

maximushugus

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

maximushugus

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

maximushugus

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 ?

stephenw10

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.....

stephenw10

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

Like: ifconfig ixl0 -vlanhwfilter

maximushugus

@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

maximushugus

I created the bug in pfSense bugtracker : here

stephenw10

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

maximushugus

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

dennypage

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

stephenw10

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

maximushugus

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