![]() WireGuard on top makes most of this transparent, to the point where I didn't even realise I had an outage last week until cron sent my phone an angry email. Room for improvement on that number, but I'm not winning any medals for going fast. It recovers from power outages, line disconnects and ISP DHCP expiry with at most 2-3 minutes of lag provided everything else is up and running. That sounds like a whole lot of busywork (it sure is!), but it does mean I don't have to rely on an external IP address checker service and I get pinged instantly at home when there's a problem. When those routes change or expire I have a script do a UPnP query for the correct address (slow and flaky, so I can't just poll using this method) and then it goes off and updates a dynamic DNS pointer with the result. The outer router has RIP2M turned on (one of the few useful things it does), the inner router runs bird and automatically maintains two kernel routes to the IPs both ends of the PPP connection. I've got this setup myself, here's what I ended up doing: My pie-in-the-sky dream is for a "big" (>= 48 port, or at least >= 24 port) 元 Switch, with non-stingy Flash (at least 64MB, preferably >= 128MB) capable of running OpenWRT (I've seen ports for some L2 switches, but none sold in my country). : One AP has a public IP and does NAT/DHCP, the others act as bridges. I've always tried to buy hardware compatible with OpenWRT (which has luckily been very easy since the early 2010s) and I've never had any real issues (even on TP-Link routers notorious for huge dnsmasq memory leaks on their factory firmware). In both cases I don't use OpenWRT's dnsmasq as my DNS server (I run bind DNS in a service VM/Helios 4 respectively), and at home I also have DHCP handled in the Helios 4.Īt work one of my most prized features of OpenWRT is its support for VLANs, which have allowed me to do some pretty nifty network segmentation (in conjunction with Managed L2 switches). At home I use OpenWRT, with the router supplied by my ISP in "Modem" mode (no NAT, it hands a public IP to whatever manages to snatch it via DHCP first, which is always my AP). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |