The Need for Business Continuity

Today I’m going to talk about low-earth orbit (LEO) satellite, like Starlink, and how you can use that for business connectivity needs. I’m here at my home office and notably, I don’t have any landline connectivity. I have a fixed wireless circuit from a local regional wireless ISP or WISP, a cellular option, LTE connection, as well as a geosynchronous satellite option. And so, we’ll add to those a LEO Sat through Starlink and take a look at what it does.

Setting Up Starlink 

To install Starlink, you first use their app to scan the sky to see if the location that you’re planning has a clear view of where their satellites will be flying by. 

*Welcome to my networking rack here in the house. In here, I’ve got a switch and my Bigleaf router, my SD-WAN router, and there’s three WAN circuits connected. We’re going to hook up the fourth today!* 

We can see here, I’m logged into the Bigleaf Web Dashboard. I pulled up my house. And on the overview page, I can see I have three WAN circuits configured so far. What I’ll do is I’ll go into our configuration tab here, go into edit mode, and I’ll add a new WAN circuit. You can specify geostationary or low earth orbit for your satellite type and the platform will adapt accordingly. And just a moment ago, the tunnels came up. 

Comparing The Data 

We now have some graph data. 

I want to address a few questions I think might be running through folks’ minds. First, how do I think about Starlink versus most landline type circuits, fiber cable, DSL, that kind of thing? 

I think the health alarm data we can see is really useful to know how these comparisons sit. If I was to go pull up another customer site, which I’ll do here. 

So this location, we have some Comcast fiber. This is in Oregon. This is a typical fiber health graph. Literally nothing. This circuit above here, this is a cable circuit, looks pretty clean as well. Users are not going to notice too much of what’s going on here. You’ve got a little bit of jitter upload and download at times. I would say this is pretty squeaky clean for a cable circuit. You can see them totally clean sometimes, but this is a nice cable circuit. We see them with plenty of packet loss and other issues at times. We’ll take a look at another location here. This top circuit here is again, Comcast fiber. So we can see, it looks pretty clean. There’s a couple blips. So, this one could be user impacting. This is middle of the day. You have basically a mini outage. 

Then Frontier Fios. We’ll take a look at that one. Again, looks pretty clean, a couple blips there, not too big of a deal. 

So back to my house: If you compare those graphs against the Starlink graph for the same time period, it’s got periods in the middle of the night where it looks pretty clean, but during the day, there’s definitely a lot of variability. And that’s what I would probably highlight. 

With most wireless type connections, they’re going to be more variable than a landline circuit. Yet, they are also a great redundancy path. Throughput wise, that can vary as well. So, fiber’s typically going to offer you more throughput than what we’re seeing with Starlink, which is around somewhere between 60 and 120mg down and upload is very variable up from zero to 15 megabit up at my location here. 

Let’s take a look at other health paths like ViaSat. ViaSat is a geosynchronous satellite, and we can see that quality wise, it’s actually very good! Now this graph doesn’t reflect the absolute latency of the path to traverse to geosynchronous orbit and back. The latency that our platform measures is in the form of relative one-way latency. So, our technology does some things to adapt for that, knowing that geosynchronous satellite does have that higher latency, just kind of in the background. 

You might wonder, well, what’s difference between geosynchronous satellite and low earth orbit satellite? I drew a cute little diagram here to show that. (4:22)  

So, if you’ve got my house, the red depicts essentially what is happening with the lower earth orbit, where there’s a shorter path from my house to the satellite, to the ground station, which then is connected via fiber to whatever data I’m reaching, some data center, whereas the geosynchronous satellite is a much larger distance. So, the reason the latency is much lower is because it’s taking a much shorter path, just geographically. 

The time of flight of the RF signals is reduced.

Compare Against LTE Circuit 

Now, if we compare against the LTE circuit I have, the LTE circuit is much more consistent in its behavior and much lower in packet loss, but the throughputs a lot less. And when I’ve tested here, I’m getting about 4mhgs each way on that circuit max. 

And then lastly, the fixed wireless circuit I have from a local residential fixed wireless provider. We can see that during times of load, there is significant jitter and packet loss. I’d say it sits in between the LTE and the Starlink as far as variability. 

So, all in all, each wireless circuit does have its pros and cons. And you need to look at what’s available in your area and trade-offs of throughput and performance characteristics.

Static IP Address

Now, what about a static IP address? That’s something that a lot of businesses need to be able to deploy with certain use cases, VPNs, or hosting a server, that kind of thing. And none of the circuits that I have, have a standard static IP address. 

They’re all using a DHCP provided NAT IP address. And the nice thing is with Bigleaf Networks, I actually have a static IP block. Bigleaf creates a tunnel across each of these circuits and delivers a single public static IP address over them. Just like you would get if you had BGP in a carrier-grade enterprise environment.

The nice thing is with Bigleaf Networks, I actually have a static IP block. Bigleaf creates a tunnel across each of these circuits and delivers a single public static IP address over them.

Joel Mulkey

So… What About SD-WAN?

Lastly, do you need SD-WAN to make use of lower earth orbit like Starlink? 

Well, looking at the health of the circuits at my home here, I would say YES. If I had just this one circuit, or even if I had multiple circuits with a less sophisticated load balancing QS mechanism, I wouldn’t be able to do things like voice calling or Zoom — those sorts of sensitive applications — in a reliable manner. 

And we could see examples of that here. I had some Zoom calls this morning, all this green saying VoIP was the Zoom traffic. And we could see that the SD-WAN platform really had to adapt hard to make best use of that. So, here’s my LTE circuit that used that for upload traffic. 

This was around 10:30 to 10:50 AM and we could see that the alarms were fairly low at that time — level two jitter was all that it was seeing. The down link looks like, in part, on the fixed wireless circuit around 10:40 to 10:50 timeframe. (6:50) 

It’s kind of jumpy because it was I think moving the traffic around and it’s likely because alarms varied. So, there’s some traffic that ended up on the fixed wireless, and then other traffic ended up here on the Starlink circuit at that time. So the platform was adapting to make sure that each packet was writing over the best possible circuit. 

If I didn’t have that in place, my Zoom quality would not have been as good. Now, would it have been unusable? In this case, no. Starlink alarms aren’t terrible at that time.  

If they were level four or five, yeah. At that point, that’s when people are unclicking their video. They’re going to just audio or saying, “Hey, can I call you on the phone?”

More On Starlink x SD-WAN

Another SD-WAN feature of note that Starlink really will need to be successful in the business environment is something that can provide QoS over very variable bandwidth circuits. 

Via Iperf testing through the platform, we can see this is download testing. This is just raw Iperf traffic varying between 50 megabits a second up to 100. (8:44)  

In the upload direction, we see traffic varies even more considerably, 9mgs down to 1mg. 

Important: If you just have a static QoS policy applied to the circuit saying it’s 10mgs or something, that QoS isn’t going to work. The traffic’s going to hit constrictions within the Starlink service, get buffered and either dropped or delayed. So, you need a platform like Bigleaf that can detect that variability and bandwidth, adapt to that, and ensure QoS prioritization through that path, even as conditions change!

Conclusion

In conclusion, I think Starlink and low earth orbit are fantastic technologies. I’m really excited about what they bring to bear for folks in rural areas like me and businesses that can’t get good landline connectivity or need a really solid redundant path that offers more throughput than LTE can! 

For business-critical use cases, I would combine it though with SD-WAN and another circuit, if you have, and we’d be more than happy to help you out with that at Bigleaf Networks.

Thanks for that walkthrough, Joel. We really appreciate it! 

You can learn more about making the Starlink Satellite part of the connectivity plans at your business & see how Bigleaf can improve your connectivity for all your connection types by requesting a FREE demo. If you have any questions, send us an email at sales@bigleaf.net.