On Nov 11, 2012, at 8:46 PM, David Griffith wrote: If you're trying to get MacTCP working so you can connect to your netatalk server, you're already done. It'll never happen. System 6 won't transit AFP over IP. You need to get your netatalk server working correctly with atalk and forget about MacTCP, if AFP is your goal. The only reason to have MacTCP is if you plan to use TCP applications such as NCSA Telnet or Fetch (assuming either even works on System 6). FWIW MacTCP is too old to know about CIDR. You need to configure it according to the old class-A/B/C rules for subnets & host numbering. This is probably why it seems "impenetrable". If you have a /24 subnet (netmask 255.255.255.0), then you have a 24-bit network and an 8-bit host number. This is what would have been a class-C subnet, though a proper, old-school class-C subnet can't have a network number smaller than 192.0.0 or larger than 223.255.255. If your network falls outside this range, you have to select the class your network number falls into, then manually override the number of bits for the host number to match your subnet mask. The leftover bits between the host and network become the "subnet". Any field larger than 8 bits will have to be calculated as a bitfield, i.e. 128.63 == 0x803F == 32831. With any luck you're not on a network that breaks down into the old class-based system with a part that doesn't fit into an 8-bit chunk, since then the math gets a little awful. ok bear. -- until further notice