<?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>MikroTik on Dhiru's Notebook</title><link>https://rfcorner.in/tags/mikrotik/</link><description>Recent content in MikroTik on Dhiru's Notebook</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rfcorner.in/tags/mikrotik/index.xml" rel="self" type="application/rss+xml"/><item><title>Easy Dual WAN Failover</title><link>https://rfcorner.in/posts/easy-dual-wan-failover/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://rfcorner.in/posts/easy-dual-wan-failover/</guid><description>&lt;h2 id="initial-setup"&gt;Initial setup&lt;/h2&gt;
&lt;p&gt;Initially, I had set up a TP-Link ER605 (TL-R605) V2 router to handle the dual WANs - on paper, it checked all the boxes: load balancing, failover, and a relatively affordable price point. But in practice, it turned out to be a frustrating experience.&lt;/p&gt;
&lt;p&gt;The biggest issue was how excruciatingly slow the device was to boot and handle failover. In a setup where uptime actually matters, waiting around for the router to recover or switch links defeats the whole purpose of having redundancy in the first place. Failover should feel seamless - this felt anything but.&lt;/p&gt;</description></item></channel></rss>