The setup in question is as follows:
MAX HD2 with two wired WAN connections and two cellular connections. SpeedFusion tunnel to a FusionHub appliance in my datacenter on the other end.
My desired configuration is to have the SpeedFusion tunnel set up with:
WAN 1 = Priority 1
WAN 2 = Priority 1 (e.g. equal to WAN 1)
Cellular 1 = Priority 2
Cellular 2 = Priority 3
The issue that I am having is that WAN 1 appears to have some kind of network issue that prevents the tunnel from performing properly. If I set WAN 2 and Cellular 1 as Priority 1, I see SpeedFusion traffic moving in both directions over both links.
If I set WAN 1 and WAN 2 to Priority 1 and then push data while monitoring SF traffic, I see traffic moving in both directions on WAN 2. On WAN 1 the traffic is minuscule in the downstream direction but normal in the upstream direction.
If I set WAN 1 as the only Priority 1 connection, the SF tunnel establishes and I can run small packets over the link (e.g. ping, DNS lookups, etc.) but TCP is completely non-functional.
I have tested WAN 1 manually to confirm that the MTU is 1500 and 1500 byte packets with the DF bit set will pass all the way through to my FusionHub appliance. I have also tried reducing the MTU just in case there was something odd happening specific to the SF traffic. No change.
I’m sure that this is an issue with something on the WAN 1 network, but I am in need of some further debugging/diagnostic capabilities for the SpeedFusion tunnel in order to be able to formulate a support request to the carrier to try and get it resolved. Is there some diagnostic function that can be run and/or debug logging that can be enabled on both ends of the SF tunnel to identify specifically what is happening?