 Hi there. Welcome back to my YouTube channel. This is Daniel Rosalier. So I did a video a couple of days ago checking out a software called Speedify, a really, really interesting product just about the only software I've come across promising to do connection bonding. Now, bonding is something very tricky to do on a hardware level. We've, we've heard a lot about SD1s recently and bonding or this idea of being able to use different sources of connectivity to get yourself one really reliable and faster connection. So if you take a cellular connection plus an ISP connection or an ISP connection plus satellite connectivity, two satellites, two cellular connections with different providers. That would really be the key thing. There wouldn't be any point in using two interfaces to pull from the same provider. But the idea of bonding is great. Very hard to do using hardware if you're not in an enterprise type environment as I've learned. But on the consumer level, they've made this nice little tool. Now, I did not find that I got a speed bump, which is what I was interested in potentially using it for. I ran a hotspot from my phone, used my ethernet connectivity from my ISP, put those together, and I didn't see an improvement on my baseline. Now, we repeated the test using USB tethering just to make sure that the computer was getting the best possible connection from cellular. And again, I didn't really see that speed boost, but it doesn't mean that Speedify keeps I keep almost saying Spotify. It doesn't mean that Speedify mightn't be useful. One use I could make of it. Now, what I've done is implemented this on the network level. But if I hadn't put together all this different hardware and I was happy to pay Speedify's monthly subscription, is I could have just used this for failover. So I could have, you know, got a little cellular hotspot, a data sim, kept that running here somewhere in my office and just used Speedify to try to failover on the network level. Or on the device level on my computer. Now, the disadvantage would be other people on the network wouldn't benefit from that failover. You can run Speedify on a Linux server. Some people have put it on Raspberry Pis, but you still need to pay that subscription. So I thought I'd just do a quick test of how well the failover works. Now, I've done failover testing on my hardware failover setup here, which is basically cellular 4G connectivity on a TP-Link modem. I have my ISP line coming into it. I got it by 20 seconds, 20 seconds when I configured dual failover testing and 30 seconds if I just had singular failover testing. The failover testing singular is it's just pinging an IP address. The dual testing is it's also pinging a root DNS server. So that's what we're trying to beat here. What I'm going to attempt to do for this test is firstly, I have my hotspot running here from the phone or I thought I had. So I'm just going to get that running and I'm going to open up Speedify and get those two connections into it. So let's go ahead and do that. So I'm just going to pull over to screen two here and let me get Speedify up somewhere as visible. So you can see now it's only seeing my ethernet connection as a source. So I'm going to go and tap the button on my phone for USB tethering. First, you need to enable the hotspot USB tethering. I'm just going to have to do a manual disconnect or reconnect because I've manually disconnected the USB. OK, so we're back in action. And now I need to just turn on USB tethering and now we should now it's running. Network manager confirms that we are connected or disconnected. Now I've connected to it. So now we can see there's two connection sources available to us in Speedify. First one is my ethernet. Second one would be the phone that's just come live. That's cellular. So that was sort of a roundabout way of verifying that it's the right connection. So that's definitely my phone hotspot there. Now I'm going to bond, let the bonding magic happen now. The bonding magic is more complicated than it looks. It's going up to the cloud with my two connections then coming back down as far as I understand and bonding them together. Now, just of interest in terms of the speed, I was getting about sort of 40 megabits per second download on the baseline and about three or four on the upload, which is pretty typical for me. As I said, when I did a test here, I didn't really see a significant difference when I added that cellular line to it. But what I'm going to do now is simulate a failing of the ethernet connection. The way I'm going to do that, I don't want to do anything on the software level to make Speedify's life any easier. It's what I'm going to do instead is I've just brought out my ethernet over a switch and the second switch there, that's running into my computer. So what I'm just going to do now in a second is pull out that ethernet, literally pull out the cabling and that's going to drop ethernet. And I'm just going to watch now to see how quickly it's going to just if there's going to be any interruption whatsoever. I suspect there will not, but let's see. So I'm going to go on to this website is my internetworking.com, which is a nice little diagnostic utility. I want to keep Speedify open to throughout this process so we can see how quickly it recognizes the loss of ethernet connectivity. So three to one, I'm going to pull the cable three to one cable is gone. So we've just lost ethernet. Ethernet is still showing, although it's now showing this gone down to zero. Now it's dropped in Speedify. So that took about three seconds and pretty good, pretty good. So that is the answer is truly zero, essentially. I mean, I don't think it took a couple of seconds for it to see that the ethernet was gone, but the actual failover happened pretty much instantaneously. So that is my quick test of failover, how well that works on Speedify. What I will say, this failover on my hardware set up here, which is a little bit more complex, running an ISP line into a 4G TP link router with cellular configured as a backup option. And that process took me 20 to 30 seconds for that router in the other room to realize, oh, the ethernet is dropped. Let's start using cellular, bring that line up and turn on to it. Speedify beat that out of the park. So I've still decided about Speedify from a speed perspective. I haven't seen those gains, but that failover testing was very encouraging. It pretty much went straight from one to the other without any interruption. And this is me browsing my cellular now. I can use the internet and, you know, it was, what, a five one connection there about so it's not going to be very quick, but on the plus side, it didn't take any time to get over to it. You know what, I may as well, I may as well go all the way with this. So we can see what we're pulling here is limited. Now let me actually just reconnect ethernet to the switch. And let's see how long it takes for speed of it. There we go. That was about what a second. Now Speedify has got that our primary connection is an operation now. And it's given me a little notification here and we're back. And I can sort of just tell, well, I'll be able to tell by looking at the speed if this is ethernet or cellular. If it's anything above eight, it's yeah, it's ethernet. So Speedify's failover testing has gone well. It's outpaced my TP-Link cellular rider by about 20 to 30 seconds, which is good if you're looking for a quick cellular failover. I feel like if you would like to get more videos for me about everything related to technology, home networking and Linux, please feel free to hit that subscribe button.