Networking

To use the sheep_net driver, you have to compile and install it first.
Change to the source directory of the sheep_net driver:

cd BasiliskII/src/Unix/Linux/NetDriver/ 

then make the driver and install it:

make 
make install 

To load the driver do:

modprobe sheep_net 

On the Serial/Network page of the GUI set Ethernet Interface to “eth0” or however your ethernet card is named.

Figure 1: Network settings for BasiliskII (Linux)

In Mac OS, got to the TCP/IP control panel and set:
-connect via: Ethernet and
-configure: Manually
-use an ip-address in the same subnet as your Linux host PC (i.e only the last three digits differ)
-use 255.255.255.0 for subnet
-use the same router ip-address as you would in your Linux host PC
-use the same nameserver ip-address as you would in your Linux host PC

1. Make sure you have the following preference items set up correctly in ~/.basiliskII_prefs:

• ether tun
• etherconfig /path/to/tunconfig (most likely like “your path to”/BasiliskII/src/Unix/tunconfig)
  

2. Disable the gui, because settings for network could overwrite your preferences

3. Make sure you have sudo working for your user for the following binaries:
/sbin/ifconfig /sbin/iptables

Or you will have to run BasiliskII as root. (on some Linux distributions one of these files might be in /usr/sbin, so copy it to /sbin)

4. Check the IP of the tun0 device with /sbin/ifconfig.
(Most of the time it will report 172.20.40.1)

5. Next, on the MacOS side, set up a static IP address in this form: 172.20.XX.2 , where XX is generally 40 as you may have found with “ifconfig”.
Use the ip address of the tun device as router address and enter your isp's dns ip-address as dns entries.

6. Start “ifconfig” when BasiliskII has started, and check for packages being RX-ed and TX-ed from the tun device.

7. If not, you might also need to issue the following command(s) to get the network going:

 echo 1 > /proc/sys/net/ipv4/ip_forward 

(try this one first)

or even these:

 echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp 

 echo 1 > /proc/sys/net/ipv4/conf/tun0/proxy_arp 

Select Slirp to enable the build-in DHCP server. In Mac OS, use the TCP/IP control panel to set configuration to automatic, using DHCP.

To get ethernet networking going, you can take two routes:

• Install the basiliskII ethernet driver. (faster)
• Use the build-in Nat/Router Module.

In both cases, on the Mac OS side ethernet must also be installed.

Windows 2000/XP:

Installing the BasiliskII ethernet driver in Windows:

- Log in with administrator rights. After installation, user rights suffice.
- Open Network and Dial-up Connections in Control Panel.
- Click Local Area Connection.
- Click the File menu, and then click Properties, or click the Properties button.
- In the Local Area Connection Properties dialog box, click Install.
- Select “Protocol”, and then click “Add”
- Click “Have disk”.
- Browse to the folder where you unzipped files “B2Win2k.inf” and the Windows 2000 version of the “B2ETHER.SYS” driver. Click OK.
- Select “Basilisk II Ethernet driver” from the list and click OK.
- Close the dialog. Wait until the binding analysis is complete.
- Reboot the computer (strongly recommended!).
- After reboot, select the desired network card in the SheepShaver GUI Network page.

Figure 1: BasiliskII Network settings

In Mac OS, got to the TCP/IP control panel and set:
-connect via: Ethernet and
-configure: Manually
-use an ip-address in the same subnet as your Windows host PC (i.e only the last three digits differ)
-use 255.255.255.0 for subnet
-use the same router ip-address as you would in your Windows host PC
-use the same nameserver ip-address as you would in your Windows host PC

Check the readme file included in the SheepShaver zip file for more information and drivers for other Windows platforms

To network BasiliskII you don't need to have Basilisk II ethernet driver installed, actually even an ethernet card is not necessary. You must have ethernet installed on the Mac side.

First, choose the Nat/Router methode in the Network settings page

• Ethernet Interface: Choose Nat/Router Module

Then, in the Mac OS TCP/IP control panel:

-Select “Connect via Ethernet”
-Select “Configure manually”

-IP address: can be any legal address, but don't use the same IP address that you have in Windows. It's always best to ask your network administrator for a unique ip address, because you may later disable the NAT/Router module and possibly cause an ip address conflict on your network.
-Subnet: 255.255.255.0
-Router address: can be almost anything, but preferably the same as the Windows ip address. It must be different than the ip address you entered above.
-Name server address(es): must be correct. Use the same one(s) you have in Windows.

Make sure that the option “Use 802.3” (if present) is not selected.

Home users are free to use the class C addresses reserved for private networks, for example:
-IP: 192.168.0.4
-Subnet 255.255.255.0
-Router: 192.168.0.1

To get active FTP working, you should also enter port information in:

• FTP Ports: define the ftp port, usually 21, others may be used too depending on the server
• Server ports: define the ftp port, usually 21, others may be used too depending on the server

Select Slirp to enable the build-in DHCP server. In Mac OS, use the TCP/IP control panel to set configuration to automatic, using DHCP.