🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.amiga.networking
Article #6213

Re: TCP/IP addresses and netmasks

#6213
From: Karl Mehlhaff
Date: Sat, 06 Apr 1996 14:54
52 lines
2308 bytes
In article <761.6658T1315T846@vip.cybercity.dk>,
Brian Ipsen <bipsen@vip.cybercity.dk> wrote:
>Hi!
>
> I'm having a small problem with tcp/ip-setup, and hope somebody here is
>able to help me...
>
> Graphically, my setup looks like this:
>
>
>
>Internet
>gateway  ---------- Server ----- Clients
>
> The gateway address is xx.yy.zz.1  ... The server has 2 Ethernet-cards,
>one which is connected to the gateway, and the other to the clients - And
>is has to be done this way!
> The max number of clients is 7-8. Now the question is how I should give
>the ethernet-cards in the server addresses... I planned something like
>xx.yy.zz.192 and the do some routing with netmasks etc... Any suggestions
>how to do it best ???
>
>
><tsb> GizmoSoft Productions 
>| bipsen@vip.cybercity.dk |
>|      Brian Ipsen        |

What capabilities do the gateway and Server have?  RIP?  Despite what IP 
addresses you set for the ethernet interfaces, it matters what routing 
you setup.  Also is the ethernet communal or separate(are all of the 
above on a thinnet-10b2 common segment, or is it twisted pair-10bT 
between the gateway and server, server and clients.  Is there a ether hub
between the server and the clients?) 
Sounds like you have different ether segments so here is what a model 
might look like:

gateway                server                  clients
ethernet interface     ether interface
xx.yy.zz.1<--------> 1: xx.yy.zz.2
                     2: xx.yy.zz.3<----->xx.yy.zz.??         
routing:
xx.yy.zz.0 255.255.255.0 xx.yy.zz.2 

                       routing:
              (default)0.0.0.0 0.0.0.0 xx.yy.xx.1
                       
                                              routing:
                                      (default) 0.0.0.0 0.0.0.0 xx.yy.zz.3


Hopefully the server is capable of RIP otherwise you might have to do static
IP routing on the server to the various clients. 
Technical Details
Message-ID: <4k60js$jri@crl4.crl.com>
Path: arc1-ca.pugleaf.net!crl4.crl.com!not-for-mail
References: <761.6658T1315T846@vip.cybercity.dk>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!crl4.crl.com!not-for-mail
From: kmehlhaf@crl.com (Karl Mehlhaff)
Newsgroups: comp.sys.amiga.networking
Subject: Re: TCP/IP addresses and netmasks
Date: 6 Apr 1996 06:54:52 -0800
Organization: CRL Dialup Internet Access
Message-ID: <4k60js$jri@crl4.crl.com>
References: <761.6658T1315T846@vip.cybercity.dk>
NNTP-Posting-Host: crl4.crl.com