Hi,
I have created two vlan interfaces on a physical interface, using the guide. The first VLAN interface I created works really well. However, the second VLAN interface I added is experiencing odd behavior. Traffic is passing through from the LAN side - I can ping/trace route/and open a Google page. But if I try and pull any larger amounts of data - speedcheck, Azure Portal login page, the connections time out (even thought the pings stay constant).
Any suggestions here? Both VLANs have the same (Best, 0) priority settings. I've tried elevating this to but it doesn't make a difference.
Cheers,
Matt
You did neither tell your configuration nor the topology, so this is only guesswork:
1. Mixing up tagged and untagged (V)LANs on FreeBSD/OpnSense does not work too well. You should have either one or the other.
2. Some hardware does mix up VLANs as well, especially cheap switches. For example, if you cascade switches, an edge switch might short-circuit both VLANs, which can lead to all kinds of problems.
I know, I deliberately didn't go into details in case someone shouted out something "MTU size". Both VLANs were tagged by the way.
Anyway I've decide to move this to a physical interface and see how that goes.
Some ISPs, for example, Comcast/ Xfinity, and using their router box in bridge mode, very much dislike seeing altered frame priority set at the interface level. I learned that the hard way. If you're using your own cable modem, less issues.
I opted instead for simpler traffic shaping at the Layer 2 IP level for traffic that needs lesser priority.