How to setup VLANs within FreeNAS 11.3

[listhor]

@listhor

Although I've read your problem, I don't know if I totally understand what you are describing:
What kind of unrelated changes in network settings?

I have multiple interfaces available in Freenas and i.e. when I change IP address of one of them (not being a part of any bridges or lagg) and save it, all vnet based jails are affected. When I had them on interface with shared IPs (iocage set ip4_addr="igb0|172.16.1.3/26"), it never had happened. It seems that in my case, vnet is a bit broken...?
Config:

Code:

igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: LAN3
    options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    hwaddr ac:1f:6b:d7:fb:c6
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
vmx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: storage net esxi
    options=60039b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,TSO6,RXCSUM_IPV6,TXCSUM_IPV6>
    ether 00:0c:29:eb:9e:f5
    hwaddr 00:0c:29:eb:9e:f5
    inet 10.55.1.2 netmask 0xffff0000 broadcast 10.55.255.255
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
vmx1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
    options=60039b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,TSO6,RXCSUM_IPV6,TXCSUM_IPV6>
    ether 00:0c:29:eb:9e:ff
    hwaddr 00:0c:29:eb:9e:ff
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
igb1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: LAN2
    options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    hwaddr ac:1f:6b:d7:fb:c5
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
igb2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: LAN4
    options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c7
    hwaddr ac:1f:6b:d7:fb:c7
    inet 172.17.0.9 netmask 0xffffff00 broadcast 172.17.0.255
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
    inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
    inet 127.0.0.1 netmask 0xff000000
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
    groups: lo
lagg4095: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: Trunk
    options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
    groups: lagg
    laggproto lacp lagghash l2,l3,l4
    laggport: igb0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
    laggport: igb1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
vlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: mgmnt
    options=600303<RXCSUM,TXCSUM,TSO4,TSO6,RXCSUM_IPV6,TXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    inet 172.16.0.9 netmask 0xffffff00 broadcast 172.16.0.255
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
    vlan: 1 vlanpcp: 0 parent interface: lagg4095
    groups: vlan
vlan11: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: resource
    options=200001<RXCSUM,RXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    inet 172.16.1.62 netmask 0xffffffc0 broadcast 172.16.1.63
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
    vlan: 11 vlanpcp: 2 parent interface: lagg4095
    groups: vlan
vlan13: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: kids
    options=600303<RXCSUM,TXCSUM,TSO4,TSO6,RXCSUM_IPV6,TXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
    vlan: 13 vlanpcp: 0 parent interface: lagg4095
    groups: vlan
vlan14: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: trusted
    options=600303<RXCSUM,TXCSUM,TSO4,TSO6,RXCSUM_IPV6,TXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
    vlan: 14 vlanpcp: 0 parent interface: lagg4095
    groups: vlan
vlan15: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: VPN
    options=200001<RXCSUM,RXCSUM_IPV6>
    ether ac:1f:6b:d7:fb:c5
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect
    status: active
    vlan: 15 vlanpcp: 1 parent interface: lagg4095
    groups: vlan
bridge11: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: resources
    ether 02:11:2a:4b:ab:0b
    nd6 options=9<PERFORMNUD,IFDISABLED>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet0.10 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 18 priority 128 path cost 2000
    member: vnet0.1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 17 priority 128 path cost 2000
    member: vlan11 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 9 priority 128 path cost 55
bridge13: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: kids
    ether 02:11:2a:4b:ab:0d
    nd6 options=9<PERFORMNUD,IFDISABLED>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vlan13 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 10 priority 128 path cost 55
bridge14: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: trusted
    ether 02:11:2a:4b:ab:0e
    nd6 options=9<PERFORMNUD,IFDISABLED>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vlan14 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 11 priority 128 path cost 55
bridge15: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: vpn
    ether 02:11:2a:4b:ab:0f
    nd6 options=9<PERFORMNUD,IFDISABLED>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet0.11 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 19 priority 128 path cost 2000
    member: vnet0.8 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 20 priority 128 path cost 2000
    member: vlan15 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 12 priority 128 path cost 55
vnet0.1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: associated with jail: nextcloud as nic: epair0b
    options=8<VLAN_MTU>
    ether ac:1f:6b:ba:b5:81
    hwaddr 02:e9:d0:00:11:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
vnet0.8: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: test as nic: epair0b
    options=8<VLAN_MTU>
    ether ac:1f:6b:09:26:03
    hwaddr 02:e9:d0:00:14:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
vnet0.10: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
    description: associated with jail: plex as nic: epair0b
    options=8<VLAN_MTU>
    ether ac:1f:6b:14:fa:09
    hwaddr 02:e9:d0:00:12:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
vnet0.11: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: trt as nic: epair0b
    options=8<VLAN_MTU>
    ether ac:1f:6b:c0:3a:d8
    hwaddr 02:e9:d0:00:13:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair

Is there anything else I could change in vnet settings?

 

[KevDog]

@listhor - You might try posting in another thread. Your ifconfig looks pretty solid. I only have two interfaces on my FreeNAS installation but currently am only using on of the interfaces. I'm aware its common to utilize many interfaces rather than one. I have absolutely no experience in setting up a lagg. There are potentially a lot of variables you introduce into the equation and I just don't have the setup on my end to test things. There are others in this forum who are very knowledgable about these additional variables (since frankly what you're doing isn't all that uncommon).

 

[bitola1970]

has the guide on page 1 been updated? do i need to send all VLANs to the managed switch by the one trunk or can i use both my NICs and and say use NIC1 as the management/gui and NIC2 for jails. thanks.

 

[Elliot Dierksen]

It depends what you want to do. If you want some VLAN's to use 1 NIC and others to use a different NIC, that is one case. In that case they would both be trunks (an interface that passes multiple VLAN's) from the perspective of the switch, and you would specify which VLAN's to pass on each individual interface. If you are using a LAGG (aggregating multiple physical interfaces into a single logical interface), that is something different. A LAGG can be a trunk, but it doesn't have to be. If you trunk multiple VLAN's on a LAGG, the packets/conversations are load balanced across the members (selecting the correct method based on your traffic patterns is very important!). Each side makes its own load balancing decision. You can't control anything other than the selection of the load balancing method.

 

[KevDog]

has the guide on page 1 been updated? do i need to send all VLANs to the managed switch by the one trunk or can i use both my NICs and and say use NIC1 as the management/gui and NIC2 for jails. thanks.

I haven't updated the guide for what you want to do since I haven't tested the configuration. You would have to adjust on your switch what vlans would traverse on the specific port and also configure your bridge/vlans on freenas to the corresponding NIC. Theoretically what you are asking should work.

 

[f00b4r00]

Hi,

I have a related issue in 11.3-U2, which was migrated from a working setup in 11.2.

In a nutshell:

2 VLANs, one untagged (1) one tagged (10).
I created VLAN10 in the network interfaces, VLAN10 carries the freenas IP and I can access the freenas system with it
The physical interfaces doesn't carry any IP address.

2 Jails; jail A connecting to VLAN10, jail B connecting to the untagged VLAN. In the original setup that was migrated I didn't define the bridges in Networks, they were defined in the jail configuration, and there are two bridges, one that groups the physical interface and the vnet that should be connected to the untagged vlan (bridge1) and one that bridges the vlan10 interface and the vnet that should connect there (bridge0).

All goes well as long as I have only one jail running (jail A): I can access FreeNAS at its vlan10 ip, and the jail at its own vlan10 ip.

If I start jail B, that sits on the untagged vlan, hell breaks loose for jail A: while I can still reach the FreeNAS box at its VLAN10 IP just fine, jail A becomes unreachable from any machine on the same subnet _EXCEPT_ the FreeNAS box itself (i can ping the jail from the FreeNAS system, but not from any other machine; and conversely jail A can only ping the FreeNAS host, nothing else). Jail B is reachable from the outside world. In other words, jail A disappears, everything else seems to operate as usual.

If I turn off jail B, the situation doesn't return to normal, it seems I have to stop both jails, ensure bridge1 is down, and then start jail A again.

Looking at the output of ifconfig when both jails are running (below), I can't find anything wrong.

Any idea what's going on? Any way to fix this without a complete reinstall? ;)

Thanks

Code:

# ifconfig -a
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: re0
    options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
    ether 30:9c:23:db:98:b1
    hwaddr 30:9c:23:db:98:b1
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
    inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
    inet 127.0.0.1 netmask 0xff000000
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
    groups: lo
vlan10: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: vlan10
    options=80001<RXCSUM,LINKSTATE>
    ether 30:9c:23:db:98:b1
    inet 10.40.10.220 netmask 0xffffff00 broadcast 10.40.10.255
    nd6 options=9<PERFORMNUD,IFDISABLED>
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
    vlan: 10 vlanpcp: 0 parent interface: re0
    groups: vlan
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:4d:47:49:2a:00
    nd6 options=1<PERFORMNUD>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet0.1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 5 priority 128 path cost 2000
    member: vlan10 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 3 priority 128 path cost 20000
vnet0.1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: plexmediaserver as nic: epair0b
    options=8<VLAN_MTU>
    ether 30:9c:23:3d:6b:aa
    hwaddr 02:87:d0:00:05:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair
bridge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:4d:47:49:2a:01
    nd6 options=1<PERFORMNUD>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vnet1.2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 7 priority 128 path cost 2000
    member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 1 priority 128 path cost 20000
vnet1.2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: associated with jail: zoneminder as nic: epair1b
    options=8<VLAN_MTU>
    ether 30:9c:23:db:a7:26
    hwaddr 02:87:d0:00:07:0a
    nd6 options=1<PERFORMNUD>
    media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
    status: active
    groups: epair

 

[KevDog]

@f00b4r00

I'm not sure if its totally necessary but I tagged all VLAN traffic for my guide -- I didn't have any untagged VLANs. I'm not sure if that would make a difference.

 

[Patrick M. Hausen]

Did you disable hardware acceleration features for your physical network interface? That would be the first thing I would look at.

If that does not help, things will get dirty. I try hard to never mix tagged and untagged traffic on the same interface. That does not help solve your current problem, but I think you should consider it. For everything else I would want access to the systems involved and that is probably not an option.

Since Cisco insists on having a "native" VLAN on every trunk port we have a dummy VLAN on all switches in our data centre (1001, named native-dummy) that is not used anywhere on any access port. I really hate this particular feature of the standard. there should not be any untagged frame on a trunk port ...

 

[f00b4r00]

Hi, thanks for the reply.

Not using untagged VLAN isn't an option. Plugged into a "dumb switch" which carries both tagged and untagged (don't ask), there's no way to redirect untagged to something tagged.

Please bear in mind that it once was a working setup; and it doesn't affect the main system (tagged and untagged works just fine there), only the jails (i.e. the vnets), so I'd be inclined to believe this is a software issue?

Thanks!

 

[f00b4r00]

OK so I "fixed" it (for some value of "fixed"): I disabled vnet on jail A (the one sitting on VLAN 10) - good thing it's not strictly necessary there - and presto, now it works as intended. Both jails can operate simultaneously, they're each on the correct VLAN and the FreeNAS system remains accessible where it should, and only there.

Edit: OK it seems I was a bit overly optimistic. The new setting seems to mess up the host's routing table (obtained from DHCP): the default route disappears :(

 

[f00b4r00]

To complete the analysis: the default route on the Freenas host disappears when stopping the non-vnet jail. Seems like a bug in jail network management.

 

[revoman]

I'm trying to use this guide on my FreeNAS 12 beta system (upgraded from 11.3, 11.3 was a new install).

I have 2 problems.

1st, I cannot modify vlan1 to add the IP address after deleting my main interface.

2nd, No matter how I configure things I cannot get the DHCP response back into a jail or VM. My pfsense router says it saw the DHCP request and responded with an IP from the correct pool, but the jail/vm never gets the reply.. :/

Any help or inspiration is greatly appreciated.

mlxen0 is my primary interface. I have vlan's and bridges configured as per the guide. Tunables as well.

 

[ChrisChros]

@revoman
There was one comment from @KevDog to create bridge0 and vlan1 via the GUI and not via tunables.
Have you tried this?

With the new changes for whatever reason the system tunables for the vlan and bridge creation is ignored. You need to set up bridge 0 and vlan 1 or specifically all bridges and vlans with the gui.

 

[KevDog]

@ChrisChros

It's been awhile since I've messed around with the VLAN stuff on FreeNAS (it kind of all just works once you get it setup), but on 11.3 you do everything with the GUI.

 

[raidflex]

Anyone that upgraded to 12.0RC have issues with Vlans and their jails? After I upgraded I noticed that all jails that were on different VLANs then the host could not communicate properly with the network. When I set these jails to use DHCP, then everything was working again. Something is broken with static addresses, VLANs and jails.

I have had no issues on 11.3, this just started with 12.0RC.

 

[KevDog]

@raidflex -- still sporting 11.3 here. I usually don't make the jump for a few months after final release. I remember something similar with the 11.2-11.3 transition -- reworked everything in the RC and then when final went live they fixed things and so I had to undo all my fixes. Wasn't that big of deal but it always takes some time to investigate the issues and try different things as I'm sure you are aware.

 

[raidflex]

Yeah there is some serious issues going on here with Vlans and jails on Truenas 12RC. I just noticed that all of the jails have very poor network performance. I am only experiencing around 10Mb/sec.

 

[KevDog]

@raidflex -- Did you report this on the FreeNas jira ticket system?

 

[raidflex]

Did you report this on the FreeNas jira ticket system?

I have not yet, was just curious if anyone else had also experienced the issue as well.

 

[raidflex]

So I just checked "Disable Hardware Offloading" for the physical interface and now the network throughput is back to normal. Never had to do that on 11.3, not sure if this will cause issues.