A. Multiple IP Addresses With Mac OS 8.1 And Later

Open Transport, as shipped with Mac OS 8.1 and later, allows multiple IP addresses to be assigned to a single Macintosh. Synonyms for this feature include IP Aliasing, Secondary IP Address Support, IP Masquerading, "Multihoming", IP Multimode support.

To configure the ShareWay Macintosh to use multiple IP addresses:

1. Set the TCP/IP Control Panel for manual addressing.
2. Create a text file with the required name "IP Secondary Addresses" and put it into the Preferences folder. A sample "IP Secondary Addresses" file is included with ShareWay IP Professional.

Each line of the IP Secondary Addresses file contains a secondary IP address to be used by the system. Each line also has fields for an optional subnet mask and router address for its secondary IP address, but they are not relevant to ShareWay IP and will not be discussed here. If fields for the optional subnet mask and router address are missing, Open Transport will use a default subnet mask for each line's IP address class, and the default router associated with the primary address.

Thus, each line has the form:

ip=xxx.xxx.xxx.xxx

Lines proceeded by a ";" are ignored. For example,

; Note: no white space in any 'ip=' line
ip=192.168.22.200
ip=192.168.22.201
ip=192.168.22.202

When Open Transport activates TCP/IP, the primary address will be obtained from the TCP/IP Control Panel setting. Open Transport then looks for the "IP Secondary Addresses" file in the Preferences folder to determine if additional addresses should also be configured. If there are duplicate IP address entries in the IP Secondary Addresses file, the duplicate addresses will be ignored. If there is an address conflict between a ShareWay-assigned IP address and either the primary or any secondary addresses with another host, Open Transport will present an error message using a dialog box and unload Open Transport/TCP from memory. The error dialog will display the conflicting IP address, the hardware address of the conflicting machine and note that your TCP/IP network interface has been shut down.

To resolve the conflict, quit all of the TCP/IP applications on both conflicting machines, reconfigure TCP/IP on one of the machines so there is no longer an address conflict, then relaunch your TCP/IP applications.

B. Log File Format

ShareWay IP's log file is written in an extended WebSTAR log format. WebSTAR log format is a standard tab-delimited text format which can be read by any word processor or spreadsheet application. This format can also be processed by a number of log analyzer applications, such as Open Door's LogDoor product.

Actions related to ShareWay IP are logged using the standard WebSTAR comment format:

!!ShareWay IP Pro 2.0d3 START 03/10/99 13:49:12
!!ShareWay IP Pro 2.0d3 STOP 03/10/99 13:49:07
!!ShareWay IP Pro 2.0d3 ENABLE_LOGGING 03/10/99 13:49:20
!!ShareWay IP Pro 2.0d3 DISABLE_LOGGING 03/10/99 13:49:17
!!ShareWay IP Pro 2.0d3 03/10/99 13:50:58 chas6100b 192.0.0.3 Server connections stopped.
!!ShareWay IP Pro 2.0d3 03/10/99 13:51:02 chas6100b 192.0.0.3 Server connections enabled.
!!ShareWay IP Pro 2.0d3 03/10/99 13:51:02 chas6100b 192.0.0.3 Server connections available.
!!ShareWay IP Pro 2.0d3 03/10/99 13:51:09 chas6100b 192.0.0.3 Server connections unavailable.

Other operations are logged using the following tokens (which are included in the !!LOG_FORMAT line whenever ShareWay IP starts up or logging is enabled):

• DATE, TIME
  • same values as in WebSTAR logs
• RESULT
  • OK for normal login or logout
  • ERR! for failed login or abnormal logout
• HOSTNAME
  • the IP address of the client
• SERVER_ADDRESS
  • the IP address assigned by ShareWay IP to the server being accessed -- included only when the ShareWay machine is multihomed
• SERVER_PORT
  • the IP port number assigned by ShareWay IP to the server being accessed
• URL
  • not used in ShareWay IP, but included for compatibility with other Open Door log files
• USER
  • user name (guest is logged as blank)
• AFP_METHOD (new token)
  • FPLogin
  • FPLogout
• AFP_STATUS (new token)
  • Additional result code. Indicates Mac error code if available. See AFP Error Codes below.
• BYTES_SENT
  • FPLogout lines only. The total number of bytes transferred while the client was connected, counted from the time the user logged on (even if the user was already connected when logging was enabled). All bytes transferred during the session are included, not just the bytes read from or written to files.
• TIME_TAKEN
  • FPLogout lines only. The total time the user was connected, measured from the time the user logged in. Format is hh:mm:ss.

Note that when ShareWay IP stops or quits, all users who are currently logged in will be listed as logging out through an FPLogout line with error code -5027.

Sample log lines

!!LOG_FORMAT DATE TIME RESULT HOSTNAME SERVER_ADDRESS SERVER_PORT URL USER AFP_METHOD AFP_STATUS BYTES_SENT TIME_TAKEN

05/05/99	10:39:18	OK	192.0.0.3	192.0.0.21	8548	chas	FPLogin	0
05/05/99	10:39:21	OK	192.0.0.3	192.0.0.21	8548	chas	FPLogout	0	394	00:00:03

AFP error codes

-1069	aspNoServers	No servers at that address
-5014	afpMiscError	Server closed session
-5016	afpNoServer	Server is not responding
-5019	afpParmErr	Miscellaneous parameter error (usually invalid user name)
-5022	afpSessClosed	Session unexpectedly torn down
-5023	afpUserNotAuth	User authentication failed (usually, password is not correct)
-5027	afpServerGoingDown	The Gateway has stopped, or ShareWay IP has quit

Back to Table of Contents
Back to Troubleshooting