<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Linux Router on Dhiru's Notebook</title><link>https://rfcorner.in/tags/linux-router/</link><description>Recent content in Linux Router on Dhiru's Notebook</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rfcorner.in/tags/linux-router/index.xml" rel="self" type="application/rss+xml"/><item><title>A repeatable and sensible Dual-WAN Failover setup</title><link>https://rfcorner.in/posts/repeatable-sensible-dual-wan-failover/</link><pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate><guid>https://rfcorner.in/posts/repeatable-sensible-dual-wan-failover/</guid><description>&lt;p&gt;In &lt;a href="https://rfcorner.in/posts/easy-dual-wan-failover/"&gt;my previous Dual-WAN failover article&lt;/a&gt;,
I moved from a TP-Link ER605 (slowest device ever) to a MikroTik hEX S. That
setup worked, but it also sent me down the usual rabbit hole of buying
increasingly specialised router hardware for a problem which does not actually
need it.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Repeatable infrastructure should depend on open networking standards and
replaceable commodity hardware, not a particular router model, vendor GUI,
or temporarily available development board.&lt;/p&gt;</description></item></channel></rss>