3 ms·

Looks great for client-side connections! I wonder to what degree this is a solution for office-based servers. How would DNS failover be handled?

weirdedhimself 14y ago
Even though we don't run any office-based servers at Sumo Logic, the recommended way is to make the Peplink a DNS server. It will then serve the IP of the currently active link... They also just sent me this in an email: "Our revolutionary SpeedFusion technology is now available. Adding a wealth of innovations that take Peplink/Pepwave gear to the next level, SpeedFusion provides Balance users a cost-effective, high-bandwidth, and reliable alternative to using expensive MPLS connections in their branch VPNs, while SpeedFusion 4G/3G Bonding gives MAX users the ultimate in speedy and dependable networking on the road. Blazing fast, secure, and easy to manage, SpeedFusion is part of Firmware 5.4, so download this new release and become part of the SpeedFusion revolution today." http://www.peplink.com/speedfusion http://www.peplink.com/speedfusion
- SlipperySlope 14y ago
  Looks great and thanks for the tip.
omh 14y ago
There are several tricks you can use for DNS failover, but it's not generally regarded as a reliable option. DNS caching has all kinds of awkward gotchas. You could also host a reverse proxy somewhere reliable which just forwards things to you over the appropriate connection If you need reliable hosting with multiple providers then you can get your own AS number and use BGP routing to provide failover. But that's more expensive by one or two orders of magnitude.
pedrocr 14y ago
You could setup a cloud machine to have the fixed public IP that DNS points to and then have that connect to your office through both connections and do the balancing. A cheap 15$/month low-memory VPS from Amazon or Linode would probably be enough. I wonder if tinc[1] is easy to use to do the load-balancing. [1] http://www.tinc-vpn.org/ http://www.tinc-vpn.org/

weirdedhimself 14y ago

Even though we don't run any office-based servers at Sumo Logic, the recommended way is to make the Peplink a DNS server. It will then serve the IP of the currently active link... They also just sent me this in an email: "Our revolutionary SpeedFusion technology is now available. Adding a wealth of innovations that take Peplink/Pepwave gear to the next level, SpeedFusion provides Balance users a cost-effective, high-bandwidth, and reliable alternative to using expensive MPLS connections in their branch VPNs, while SpeedFusion 4G/3G Bonding gives MAX users the ultimate in speedy and dependable networking on the road. Blazing fast, secure, and easy to manage, SpeedFusion is part of Firmware 5.4, so download this new release and become part of the SpeedFusion revolution today." http://www.peplink.com/speedfusion http://www.peplink.com/speedfusion

SlipperySlope 14y ago
Looks great and thanks for the tip.

omh 14y ago

There are several tricks you can use for DNS failover, but it's not generally regarded as a reliable option. DNS caching has all kinds of awkward gotchas. You could also host a reverse proxy somewhere reliable which just forwards things to you over the appropriate connection If you need reliable hosting with multiple providers then you can get your own AS number and use BGP routing to provide failover. But that's more expensive by one or two orders of magnitude.

pedrocr 14y ago

You could setup a cloud machine to have the fixed public IP that DNS points to and then have that connect to your office through both connections and do the balancing. A cheap 15$/month low-memory VPS from Amazon or Linode would probably be enough. I wonder if tinc[1] is easy to use to do the load-balancing. [1] http://www.tinc-vpn.org/ http://www.tinc-vpn.org/