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.37 by cebix, 2004-01-12T15:29:19Z vs.
Revision 1.39 by gbeauche, 2005-05-13T09:33:51Z

# Line 362 | Line 362 | ether <ethernet card description>
362  
363    Linux:
364      The "ethernet card description" is the name of an Ethernet interface.
365 <    There are two approaches to networking with Basilisk II:
365 >    There are four approaches to networking with Basilisk II:
366  
367        1. Direct access to an Ethernet card via the "sheep_net" kernel module.
368           The "ethernet card description" must be the name of a real Ethernet
# Line 432 | Line 432 | ether <ethernet card description>
432           your network administrator about the nets and zones you can use
433           (instead of the ones given in the example above).
434  
435 +      3. Access the network through a "tuntap" interface.
436 +         The "ethernet card description" must be set to "tun".
437 +
438 +         TUN/TAP provides packet reception and transmission for user
439 +         space programs.  It can be viewed as a simple Point-to-Point
440 +         or Ethernet device, which instead of receiving packets from a
441 +         physical media, receives them from user space program and
442 +         instead of sending packets via physical media writes them to
443 +         the user space program.
444 +
445 +         A virtual network configuration script is required and the
446 +         default is /usr/local/BasiliskII/tunconfig unless you specify
447 +         a different file with the "etherconfig" item.
448 +
449 +         This script requires you that "sudo" is properly configured
450 +         so that "/sbin/ifconfig" and "/sbin/iptables" can be executed
451 +         as root. Otherwise, you can still write a helper script which
452 +         invokes your favorite program to enhance a user priviledges.
453 +         e.g. in a KDE environment, kdesu can be used as follows:
454 +
455 +           #!/bin/sh
456 +           exec /usr/bin/kdesu -c /path/to/tunconfig $1 $2
457 +
458 +      4. Access the network through the user mode network stack.
459 +         (the code and this documentation come from QEMU)
460 +
461 +         By setting the "ethernet card description" to "slirp",
462 +         Basilisk II uses a completely user mode network stack (you
463 +         don't need root priviledges to use the virtual network). The
464 +         virtual network configuration is the following:
465 +
466 +           Basilisk II <------> Firewall/DHCP server <-----> Internet
467 +           (10.0.2.x)      |         (10.0.2.2)
468 +                           |
469 +                           ----> DNS server (10.0.2.3)
470 +                           |
471 +                           ----> SMB server (10.0.2.4)
472 +
473 +         Basilisk II behaves as if it was behind a firewall which
474 +         blocks all incoming connections. You can use a DHCP client to
475 +         automatically configure the network in Basilisk II.
476 +
477 +         In order to check that the user mode network is working, you
478 +         can ping the address 10.0.2.2 and verify that you got an
479 +         address in the range 10.0.2.x from the Basilisk II virtual
480 +         DHCP server.
481 +
482 +         Note that ping is not supported reliably to the internet as
483 +         it would require root priviledges. It means you can only ping
484 +         the local router (10.0.2.2).
485 +
486 +         When using the built-in TFTP server, the router is also the
487 +         TFTP server.
488 +
489    FreeBSD:
490      The "ethertap" method described above also works under FreeBSD, but since
491      no-one has found the time to write a section for this manual, you're on

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines