Issue with pfSense on XCP-ng using tagged networks (xcp-ng) cannot resolve hosts on peer xcp-ng hosts and latency on external hosts.
I have configured vLAN tagged networks that connect to a trunk that is bonded to two NICs. The ISPs are on their own interface.
I have 6 of these setup:
WAN network → pfSense on XCP-ng → XCP-ng network vLAN tagged and connected to redundant trunk
x.x.x.10 (WAN) → x.x.10.1 (fpSense) → vLAN 10
The trunk has the management network as its native network untagged.
If I connect a VM to this same tagged network on the XCP-ng host, it will see the router and I can login to the UI but not be able to get out to the internet. If I connect via a VM or physical host outside of XCP-ng, I can connect but the connection is very slow (~20 Mbs). If I connect the directly to the WAN on the XCP-ng hosts, there is no latency.
I have had a similar setup without the vLANs on esxi 7 that I transitioned to XCP-ng and vLANs, but it did not face any latency issues running on the vmware stack (it also did not use vLAN tags).
I suspect that I have done something wrong with vLAN tagging or best practices, since this is new tech in my stack that I am learning. XCP-ng is working for the other hosts and setups, the only real thing on this pfSense (one-to-many+to-one+balanced gateway) approach seems to be some issue with the network stack and configs I have implemented in some way. I could be wrong though.
Intended application: I need to setup router(s) for each ISP IP block address to provide unique gateways to have an additional router balance outbound traffic across them.
I am sure it is just something simple I am doing wrong, but I am at a loss for what I did that causes this behavior.