ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/cebix/BasiliskII/README
(Generate patch)

Comparing BasiliskII/README (file contents):
Revision 1.7 by cebix, 1999-10-21T18:29:04Z vs.
Revision 1.9 by cebix, 2000-02-11T17:25:02Z

# Line 332 | Line 332 | ether <ethernet card description>
332    Linux:
333      The "ethernet card description" is the name of an Ethernet interface.
334      There are two approaches to networking with Basilisk II:
335 +
336        1. Direct access to an Ethernet card via the "sheep_net" driver.
337           In this case, the "ethernet card description" must be the name
338           of a real Ethernet card, e.g. "eth0". It also requires the "sheep_net"
# Line 341 | Line 342 | ether <ethernet card description>
342           networking. MacOS will only be able to talk to other machines on
343           the Ethernet, but not to other networks that your Linux box routes
344           (e.g. a second Ethernet or a PPP connection to the Internet).
345 +
346        2. Putting Basilisk II on a virtual Ethernet via the "ethertap" device.
347           In this case, the "ethernet card description" must be the name
348           of an ethertap interface, e.g. "tap0". It also requires that you
349           configure your kernel to enable routing and the ethertap device:
350           under "Networking options", enable "Kernel/User netlink socket" and
351           "Netlink device emulation", under "Network device support", activate
352 <         "Ethertap network tap". Next, see /usr/src/linux/Documentation/
353 <         networking/ethertap.txt for information on how to set up /dev/tap*
354 <         device nodes and activate the ethertap interface. Under MacOS,
355 <         select an IP address that is on the virtual network and set the
356 <         default gateway to the IP address of the ethertap interface. This
357 <         approach will let you access all networks that your Linux box has
358 <         access to (especially, if your Linux box has a dial-up Internet
359 <         connection and is configured for IP masquerading, you can access
360 <         the Internet from MacOS). The drawback is that you can only use
361 <         network protocols that Linux can route, so you have to install and
362 <         configure netatalk if you want to use AppleTalk.
352 >         "Ethertap network tap". You also have to modify devices/net/ethertap.c
353 >         a bit before compiling the new kernel:
354 >
355 >          - insert "#define CONFIG_ETHERTAP_MC 1" near the top (after the
356 >            #include lines)
357 >          - comment out the line "dev->flags|=IFF_NOARP;" in ethertap_probe()
358 >
359 >         Next, see /usr/src/linux/Documentation/networking/ethertap.txt for
360 >         information on how to set up /dev/tap* device nodes and activate the
361 >         ethertap interface. Under MacOS, select an IP address that is on the
362 >         virtual network and set the default gateway to the IP address of the
363 >         ethertap interface. This approach will let you access all networks
364 >         that your Linux box has access to (especially, if your Linux box has
365 >         a dial-up Internet connection and is configured for IP masquerading,
366 >         you can access the Internet from MacOS). The drawback is that you
367 >         can only use network protocols that Linux can route, so you have to
368 >         install and configure netatalk if you want to use AppleTalk. Here is
369 >         an example /etc/atalk/atalkd.conf for a LAN:
370 >
371 >           eth0 -seed -phase 2 -net 1 -addr 1.47 -zone "Ethernet"
372 >           tap0 -seed -phase 2 -net 2 -addr 2.47 -zone "Basilisknet"
373 >
374 >         (the "47" is an arbitrary node number). This will set up a zone
375 >         "Ethernet" (net 1) for the Ethernet and a zone "Basilisknet" (net 2)
376 >         for the internal network connection of the ethertap interface.
377 >         MacOS should automatically recognize the nets and zones upon startup.
378 >         If you are in an existing AppleTalk network, you should contact
379 >         your network administrator about the nets and zones you can use
380 >         (instead of the ones given in the example above).
381  
382    AmigaOS:
383      You have to specify the name of the SANA-II Ethernet device and the device
# Line 633 | Line 653 | Contributions by:
653   - Bill Huey <billh@mag.ucsd.edu>: 15/16 bit DGA and 15/16/32 bit X11
654     window support
655   - David Lawrence <davidl@jlab.org>: incremental window refresh code
656 + - Samuel Lander <blair_sp@hotmail.com>: tile-based window refresh code
657   - Gwenole Beauchesne <gb@dial.oleane.com>: SPARC assembly optimizations and
658     fbdev video code
659   - and others...

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines