Menu
▾
▴
Re: [Astlinux-devel] WAN Failover
|
From: Lonnie A. <li...@lo...> - 2018-05-17 21:01:23
|
David, Thanks for the explanation, more comments inline ... > On May 17, 2018, at 3:09 PM, David Kerr <Da...@Ke...> wrote: > > Lonnie, > My cable modem has an internal LAN address of 192.168.100.1. If there is no external internet connection then the modem issues a IP address in the 192.168.100.x range, and itself as the gateway, by DHCP to the internal client. Thus the internal client has a valid private network address and can access the modem status page. If there is an external connection then the modem issues the IP address and gateway as provided by the cable company through DHCP. It retains 192.168.100.1 as its own address so if that range is routed through eth0 then clients can still access the modem's status page. > > So, when I say that the WAN failover status primary gateway is bogus then what I mean is that it is no longer a valid gateway from my ISP, but rather just the modem itself which has no external connection. > > Some observations... 1) when the modem issues a 192.168.100.x address it provides a lease time of 30 seconds. This results in 2 lines into syslog from udhcpc every 30 seconds. Yuk. Noisy yes, but working as designed, and I understand why the lease is so short when "offline" waiting to establish a public lease. > 2) monitoring for gateway changing to a specific IP (in my case 192.168.100.1) would be another way to detect that primary WAN link had failed. For your current case, but there are many different situations when the Primary WAN can fail ... failed at your ISP's node, a cable cut beyond your head-end, etc... AstLinux's heuristic is to fping a couple IPv4's and switch then they all fail, return back when the fping's succeed. In my past testing on my main box, the only annoying thing when WAN Failover is active all the time is if a very short outage (say 30 seconds) causes a switch which can be 2 minutes or so before it returns back to the Primary ... in those special cases I would prefer it would not switch, but until we have a heuristic to predict the future :-) it is what it is. Lonnie > > David. > > > > > > On Thu, May 17, 2018 at 11:33 AM, Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > First, a 4G/LTE Modem in bridge mode behaves just like a cable modem, which is ideal with AstLinux ... the WiFi client to iPhone tethering method leaves the public IP address unknown to the local interface ... workable but not ideal. I'm not sure what you mean that "WAN failover status shows 192.168.100.1 as (bogus) primary gateway" > > > My ddclient uses eth0 as the external IPv4 address. > > The simplest is to use a public server to determine your IPv4 address when using WAN Failover. > > or "service dynamicdns stop" when switching to failover if you don't want to expend the extra traffic on updating your dynamic DNS. > > > > Is there a setting to change when Astlinux does the shutdown? > > I seem to recall that when the UPS goes to a "critical" level then AstLinux does a shutdown, the accuracy of that number can vary a lot per the age of the battery. If you want to ride the UPS down you could just "service ups stop" temporally. > > The /etc/ups/*.conf files are auto-generated unless if a matching /mnt/kd/ups/*.conf file exists. Samples are in /stat/etc/ups/ > > Saying that, what Michael suggested is good info as well, configuring the UPS itself. > > Finally, if you really want your AstLinux box to power-down before the UPS powers off with safety, any margin less than 10-20% will be too low as the UPS battery ages. > > > Lonnie > > > > > > On May 17, 2018, at 9:12 AM, David Kerr <Da...@Ke...> wrote: > > > > Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... > > > > Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. > > > > WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. > > > > My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. > > > > I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? > > > > Thoughts? > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
