 Hi there, welcome back to my YouTube channel. This is Daniel Rossell here and bringing you another video on backup internet, failover internet. Yes, not the most exciting topic in the world, but if like me, you spent the last year living with internet that trips out multiple times per day and leads you offline for 10, 15 minutes at a time, you'll be very happy when you have a good backup solution. So what I'm doing now is just seeing, there was one setting that I came across on my new TP-Link writer. That's the TLMR100. It's a 4G router that has a one SIM card. What I've done is bought a data only SIM card, put that in the router and I've subscribed for a data only SIM card plan, data only SIM plan. And what this does, the way I've set it up, and if you're really interested in configuring this kind of a thing in your home, I've done another video explaining all the settings you need to configure on the TP-Link writer so that it knows that its main job is to pass along internet from the ISP, which is what I've got it doing. My ISP writer is going into the one port of the TP-Link. It's got the cellular and it's doing all the magic of failover now. I did a video on here demonstrating how long that takes and I got about 45 seconds to failover but there is another setting that I hadn't yet configured and I just wanted to see if this would make things any quicker. Now this is in network internet, you've got this page called internet connections as you can see, and in it you have offline detection. Now by default it's set up actually on only single detection and you can see that what it has there, again this was automatically populated, there's a DNS lookup and there's a server there. Now this server is from to the best of my knowledge one of like the main DNS servers, the root level, the root servers. It's one of the root name servers on the internet. So this is like a very core piece of internet functionality and therefore it's going to be sending a DNS request out to this DNS server and when it does, and it's doing that kind of on an ongoing basis I guess and when it sends its DNS request and the DNS server doesn't respond to us anything it says, hey where is the internet, the internet must be down. And when it detects the internet is down it's going to failover, it's going to move from the ISP connectivity coming into the WAN port and failover to your cellular. Now how does it go back from cellular internet to how does it know when the main internet source is back so that it can move from cellular back to ISP? I have no idea, but it does. So here is a quick test. So what I've done, instead of wheeling across my office I set this experiment up a little bit differently but I did is actually rigged up to ethernet extensions out of my router and I just got a little ethernet joiner. Now what happens is that when I'm going to pull apart the joiner it's going to break this ethernet connection and this is the ISP connection going out to the cellular router which is in another room. So by just pulling out one of these cables doesn't matter which I'm going to break the connection and interrupt the connectivity going to the router. So what I want to do is firstly measure the time and hopefully it can be a bit more exact than it was last time because of this sophisticated testing device upgrade that we have going on. What I'm going to do is firstly get things set up. I'm going to be using, is my internetworking.com for this device and the reason I'll be using that is because of the fact that when I pull this device it'll, internet's going to go down on the cellular and this desktop computer that I'm screencasting is coming back in from the router so it gets its connectivity from the router and therefore it's going to be offline until the cellular failover kicks in, then it's online. So let me firstly bring across this and I'm actually going to bring across me as well so you can see the big moment that it's going to occur, the failover and in addition to that I'm going to bring across a stopwatch application so I'm just going to actually move this off slightly so we can get an exact measurement on at least it's going to be exact to the nearest two seconds because that's the shortest testing interval that this supports. So these should all be pretty much good to go now and I'm just going to put this here and keep this on top. All right, so we should be good to go now with our testing gear, testing infrastructure in place so you can see me, you can see my stopwatch and you can see that the internet's currently working so I'm going to move over to testing every two seconds. Internet's up, so now I'm going to do the test three, two, one, start the stopwatch and I've just pulled out this way so I've just broken the connection and you're going to see in a second that the internet's going to go to no, there we go. So the failover process should be running now and it's using our one, it's using our single detection DNS method for failover so we're at about 20 seconds and when this goes yes, your internet's working we know that the failover has happened and it's now using cellular connectivity. So I got about 45 seconds on the last test but there we go, 31. So that was 30 seconds to failover so now I'm going to go and put these guys back and now I'm going to, so I've just made the connection again so in order to see when the connection returns I'm going to have to use this time, what is my ISP? Has it already come back to partner? It looks like it has, is that even possible? Apparently it is partner, that's crazy because this is, so that process happened really quickly the last time we did the test I did a bit differently I actually pulled out the DNS connectivity into the rider and that's probably a less smart way to do it because if you have an outage on your ISP rider I guess the most realistic way to simulate that's probably if you pull out the DNS cabling on your rider the rider's going to have to get it back up internally whereas if you just pull out the outbound connectivity you're just simulating it goes down but the rider's ready for the connection so that was pretty crazy it came back like straight away so this is already different than our first test so we've got about 30 seconds if I recall on the first failover so now let me go over and try out the dual detection failover on the TSP link rider and let's measure that and see if we can do better so what I'm going to use is actually 8.8.8.8 and that is the, that's the Google that's a Google server that people use commonly for this purpose so it looks sounds good to me so I've moved into dual detection failover and I've gone for 8.8.8.8 as the IPv4 ping here and I'm just going to go now and set this up so I said if I'm going to all this trouble I may as well not be lazy so I just looked up the IPv6 acrylic now I'm not so familiar with IPv6 I've rarely done this but this is apparently the IPv6 address for that 8.8.8.8 Google server so I have the IPv4, I have the IPv6 of the server and I have my DNS and now I've got two dual detection for offline I'm just going to save this and make sure so this happened the last time as well I don't know why it kicked me out like that maybe because the connectivity's changed so I'm just going to pause the video for a second get back in, make that setting change and then resume okay so I'm just back to where I was a second ago now it has got the 8.8.8.8 and it just didn't register my IPv6 address now the IPv6 is there I'm saving and this time I think it's held I'm pretty sure it's held because it didn't kick me out so we're good to go we have our dual detection failover set up now and what do we need now we need our, this one we need is my internet working and we need our two second interval for the testing here and we need our trusty stopwatch and I'm going to reset the stopwatch three, two, seems so unnecessarily dramatic what's going on, three, two, one okay, start with the stopwatch wait for it to go no because we've broken the connection six, now what's hopefully happening is that it's pinging away at the DNS it's pinging away at Google and it's saying, hey we can't get you and now it's selling itself whatever program is on the router okay we need to like, there you go, 22 so we recorded 22 seconds on the Google failover so therefore the exciting conclusion of today's installment of Daniel's Wild Experiments in Failover Internet is that we were able to reduce the failover time by 10 seconds or so by using Google DNS and now I've reestablished the connection and I've gone back to partner so the failover back to ISP is actually pretty much instant conclusion of this episode if you use dual detection failover on your TP-Link router you can reduce the failover time by I got it by 10 seconds, 30 seconds or 20 seconds it's not huge either way but at least it was an improvement and you'll get quicker failover to your backup connection so hope that video was useful if you'd like to get more videos from me please feel free to subscribe to this YouTube channel thank you very much for watching