One of the best explanations of TCP/IP in general, and subnet masking specifically is 
in the TCP/IP White Paper on 3com's web site.

Unless you are doing something really odd, your subnet mask will be the same whether 
your network is viewed from the "inside" or the "outside"

Carl

>>> Martin Roberts <[EMAIL PROTECTED]> 09/09 11:26 AM >>>
"Similarly confused" from UK writes:
Look at the Linux Network Administrators Guide (NAG).  It has some
guidelines for how net-masks work etc.  I guess you could get it from
Sunsite or similar.

Good luck,

Martin

> -----Original Message-----
> From: Bogdan Taru [mailto:[EMAIL PROTECTED]] 
> Sent: 09 September 1998 15:41
> To: linux-newbie
> Subject: netmask
> 
> 
> 
>  Hi everyone, 
> 
>  I need your help in order to understand something that's 
> been bothering
> me for a long time now. I just don't understand what is a 
> netmask, why is
> it needed, and how is it generated.
>  Let's take an example: we have a network with this IP: 194.195.227.0.
> Right? So, it's a class C network... It can have up to 254 
> hosts. But it
> has only, let's say, 8 hosts, with these addresses:
> 194.195.227.2
> 194.195.227.3
> .............
> 194.195.227.9 
> 
>  I would imagine that from the outside, the netmask for this virtual
> network is 255.255.255.0. Right? 
>  Ok! Now from the inside, the netmask (in my opinion) would also be
> 255.255.255.0. Right? But here starts the funny part, because 
> it's not, in
> other's opinion... 
>  I can be very wrong! But I'm willing to learn, so please help me...
> 
> Have fun,
> bogdan
> 
> 
> 
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                  
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                                  
                                                                                       
                                                                                       
                                                                                       
                                                                                       
                                                              

Reply via email to