On Thu, Sep 23, 1999 at 01:14:08PM -0500, Tim wrote:
> This may be a very basic question, but it still seems to have gotten
> beyond me in a hurry.
>
> I'd like to create a new network using IP Aliasing to allow us some
> growth. Our existing network is 192.168.100.0 and we use 192.168.100.10
> as our gw on the clients. I'd like to create a new network 192.168.200.0
> and allow access to both networks regardless of their ip (192.168.100.xxx
> or 192.168.200.xxx) and also allow them internet access through
> 192.168.100.10 (inetgw)
It sounds like a better thing might be to expand the host number portion
of the IP address "leftwards". I'm guessing your netmask is currently
255.255.255.0, right? If you were to change it to 255.255.252.0 (moving the
network/host number boundary leftward by 2 bits), you could use IP addresses
from 192.168.100.0 to 192.168.103.255 (except ..100.0 and ..103.255 are
reserved of course), as these would all be considered to be on the same
subnet. So you've effectively increased the number of possible hosts by a
factor of 4. It also leaves the rest of 192.168.* free in case you actually
ever do add extra subnets.
This works because the boundary between the network number and host number
in the IP address doesn't have to be on a byte boundary (class based routing
went south years ago). O'Reilly published a book called "TCP/IP Network
Administration" which is probably slightly dated now (if they haven't updated
it), but which helped me enormously when I first made the mistake of getting
involved in all this stuff ;-) The ISBN is 0-937175-82-X, and it's by Craig
Hunt.
You might want to check my maths on the netmask stuff. I'm notorious for
being slapdash and screwing that sort of thing up..
--
We are Linux. Resistance is an indication that you missed the point.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
