Northern Journey.com: Home Networking, Part 3: IP Masquerading
Sep 03, 2000, 12:30 (0 Talkback[s])
(Other stories by Gene Wilburn)
Re-Imagining Linux Platforms to Meet the Needs of Cloud Service Providers
[ Thanks to Gene
Wilburn for this link. ]
"In the previous installments of this home networking
mini-series we connected our Linux and Windows PCs into a local
area network (LAN) with NICs, cables and a hub, and implemented a
"private" TCP/IP network based on the IP range of 192.168.0.0-255.
We then added name support in hosts files. In last month's
installment we added Samba support to provide MS-compatible file
and print services for all the PCs on the network."
"In this final home networking installment we'll look at
another option for our network: providing concurrent access to the
Internet to any workstation on our LAN. In order to do this,
our main Linux server must already be capable of linking to the
Internet, as we covered in Part 8: "Connecting to the
"The main reason for connecting a home network to the Internet
is convenience. Being able to share the same connect to the
Internet is useful when you have two or more family members who
want to visit web pages or check email at the same time. It's
easier to maintain a single modem than multiple modems, and a
single Internet setup, rather than several."