<html><head></head><body><div>Like Ioannis, I control my own LAN and isolate it from the "LAN" of the ISP-provided device.</div><div><br></div><div>I currently have an Ubiquity EdgeRouter and its WAN port is the only thing connected to the ISP-provided device.</div><div>I set the ISP-provided device into bridge mode (if I can't I have my ISP do it).</div><div><br></div><div>When this is complete, my EdgeRouter WAN directly faces the Internet (gets an Internet routable address). </div><div>I have the EdgeRouter set up as a DHCP server on the LAN side and have all incoming and outgoing routes denied by default. </div><div>I add rules to allow only what I want in and out of my network.</div><div><br></div><div>I also have the ability to support VLANs for IoT devices that I don't want on my LAN - they get a separate VLAN</div><div><br></div><div>Set up like this, my entire LAN operates within the LAN even when the ISP or the WAN goes dark.</div><div><br></div><div>On Thu, 2018-08-30 at 16:28 +0000, Iznogoud wrote:</div><blockquote type="cite"><pre><blockquote type="cite">
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'.
</blockquote>
>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
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a>
</pre></blockquote></body></html>