linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin J. Cummings" <cummings@kjchome.homeip.net>
To: linux-admin@vger.kernel.org
Subject: Re: IP subnetting
Date: Mon, 14 Jul 2008 16:18:54 -0400	[thread overview]
Message-ID: <487BB4AE.5040702@kjchome.homeip.net> (raw)
In-Reply-To: <487B3757.6329.37A4346B@dermot.sciencephoto.com>

Beginner wrote:
> Hi,
> 
> I have a 126 IP addresses on a single subnet all routing through the 
> same gateway. I have upgraded my router so I now have 2 interfaces. I 
> want to put an SMTP and HTTP server on the 2nd interface and keep the 
> internal hosts on the original interface. I think this is basically a 
> DMZ configuration.
> 
> My current IP address assignment is sporadic, with some static hosts 
> at one end or the other on the IP block and DHCP given a pool from 
> the middle. 
> 
> I want to assign a /29 block of address from within my range to the 
> 2nd interface giving me 5 addresses to use. I am a little unsure what 
> the impact of this change will be on other network services, in 
> particular DHCP. 
> 
> Will I be turning my simple single subnet into 3 different subnets? 
> Do I configure my dhcp.conf with 3 subnet declarations? Can 2 subnets 
> share a gateway address even if it's not local? Would it be advisable 
> to re-configure those static hosts at one end of the block into the 
> other end so I only have 2 subnets? What other services might be 
> effected by this change? I can think of a few httpd.conf allow 
> statements that might need changing and possibly some smb.conf 
> changes. 

Over 10 years ago, I had an office set up with a class C network.  We 
installed a terminal server with 16 dial-up lines, each with a modem for 
dial-in.  I reserved 32 IP addresses for office users to dial in on, and 
their IP addresses were set based on a dial-back scheme used by the 
terminal server.  The IP addresses were all taken out of our class C 
network as a lump at the end.  I viewed it as a subnet of our network, 
but in reality, I didn't have to.  The TS was capable of proxy-arp for 
the remote users, so they looked to the office network like a part of 
the office network, even though they were all routed through the TS.  It 
made life simple.  It would probably have been much more complicated if 
we didn't use that particular TS or at least one capable of doing 
proxy-arp.  I'm sure you could set up something similar, so long as 
whatever you are using to separate the second network is capable of 
proxy-arp for the second network and will do the routing for you.


A.B.C.0/24 <-----> TS <-------> A.B.C.224/27  dial-in machines

-- 
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)

      parent reply	other threads:[~2008-07-14 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 10:24 IP subnetting Beginner
2008-07-14 10:55 ` Glynn Clements
2008-07-14 16:10   ` Beginner
2008-07-14 20:18 ` Kevin J. Cummings [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=487BB4AE.5040702@kjchome.homeip.net \
    --to=cummings@kjchome.homeip.net \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).