Assigning physical interfaces ...

[Patrick M. Hausen]

Hi all, dear Franco and colleagues,

could you clarify a bit under which circumstances this action is necessary? I got that when VLANs are defined on top of a physical interface then for consistency reasons the hardware offloading is not disabled anymore on the physical one by default. So far so good.

I have updated two production firewalls that depend heavily on VLANs without being aware of that requirement. Wasn't that obvious to me although I am one of those guys who reads release notes ;)

But ... the two systems in my responsibility also use LACP "between" the physical interfaces and the VLANs. And it looks like in that case hardware offloading IS disabled without any special action:

Code Select Expand

ix0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4803828<VLAN_MTU,JUMBO_MTU,WOL_UCAST,WOL_MCAST,WOL_MAGIC,NOMAP>


So ... an exhaustive documentation stating what exactly happens when would be most welcome :)

Kind regards, excellent release so far!
Patrick

[franco]

I think LAGG is enforcing its settings via kernel on its parents... I've seen this with happen with MTU so would make sense the flags are also synced to parent devices? It's easy enough to try and alter lagg0 (or whichever lagg device this is) with ifconfig.


Cheers,
Franco

[Patrick M. Hausen]

Makes sense (he, he ...  8)) Thanks.

[Andreas_]

I played with this, and apparently (as Franco stated) they're 'somehow' applied. But this means, if you change settings (tso or so), the lagg members will take the settings only on reboot from global settings, no possibility to tweak the hardware online or individually.