toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

240
active users

#failover

0 posts0 participants0 posts today
Peter N. M. Hansteen<p>EdgeRouter 4 under OpenBSD with Failover WAN <a href="https://www.undeadly.org/cgi?action=article;sid=20250516062907" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">undeadly.org/cgi?action=articl</span><span class="invisible">e;sid=20250516062907</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/octeon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>octeon</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://mastodon.social/tags/router" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>router</span></a> <a href="https://mastodon.social/tags/edgerouter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>edgerouter</span></a> <a href="https://mastodon.social/tags/wan" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wan</span></a> <a href="https://mastodon.social/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://mastodon.social/tags/ifstated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ifstated</span></a> <a href="https://mastodon.social/tags/nat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nat</span></a> <a href="https://mastodon.social/tags/dhcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dhcp</span></a> <a href="https://mastodon.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a> <a href="https://mastodon.social/tags/libresoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>libresoftware</span></a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freesoftware</span></a></p>
Felix Palmen :freebsd: :c64:<p>When I recently installed <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> 14.2 on the "new" <a href="https://mastodon.bsd.cafe/tags/Thinkpad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Thinkpad</span></a> T15 Gen1 for my mother, I was first excited to see the installer load <a href="https://mastodon.bsd.cafe/tags/iwlwifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iwlwifi</span></a>. And later disappointed it's *still* restricted to 802.11g.</p><p>But configuring <a href="https://mastodon.bsd.cafe/tags/lagg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lagg</span></a> in <a href="https://mastodon.bsd.cafe/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> mode over lan and <a href="https://mastodon.bsd.cafe/tags/wifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wifi</span></a> is an awesome feature, and as this machine will be operated almost 100% of time in a docking station connected via 1000-BaseT, its fine for now. Still hoping to see newer wifi standards supported ... I see there's work going on from bugzilla and other sources.</p>
David August ❌👑<p>Footnotes: </p><p>₁ three points-safe - at least three independent components or safety features must fail simultaneously for major disaster happen.</p><p>₂ failover - NIST defines as the process of automatically switching to a backup system when the primary system fails. The goal of failover is to minimize or eliminate the impact on users and keep critical systems running.</p><p>🧵 3/3 end </p><p><a href="https://mastodon.online/tags/spaceX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spaceX</span></a> <a href="https://mastodon.online/tags/space" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>space</span></a> <a href="https://mastodon.online/tags/safety" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>safety</span></a> <a href="https://mastodon.online/tags/3PointsSafe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>3PointsSafe</span></a> <a href="https://mastodon.online/tags/ThreePointsSafe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThreePointsSafe</span></a> <a href="https://mastodon.online/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://mastodon.online/tags/GroundControl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GroundControl</span></a> <a href="https://mastodon.online/tags/musk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musk</span></a> <a href="https://mastodon.online/tags/elon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>elon</span></a> <a href="https://mastodon.online/tags/ElonMusk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ElonMusk</span></a> <a href="https://mastodon.online/tags/disaster" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>disaster</span></a> <a href="https://mastodon.online/tags/aerospace" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aerospace</span></a></p>
Richard "mtfnpy" Harman (he/him)<p>Anybody here with a <a href="https://infosec.exchange/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://infosec.exchange/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firewall</span></a> <a href="https://infosec.exchange/tags/router" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>router</span></a> that has two upstream internet links with <a href="https://infosec.exchange/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> between primary/backup?</p><p>I'm trying to RTFM just *how* that would be done without a stupid shell script in a cron job "Can I ping interface1's gateway? No, remove it from the routing table" because routes _tend to be sticky_ and it doesn't make sense to _stay_ on a backup network connection if the primary (faster) connection has been restored.</p>
gary<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@jerry" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jerry</span></a></span> this would be a good writeup - ie how to make your dns more reliable/robust <a href="https://infosec.exchange/tags/round" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>round</span></a> robin dns <a href="https://infosec.exchange/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://infosec.exchange/tags/munin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>munin</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@necrosis" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>necrosis</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@pallenberg" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pallenberg</span></a></span> <br>Ich selbst nutze <a href="https://mstdn.social/tags/pfSense" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pfSense</span></a> seit Jahren produktiv inklusive transparenter <a href="https://mstdn.social/tags/Failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Failover</span></a> &amp; <a href="https://mstdn.social/tags/Fallback" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fallback</span></a> - Setups samt <a href="https://mstdn.social/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPN</span></a>-Tunneling um unterbrechungsfreie Anbindungen zu ermöglichen...</p><p>Für <a href="https://mstdn.social/tags/WLAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WLAN</span></a> nutz' ich hingegen <a href="https://mstdn.social/tags/Ubiquiti" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubiquiti</span></a> <a href="https://mstdn.social/tags/UniFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UniFi</span></a> weil's effizient und skalierbar ist.</p><p>Und bei beidem braucht mensch kein <a href="https://mstdn.social/tags/CCNA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCNA</span></a> oder Equivalent um Zeug einzurichten!</p>
GrapheneOS<p>We host our own authoritative DNS servers rather than using a managed service. When you connect to <a href="https://grapheneos.org/" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">grapheneos.org/</span><span class="invisible"></span></a>, your DNS resolver service obtains an IP from our own DNS servers. We route traffic to the closest server via GeoDNS and have automatic failover on downtime.</p><p><a href="https://grapheneos.social/tags/grapheneos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>grapheneos</span></a> <a href="https://grapheneos.social/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> <a href="https://grapheneos.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://grapheneos.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a> <a href="https://grapheneos.social/tags/nameserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nameserver</span></a> <a href="https://grapheneos.social/tags/anycast" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>anycast</span></a> <a href="https://grapheneos.social/tags/geodns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geodns</span></a> <a href="https://grapheneos.social/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://grapheneos.social/tags/powerdns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>powerdns</span></a> <a href="https://grapheneos.social/tags/ovh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ovh</span></a> <a href="https://grapheneos.social/tags/buyvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>buyvm</span></a></p>
Renée<p>I'm literally right now putting together a presentation on DR and mutiregion resilience for a workshop at the end of the month, and I would like to thank AWS US East 1 for its service.</p><p><a href="https://mastodon.social/tags/useast1" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>useast1</span></a> <a href="https://mastodon.social/tags/use1" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>use1</span></a> <a href="https://mastodon.social/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aws</span></a> <a href="https://mastodon.social/tags/dr" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dr</span></a> <a href="https://mastodon.social/tags/resilience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>resilience</span></a> <a href="https://mastodon.social/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://mastodon.social/tags/activeshmactive" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>activeshmactive</span></a></p>
scy 🔜 WHY<p>I need to build a highly available service on 2 bare metal servers, no cloud whatsoever.</p><p>The service will download files, process them &amp; upload them to another (third) server. If one of my servers fails, the second one should take over. It would be nice if only _one_ of them did the work at any given time, to save resources &amp; not confuse server #3.</p><p>I have some ideas, but I’m interested in yours. How would you do it? Any recommended tools?</p><p><a href="https://chaos.social/tags/HighAvailability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HighAvailability</span></a> <a href="https://chaos.social/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://chaos.social/tags/redundancy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>redundancy</span></a> <a href="https://chaos.social/tags/AskFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AskFedi</span></a></p>
Jay Jackson<p>How cool is this? Just got this email for my EERO network update. I can setup a backup internet if my primary network goes down, such as a hotspot, like convert my phone hotspot. I will have to test this out. This is very cool to have this kind of granular control for home networks. Very business like. <a href="https://twit.social/tags/eero" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eero</span></a> <a href="https://twit.social/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://twit.social/tags/internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>internet</span></a></p>