🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.protocols.tcp-ip
2 messages
2 total messages Started by Mark Landin Wed, 11 May 1994 20:39
Subnetting and Netware
#15502
Author: Mark Landin
Date: Wed, 11 May 1994 20:39
35 lines
2558 bytes
I need to break a Class C network into subnets, using each subnet in a 
locations which are connected basically as follows:

+----+    +------+                         +------+   +----+
| W1 |----|  S1  |-------------------------|  S2  |---| W2 |
+----+    +------+                         +------+   +----+

|            | |                             | |           |
+------------+ +-----------------------------+ +-----------+
 Network 1,             Network 2                 Network 1,
 Subnet A                                         Subnet B

111.111.111.2                                    111.111.111.254

W1 and W2 are PC's with an IP address in different subnets of Class C network
1. S1 and S2 are Netware servers which are connected to a backbone with
addresses in Class C Network 2. (The actual IP addresses are made up; I know
that .2 and .254 are not valid the way subnetting works.)

My question is whether another server on the backbone (call it S3) will be
able to figure out that to get to 111.111.111.2 you need to go through server
S1, but that 111.111.111.254 is accessible only through server S2.

I would try this, but the servers in question are inconveniently far apart,
and this looks like a pretty simple "yes-or-no" proposition. 

Thanks for any responses (that pertain to my question, that is!)


 
-- 
*-----------------------------------------------------------------------------*
*  Mark C. Landin					Northeastern St. Univ *
*  landin@cherokee.nsuok.edu					Tahlequah, OK *
*   "Living in the pools, they soon forget about the sea" - Neil Peart, RUSH  * 
Re: Subnetting and Netware
#15503
Author: Samuel Lam
Date: Thu, 12 May 1994 01:40
20 lines
1945 bytes
In article <1994May11.203948.27795@cherokee.nsuok.edu>,
 landin@cherokee.nsuok.edu (Mark Landin) wrote:
>My question is whether another server on the backbone (call it S3) will be
>able to figure out that to get to 111.111.111.2 you need to go through server
>S1, but that 111.111.111.254 is accessible only through server S2.
>
>I would try this, but the servers in question are inconveniently far apart,
>and this looks like a pretty simple "yes-or-no" proposition. 

The simple answer is "no".  To make it work you would need to either
1) use two unique class C IP network numbers on the two stub networks
or 2) use a third subnet of the non-contiguous class C network (the one
used for the stubs) on the backbone network.

...Sam
-- 
<skl@Connectivity.com> -- Connectivity Technology Inc.

"Packet Driver, WinSock & TCP/IP CD-ROM" product information:
{gopher,www,ftp}.CDPublishing.com or <info@CDPublishing.com>
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads