I have one hosted at home, the ip address is using dhcp from providers, so it will changed everytime the lease is expired. I don't see any problem with this. As long as connected to the internet. Me as atlas users also doesn't care if it's changed everyday. Thank you Budiwijaya On Fri, Jul 21, 2017 at 12:55 AM, Anurag Bhatia <me@anuragbhatia.com> wrote:
Hello, everyone!
Greetings from India. I am hosting RIPE Atlas probe at home for a while. I have two connections - primary which is high capacity symmetric link and secondary which is a low-end cable broadband connection. The core router is Ubnt edge router and it runs "load balancing" to keep primary link as primary and switch to secondary if the primary is down for more than 30 seconds. This setup works well for me but RIPE Atlas is not part of this "auto switch" if the primary is down.
I wonder if it makes sense to add RIPE Atlas to it?
It will improve my monthly availability report and possibly will move from 98% uptime (of primary) to 99.9% uptime (of both links) and that's actually real uptime on LAN.
But it would screw up probe data as both networks are completely different and have different sets of upstream resulting in different routing preference to root DNS instances etc.
Also, does probe comes only if connectivity is switched? It's a non-BGP setup and when I say "auto switch" of uplinks, it's basically switching the default route from primary to secondary while keeping same private IP on LAN side. Due to NATing, WAN IP changes in this scenario.
Curious to hear thoughts if I should or should not. Another way, of course, would be to do it for a month and see data. :)
Thanks.
--
Anurag Bhatia anuragbhatia.com
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas-ambassadors