Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Tim Watts Newsgroups: comp.os.linux.misc Subject: Home network - design ideas Date: Sat, 31 Jan 2015 11:36:19 +0000 Lines: 74 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 521b9mUsBGkAv7aboMRzUw2cFHynEh8W2nDy4nZKXwVkgYRV0q X-Orig-Path: squidward.dionic.net!not-for-mail Cancel-Lock: sha1:yXCeHxrVZgWrwIZjeAlas1KfriE= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 Xref: csiph.com comp.os.linux.misc:13525 Hiya, This is not a "how do I do this" - that's not a problem. I'd just like to bat an idea or two as I have a couple of ways and I cannot decide which is best... OK - I have a /27 IPv4 public block (yay for good ISPs!) That's enough for: 4, later 5 servers Various IP cams Several laptops Various infrastructure But not enough for every ad hoc smartphone and visitor items. My PPPoE endpoint *and* router *and* firewall is a linux box, Atom MiniITX that can manage gigabit throughput. Switches are NetGear gigabit SmartSwitches So - Option 1 ============= 1) Visitor network on say 10.0.1.x, NATed 2) My stuff on /27 including infrastructure like wifi, switches etc 3) Ad hoc smartphones etc use visitor net Pro: Clean and simple Pro: Internal-Internal traffic is switched (fast, no real bottleneck) Con: Might still might hit the /27 limit one day Con: Still need to NAT all my Netflix devices as Unblock-US only works with one client IP Option 2 ======== 1) Visitor network on say 10.0.1.x, NATed 2) My really public stuff (like IPCams, servers, home automation) on /27 3) My other stuff on another private, say 10.0.0.x, NATed Pro: Unlimited local IPs and I will NOT hit the end of a /27 for my public stuff Con: Certain Internal-Internal traffic gets routed so will bottleneck Option 3 ======== 1) Visitor network on say 10.0.1.x, NATed 2) All my stuff on private, 10.0.0.x NATed 3) Router does IP translation from /27 to 10.0.0.x for public stuff Pro: Fast switching for Internal-Internal Con: Needs either split-DNS (have this now, do not like it) OR the router will end up doing reflection-translation for Internal-Internal Pro: Saves one IP that would otherwise be used on the router at the gateway Pro: Very flexible. Con: I just don't like it. I am very much pro using public IPs as the Internet originally intended. I hate NAT but it is OK for misc visitor stuff. Prefer to have my regular kit on public IPs and clean. There is an Option 4, dual public/private IPs on certain devices but that was so disgusting I do not want to go there again... What would you do?