I guess better late than never...

So we've got a failover IP, and a nice trick to be able to get the same WAN IP on both our routers. If you do stateless packet filtering, this is actually enough, and your redundant setup is already finished. However, if you do stateful packet filtering, the moment the failover IP moves to the backup router, your connection will be dropped because it doesn't have any knowledge about it in its connection tracking table.

This is something that has been bothering me for a long time. I use the same SSID for both my 2.4GHz and 5GHz networks, so that clients can roam from one network to another. However, in this setup, the client decides what network it think will work best. And unfortunately, most clients just suck at making this decision.

Usually my clients end up connecting to the 2.4GHz network, unless they are in the same room as the AP. There's a simple explanation for this: the 2.4GHz network usually has a stronger signal strength, simply because the lower frequency penetrates walls easier.

Little over a year ago I ordered 2 Yubico U2F security keys, through the Github offer. When they arrrived, I was immediately annoyed by the fact that only Chrome (and Chromium) supported the U2F standard. At that time, my main browser, did not support U2F at all, and the feature request had been open for a year, with no real progress. Sigh.