--- BasiliskII/README 2004/05/09 16:15:36 1.38 +++ BasiliskII/README 2008/10/01 10:34:34 1.46 @@ -2,7 +2,7 @@ Basilisk II A 68k Macintosh emulator - Copyright (C) 1997-2004 Christian Bauer et al. + Copyright (C) 1997-2008 Christian Bauer et al. License @@ -26,7 +26,7 @@ Basilisk II has currently been ported to IRIX 6.5) - AmigaOS 3.x - Windows NT 4.0 (mostly works under Windows 95/98, too) - - Mac OS X 10.1, 10.2 + - Mac OS X 10.1 thru 10.4 Some features of Basilisk II: - Emulates either a Mac Classic (which runs MacOS 0.x thru 7.5) @@ -362,7 +362,7 @@ ether Linux: The "ethernet card description" is the name of an Ethernet interface. - There are three approaches to networking with Basilisk II: + There are four approaches to networking with Basilisk II: 1. Direct access to an Ethernet card via the "sheep_net" kernel module. The "ethernet card description" must be the name of a real Ethernet @@ -442,6 +442,12 @@ ether instead of sending packets via physical media writes them to the user space program. + Prerequesties: + - Make sure the "tun" kernel module is loaded + # modprobe tun + - Make sure IP Fordwarding is enabled on your system + # echo 1 >/proc/sys/net/ipv4/ip_forward + A virtual network configuration script is required and the default is /usr/local/BasiliskII/tunconfig unless you specify a different file with the "etherconfig" item. @@ -455,6 +461,37 @@ ether #!/bin/sh exec /usr/bin/kdesu -c /path/to/tunconfig $1 $2 + 4. Access the network through the user mode network stack. + (the code and this documentation come from QEMU) + + By setting the "ethernet card description" to "slirp", + Basilisk II uses a completely user mode network stack (you + don't need root priviledges to use the virtual network). The + virtual network configuration is the following: + + Basilisk II <------> Firewall/DHCP server <-----> Internet + (10.0.2.x) | (10.0.2.2) + | + ----> DNS server (10.0.2.3) + | + ----> SMB server (10.0.2.4) + + Basilisk II behaves as if it was behind a firewall which + blocks all incoming connections. You can use a DHCP client to + automatically configure the network in Basilisk II. + + In order to check that the user mode network is working, you + can ping the address 10.0.2.2 and verify that you got an + address in the range 10.0.2.x from the Basilisk II virtual + DHCP server. + + Note that ping is not supported reliably to the internet as + it would require root priviledges. It means you can only ping + the local router (10.0.2.2). + + When using the built-in TFTP server, the router is also the + TFTP server. + FreeBSD: The "ethertap" method described above also works under FreeBSD, but since no-one has found the time to write a section for this manual, you're on @@ -467,6 +504,10 @@ ether not an Ethernet device, Basilisk II will display a warning message and disable Ethernet networking. + Mac OS X: + The "slirp" method described above now seems to work. + + See the next item for an alternative way to do networking with Basilisk II. udptunnel <"true" or "false"> @@ -939,7 +980,7 @@ And another mailing list for Basilisk II http://lists.sourceforge.net/lists/listinfo/basilisk-devel Some general advice about asking technical support questions can be found at - http://www.tuxedo.org/~esr/faqs/smart-questions.html + http://www.catb.org/~esr/faqs/smart-questions.html Keeping this in mind will greatly increase your chances of getting a useful answer.