Like Ioannis, I control my own LAN and isolate it from the "LAN" of the ISP-provided device. I currently have an Ubiquity EdgeRouter and its WAN port is the only thing connected to the ISP-provided device. I set the ISP-provided device into bridge mode (if I can't I have my ISP do it). When this is complete, my EdgeRouter WAN directly faces the Internet (gets an Internet routable address). I have the EdgeRouter set up as a DHCP server on the LAN side and have all incoming and outgoing routes denied by default. I add rules to allow only what I want in and out of my network. I also have the ability to support VLANs for IoT devices that I don't want on my LAN - they get a separate VLAN Set up like this, my entire LAN operates within the LAN even when the ISP or the WAN goes dark. On Thu, 2018-08-30 at 16:28 +0000, Iznogoud wrote: > > > > > > Because of this incident I am trying to figure out how to continue > > to have a > > functioning network even when my WAN connection dies as I need my > > internal > > lan to 'work'. > > > From day one, circa 2002-3, I had a router right after the DSL > modem's LAN. > This, because I knew that Qwest would very happily log into my DSL > model and, > at the very least, "fix" things now and then. > > I laugh thinking about having gone the more naive way! > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20180830/4d0e5feb/attachment.html>