Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #13525

Home network - design ideas

Show all headers | View raw

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?

Back to comp.os.linux.misc | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Home network - design ideas Tim Watts <tw_usenet@dionic.net> - 2015-01-31 11:36 +0000
  Re: Home network - design ideas William Unruh <unruh@invalid.ca> - 2015-01-31 18:23 +0000
    Re: Home network - design ideas Tim Watts <tw_usenet@dionic.net> - 2015-01-31 20:02 +0000
      Re: Home network - design ideas Chick Tower <c.tower@deadspam.com> - 2015-02-03 20:17 +0000
        Re: Home network - design ideas The Natural Philosopher <tnp@invalid.invalid> - 2015-02-03 20:33 +0000
        Re: Home network - design ideas Tim Watts <tw_usenet@dionic.net> - 2015-02-03 20:47 +0000
  Re: Home network - design ideas Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-01-31 20:37 +0000
    Re: Home network - design ideas William Unruh <unruh@invalid.ca> - 2015-01-31 22:24 +0000
      Re: Home network - design ideas Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-02-01 16:21 +0000
        Re: Home network - design ideas John Hasler <jhasler@newsguy.com> - 2015-02-01 10:52 -0600
          Re: Home network - design ideas Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-02-01 20:42 +0000
            Re: Home network - design ideas Marc Haber <mh+usenetspam1118@zugschl.us> - 2015-02-02 07:24 +0100
    Re: Home network - design ideas Tim Watts <tw_usenet@dionic.net> - 2015-01-31 23:43 +0000
      Re: Home network - design ideas Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-02-01 16:23 +0000

csiph-web