Hello, I also posted this in Jails & bhvye. I think this is an issue that might have been caused by a previous tunable change to "fix" the issue before, but I can't remember where I read the fix or where it was in the tunable.
Issue: All NICs are seemingly bridged to the FreeNAS host process, causing a broadcast storm when my VM’s NICs are plugged in. Also, the VMs NICs seem to be bridged as well.
Troubleshooting performed: pinged network resources, noticed dropped pings to Freenas IP and PFSense (VM). Unplugged ix3 and broadcast storm stopped, plugged it back in, storm resumed. Rebooted freeNAS, issue persists. Reset network interfaces ix0-3, issue persists. Set Freenas to 10.0.1.100, instead of 0.0.0.0, issue persists.
Narrative:
When I rebooted after applying 11.3-U4.1 my Freenas server seems to have bridged all of the NICs, even the ones assigned to my PFSense server. So, it basically is creating a broadcast storm. I only want FreeNAS to "talk" on ix0. The VM is using ix2 as WAN and ix3 as LAN. Ideas as to the cause?
Issue: All NICs are seemingly bridged to the FreeNAS host process, causing a broadcast storm when my VM’s NICs are plugged in. Also, the VMs NICs seem to be bridged as well.
Troubleshooting performed: pinged network resources, noticed dropped pings to Freenas IP and PFSense (VM). Unplugged ix3 and broadcast storm stopped, plugged it back in, storm resumed. Rebooted freeNAS, issue persists. Reset network interfaces ix0-3, issue persists. Set Freenas to 10.0.1.100, instead of 0.0.0.0, issue persists.
Narrative:
When I rebooted after applying 11.3-U4.1 my Freenas server seems to have bridged all of the NICs, even the ones assigned to my PFSense server. So, it basically is creating a broadcast storm. I only want FreeNAS to "talk" on ix0. The VM is using ix2 as WAN and ix3 as LAN. Ideas as to the cause?