Set MTU Size on VLAN Interface

[c-mu]

Hi,
I'm currently installing a hardware Firewall with OpnSense (20.1.2) and 10GBit NICs and I'm trying to set die MTU Size to 9000 on each VLAN interface.

But I get the following error:

Code Select Expand

The following input errors were detected:

    MTU of a vlan should not be bigger than parent interface.

I have to assign die Parent Device and let it unconfigured except MTU Size.

Next Thing: If I check die MTU Size via CLI, all Interfaces still have the default MTU1500. First if I change the MTU Size via CLI to 9000, I will get my full 10gbit speed.

It looks like something went wrong. The Networkcard is an IntelX710-DA4. Any Idea what goes wrong?

I also get an erro message on cli if something changed with the NIC Config like:

Code Select Expand

ixl0: aq_add_macvlan err -53, aq_error 14

or

Code Select Expand

WARNING: queue 0 appears to be hung!

Code Select Expand

WARNING: queue 2 appears to be hung!

But I dont see any negative effects.

[c-mu]

Could maybe a driver problem. But I'm unable to install the latest:

Intel's instructions:

Code Select Expand

7. If you want the driver to load automatically when the system is booted:

   cd ixgbe-x.x.x/src
   make
   make install

My output:

Code Select Expand

root@gw01:~/tmp/src # make
make: "/usr/share/mk/bsd.kmod.mk" line 12: Unable to locate the kernel source tree. Set SYSDIR to override.
root@gw01:~/tmp/src # make install
make: "/usr/share/mk/bsd.kmod.mk" line 12: Unable to locate the kernel source tree. Set SYSDIR to override.
root@gw01:~/tmp/src #

little googling says, that i have to check out the source tree via svn, but i'm not able to install svn too XD

[c-mu]

Okay my VLAN Parent device seems to be persistent with MTU9000, but not my VLAN childs :/

[c-mu]

mhh is it possible to set a @reboot cronjob? Then I would write a script, that change the MTU Sizes after a reboot.

I still dont have a solution for that problem :-/

[hbc]

It's not a cronjob and I assume, it should be triggered on every kind of (re)boot.
There is a syshook for start

https://docs.opnsense.org/development/backend/autorun.html

[c-mu]

Thank you, thats a workaround that works and I can live with.