This is an issue caused by server policies. See for instance Netflix blocking SFC
Too bad, but many servers are wary of connections from IP addresses hosted by VPN-capable server farms. Your break-out with the bonded connection provides such an IP address.
Hi! I’m encountering the same issue while using SpeedFusion for the same reason (bandwidth bonding because of low quality rural internet). We’re you able to find any solutions or work-arounds?
One alternative solution is to have a second peplink device (“speedfusion server router”) deployed at a well-connected location, and then establish a speedfusion connection between your rural device and the server.
As long as the server is not perceived as a public VPN server then you should be fine. The cost would be the additional router, and whatever it would cost you to connect the server router to the internet.
As an example, we have a non-profit helping connecting a rural community in the mountains of California. The members of the community each have a speedfusion connection to a Peplink router we have in the SF Bay metro area, and route their traffic through that hub as warranted. The hub is located at an already-well-connected place we provide, so there are no additional connection expenses.
The world perceives the connections from the mountains as actually being at a corporate (non-server-farm) IP address, and thus not something that the copyright folks worry about.
Just the usual $0.02
Cheers,
Sigurd
PS: The dual connection ability has saved everybody’s behind a number of times - most are running a combination of VZW and TMO, both of which suffer occasional outages.