Hi!
Where can I find a more detailed explanation about how does SFC relay works?
My main concern is about latency as I have no near SFC server. Does the SFC server operate as an intermediate relay between the Peplink client device and the relay node? or does the SFC server only acts as a way to hole punch trough NAT and establish a direct connection between the client and relay node?
Thanks!
I’m curious about this also. Not for latency but for how the traffic is routed.
I recently tested an SFC Relay and it appeared just like I was accessing the internet from the relay. No VPN warnings on sites that don’t like a regular SFC connection because it detects a VPN.
BUT, all traffic was deducted from my purchased SFC data. Why would I be charged for data unless it’s somehow going through SFC servers?
I did some testing using a couple of fusionhub instances. It seems the traffic first goes to Peplink’s server.
in my case ping times reached 150ms for two devices on the same city. In comparison a direct connection clocked at 5 ms.
Well, that makes sense for the charges but makes no sense at all for efficient routing… Strange.
Thanks for the info!
I also emailed my contact at Peplink and inquired about this, and I understand now…
I also understand how such a tiny simple device (the SFC Relay) can handle the complexity of speed fusion bonding of multiple simultaneous connections. It’s because it doesn’t.
All of the bonding happens between the peplink router and SFC servers, then an extra (single) tunneled connection is made from the SFC Server to the SFC Relay.
This explains the high latency and why we’re charged for data.