intervlan problems

[ChronicEcks]

I am running dual opnsense firewall with identical hardware in high availability mode. I do not think that is related as even if I disable it or set the gateway as one of the firewall ips as opposed to the carp the same problems occur.

First the web ui is sometimes extremely slow or doesnt load properly but only if I am not on the same vlan. If I access from the same vlan, there is no problem.

Another problem I am getting is proxmox shell becomes unusable only if I access from a different vlan or non vlan. After about 30 seconds the shell stops responding, no error or anything just no input. I can refresh the page and it works again only for the same thing to happen again. If I join the same vlan that I am accessing the webui from this doesnt happen at all.

I have read that I need to enable the parent interface of the vlan in opnsense. I have done that, just enabled it without assigning an ip and same thing happens.

I was running both opnsense in vm on proxmox and was also getting this error, I thought it could  be related to virtualization so I switched to baremetal and it is still happening. I dont know where else to look, thanks.

[zan]

Try enabling/disabling VLAN hardware filtering, some NICs have trouble passing vlan tagged traffic with hardware filtering on/off.
May also try enabling promiscuous mode on parent iface and see if it makes difference.

[ChronicEcks]

I had already tried the vlan filtering both enabled and disabled same problem. I tried out the promiscuous as you said and same problem as well.

However I was using a broadcom 10g nic and swapped it out for an intel 10g nic set everything up again and the problem went away. Maybe it was a tunable specific for the broadcom although that is unlikely since I was getting this error with opnsense as a vm with the nic as a virtual nic and not passthrough. I will just be ordering a 2nd intel nic for the other opnsense box.

If anyone else has this problem or is wondering I was using a N20KJ Dell Broadcom 57810S and I now I am using a Intel X520-DA2.

[ChronicEcks]

ok I thought it was fixed but now its started happening again, I thought it might be my specific pc that im accessing the webui from but I tried a different client pc and the same thing.