🚀 go-pugleaf

Steve Baker <bakes@corona.iinet.net.au> writes:

>Brett Stevens wrote:
>> 
>> I'm new to this group but I'm worndering if anyone can help me with a
>> little problem.
>> 
>> I'm trying to put Linux on my small net at home but I'm unsure what to
>> do with IP addresses when I'm dialing up to my ISP

>You don't need to do anything, unless you want your whole home net to be
>able to access the internet.  Just assign your own net IP addresses in
>one of the following ranges:
>    10.0.0.0     - 10.255.255.255
>    172.16.0.0   - 172.31.255.255
>    192.168.0.0  - 192.168.255.255
>These ranges are reserved for computers on a non-connected network, so
>your net won't conflict with other systems on the Internet.

I had thought this too actually, but what I find was that as soon as I 
setup a default route to my ISP (I have a static IPaddress), my 
home network stopped working.

To work around this I played around with a couple of routers, which fixed 
the problem, if I recalled correctly, they were bcastd, and srouted, 
however, IMHO IPmasquerading is the best choice as it allows  all the other 
home machine to have access to the net as well.

>If you want your whole home net to be able to access the Internet, you
>will need to set up IP masquerading on your 'Internetted' PC, so that
>packets coming from other computers on your home net _look_ like they
>come from only one source (since you only have 1 IP address allocated).
>There is information on this in
>ftp://ftp.eves.com/pub/masq/ip_masquerade.faq
>and supposedly http://www.indyramp.com .

Yep, this is the way to go, many thanks to those who worked on the masq. 
project, I can now squeeze up to 7k/s transfer sometime when all the 
home machines is hooked up to the net :-).

Cheers,
Paul Pham
PPham@mailbox.uq.oz.au