Steven's Home Network

Support this page!
This page describes my little home network, which includes practical applications of Ethernet, Apple's Airport (i.e. 802.11) technology, networkable PostScript printers, external print servers, AppleTalk, TCP/IP, network address translation (NAT), port forwarding (inbound port mapping), and cross-platform file-sharing. Unlike other reference-type pages, this is a description of one particular implementation a home network. I don't have the depth of knowledge to explain how everything works; I just explain what I've done. Extrapolate as you will:


Introduction:

In my house I have two floors, four people, six computers, and two printers, all hooked together into a network with file-sharing, print-sharing and Internet access. Some of the components are wired; some are wireless; some are new; some are ancient; and they pretty much all work together.

Back to the top of the page.


The Wires: How it's all (un)wired

Physically speaking, I have the following devices on my network:

The colored dots indicate the maximum speeds of the network interfaces. They may be operating at below their maximum rated speeds due to the limitations of the other end of the link.

The Lines: How it all works together

This is a peer-to-peer network. There is no hierarchy among the components; each component determines which other clients will have access to its resources.

I have two protocols and several types of services running on my network. Services are the higher-level functionality that computers, users, and applications need. The protocols are the underlying "language" that the services use. In theory, services can be implemented on top of different protocols, such as Apple File Sharing over TCP/IP or AppleTalk.

TCP/IP provides the underlying "plumbing" for Internet access, for Windows file- and print-sharing, and for AppleShare over IP (ASIP).

Every device on my network speaks TCP/IP with the exception of the LaserWriter, which speaks only AppleTalk. Higher-end LaserWriters, such as the 16/600, speak TCP/IP as well as AppleTalk.

AppleTalk is also used for file- and print-sharing among pre-9.0 Mac's, and for network browsing (LAN, not Internet) among even modern Macs. AppleTalk does not require addresses to be manually assigned.

Internet Access (TCP/IP)


Logically, all the devices connected to each other via the LAN, and to the Internet (WAN) via the Router. The router has a WAN side and a LAN side. The WAN side is connected to the cable modem, and has a single, public IP address from my cable modem account. On the LAN side, the router is the gateway, and forwards all Internet traffic out to the WAN side via Network Address Translation (NAT).

Although the LinkSys router is also capable of serving address to the LAN via DHCP, I have this feature turned off because it disables the router's inbound port mapping.

Instead, I have the AirPort Base Station doing DHCP serving for both the wired side and the wireless side. On the LAN side, infrastructure components and servers have static (e.g. hard-coded) IP addresses; all other LAN devices have DHCP-assigned dynamic addresses. All LAN addresses are, of course, private (192.168.x.y). The cable modem provides a single, static, public IP address to my router.

Apple File- and Print-Sharing (TCP/IP or AppleTalk)


Macs can share files and printers via TCP/IP or AppleTalk.

AppleTalk has been included with the Mac OS for as long as I've owned Macs. It is reliable, robust and slow.

Mac OS 9 includes a bundled copy of Shareway IP, an implementation of AppleShare file sharing over TCP/IP (ASIP). This was previously available for earlier versions of Mac OS as a third-party extension. ASIP is faster than AppleShare over AppleTalk, and has the advantage of being routable over the Internet, but if lacks some nice features of AppleTalk, such as server-less address assignment and announcement, which facilitate browsing of the local network for available resources (what Mac users are accustomed to doing in the Chooser).

Since my LaserWriter speaks only AppleTalk, every computer that needs to print to it must also speak AppleTalk. Every Mac has this ability built-in, of course, but what about the PC's? Windows 2000 includes AppleTalk, but by default it is not installed or activated. Adding the AppleTalk protocol in the Network control panel and then installing the LaserWriter driver (also on the Win2K CD) takes care of this pretty painlessly. For Windows 95/98/Me, I have used Miramar System's PC MacLAN, which implements an AppleTalk protocol stack for file- and print-sharing. PC MacLAN can also connect to an ASIP server, although it cannot be an ASIP server.

If my Mac-compatible printers did not have built-in networking, I would have to connect them to one or more of my Macs via a local (USB or serial) port and then "share" or serve them to the network. This would require AppleTalk for sharing with Macs (or AppleTalk-enabled PCs) and DAVE for sharing with Windows machines. One important thing to note is that AppleTalk and/or DAVE handle only the communications layer of printer-sharing. The Macs and the PCs still have to handle the imaging layer in the same language. For practical purposes, this limits cross-platform printer-sharing to printers that speak PostScript. Since both of my printers have built-in networking, each client talks directly to each printer, and so I don't have this limitation (the Epson 740 is not a PostScript printer).

Windows File- and Print-Sharing

Windows computers natively use the SMB/CIFS protocol to share their files and printers. Mac OS X 10.1 includes an SMB/CIFS client, so any Macs running 10.1 can access Windows shared resources. For computers running Mac OS 7/8/9, you can install DAVE on the Mac (or else do this with PC MacLAN on the PC's; see AppleTalk, above). For more detail on this, see the excellent MacWindows site. If my PC-compatible printers did not have built-in networking, I would have to connect them to one of my PCs via a local (USB or parallel) port and then "share" or serve them to the network. This would require either that the Macs have DAVE installed or that the "server" PC have PC MacLAN installed in order to share the printer across platforms.. One important thing to note is that PC MacLAN and/or DAVE handle only the communications layer of printer-sharing. The Macs and the PCs still have to handle the imaging layer in the same language. For practical purposes, this limits cross-platform printer-sharing to printers that speak PostScript. Since both of my printers have built-in networking, each client talks directly to each printer, and so I don't have this limitation (the Epson 740 is not a PostScript printer). Here's a summary of what software a computer needs to have in order to serve or connect to various types of resources:

What a computer needs to serve . . .
Server
OS
Resource Type
AppleTalk
File Server
ASIP
File Server
AppleTalk
Print-sharing
Windows
File Server
Windows
Print-Sharing
Mac OS 7-8Built-inRequires
ShareWay IP
Built-inRequires
DAVE
Requires
DAVE
Mac OS 9Built-inBuilt-inBuilt-inRequires
DAVE
Requires
DAVE
Mac OS X Built-inBuilt-inBuilt-inBuilt-in??
Win9x/Me Requires
PC MacLAN
Requires
PC MacLAN
Requires
PC MacLAN
Built-inBuilt-in
Win2K Requires
PC MacLAN
Requires
PC MacLAN
Requires
PC MacLAN*
Built-inBuilt-in
Networkable
Printer
N/AN/AVariesN/AVaries
What a computer needs to connect to . . .
Client
OS
Resource Type
AppleTalk
File Server
ASIP
File Server
AppleTalk
Printer or
Print Server
Windows
File Server
Windows
Printer or
Print Server
Pre-
Mac OS 8.x
Built-inRequires
AppleShare x.xx
Built-inRequires
DAVE
Requires
DAVE
Mac OS 8.x-9Built-inBuilt-inBuilt-inRequires
DAVE
Requires
DAVE
Mac OS X Built-inBuilt-inBuilt-inBuilt-in??
Win9x/Me Requires
PC MacLAN
Requires
PC MacLAN
Requires
PC MacLAN*
Built-inBuilt-in
Win2K Requires
PC MacLAN
Requires
PC MacLAN
Built-inBuilt-inBuilt-in
Back to the top of the page.


Configuration: The settings

Please note that this is not intended to be a tutorial of any sort; it's just an example of one way to set up a home network.

Back to the top of the page.


Options: Other ways to do this

I've made a few design decisions for reasons specific to my needs. Here are variations that may suit your needs better. Depending on your needs, you may be able to get away with fewer devices: Back to the top of the page.


Back to the 6100 Upgrade Page

Feedback? Corrections? Mail me @ steven@kan.org (Navigator users) or steven@kan.org (everyone else)


 This page has been viewed: times since 10/22/01.

Warning: Shameless Commerical Plug Ahead!

Books Music  Enter keywords... 
Support this page!!
Amazon.com logo Pay and get paid for auctions or private party transactions, freely and securely over the Internet! Sign up for PayPal now! Get a $5 bonus just for signing up, and get me a $5 referral bonus just for using my referral link!

If you want, you can even make a small donation to this site. Obviously, I don't expect anything, but I have put an awful lot of time, money and energy into this site, so if you've saved yourself time, money or Advil by coming here, you can help me defray the cost of a new G4! Heck, even a dollar would show me that you care :-) Just register with PayPal and send money to steven@kan.org. Thanks!

Last updated: 10/22/01

Thanks, and please come back soon!


p.s. Use Netscape, or be viciously mocked, taunted and ridiculed.

Document change history

10/22/01--First posting