Subj : Re: setup
To   : Ben Ritchey
From : Tony Langdon
Date : Tue May 02 2017 13:46:00

-=> Ben Ritchey wrote to Richard Menedetter <=-

 RM> Also stop using cascaded routers also on IPv4.

 BR> Heck no, it works great!

In IPv4, cascaded NAT actually breaks things in subtle ways.

 RM> Just changed the config to dumb down the routing on the second router
 RM> to a dumb switch.

 BR> Can't, need DNS plus Reserved, wireless and switching for both routers.
 BR> Two completely different households/systems that don't overlap.

DNS - don't know what you mean here, you can point all devices to your ISP's
DNS servers and it all "just works" for 99% of people.

Wireless, it is possible to run a wireless router as a switch/access point. 
Done it heaps of times myself.

Now if the households are separate, with the default way of cascading, the
household on the second router can see everything on the house LAN.  Is this
what you want?  Using proper (non NAT) routing and firewalling would be a
better way to go, to keep the networks separate.  The only NAT would be at the
connection to the Internet  But that does require a bit of networking knowledge
to pull off, and I would want to be running a capable OS on the main router
(e.g. OpenWRT), as many home routers are brain dead when it comes to handling
multiple subnets, as this is not a common configuration.

Of course, with IPv6, you'd have to do the same - run separate /64 LAN segments
on each LAN and route / firewall between them.  That would require an ISP
willing to route more than a /64 (e.g.  a /56) to you.  For example, I could do
it here, as I have a /56.


.... Auto correct has become my worst enema.
--- MultiMail/Win32 v0.49
 * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

.