Network protocols, like TCP/IP and AppleTalk, must be configured into the A/UX kernel before they can be used. When A/UX is shipped, TCP/IP is not part of the kernel. AppleTalk is installed but configured only for the LocalTalk port, not over an Ethernet card.
To add networking capability through the Ethernet port, you must add a low-level driver to the kernel. The EtherTalk drivers on the EtherTalk Installer disk install an Ethernet driver for the Macintosh Toolbox to use. Because, under A/UX, the Macintosh Toolbox environment relies on the A/UX kernel to take care of networking, installing a Macintosh Toolbox level driver is not enough.
To use either TCP/IP or EtherTalk protocols, add the Ethernet driver using the newconfig command. See the directions in the "Network System Administration" manual for a full description of configuring the kernel for Ethernet. The short version follows.
Before beginning, you must have the following:
- An IP address
- A broadcast address
- A netmask and a hostname.
Check with your network administrator if you aren't sure what these should be in your installation. These instructions assume an Apple Ethernet card. If your Ethernet card is from another vendor, you will need to get A/UX drivers for the card. The Macintosh OS drivers are not sufficient to establish Ethernet services (TCP/IP or AppleTalk) under A/UX. Follow the instructions from the vendor for how to install the A/UX drivers and configure the kernel.
1) Assuming you have an Apple card (or have properly configured your third-
party card), from the Command Shell, type the line:
newconfig bnet
2) If you also need nfs services, type:
newconfig nfs
The system will reconfigure itself to include the new modules. It will prompt you to answer several questions, including IP address, broadcast address, and so on. When it asks if you want this system to be a Yellow Pages client, say no.
--WARNING--¨If the system is configured to be a Yellow Pages client when there is no Yellow Pages server present on the network, or if the A/UX system can't talk to the YP server for any reason, the A/UX system will hang forever on the next boot. This is because it is trying to connect to a server that doesn't exist. It's much safer to say "no" to being a YP client now and turn on the YP daemon later, after the TCP/IP connections have been verified.
Article Change History:
2 Sept 1994 - Reviewed.
31 Aug 1992 - REVIEWED for technical accuracy.
Support Information Services