- add instructions for setting up DLX linux for networking
This commit is contained in:
Bryce Denney
parent
6b11183d70
commit
0beda7ae26
@ -1,7 +1,7 @@
|
||||
<!--
|
||||
================================================================
|
||||
doc/docbook/user/user.dbk
|
||||
$Id: user.dbk,v 1.31 2002-03-05 17:17:50 bdenney Exp $
|
||||
$Id: user.dbk,v 1.32 2002-03-08 09:43:57 bdenney Exp $
|
||||
|
||||
This is the top level file for the Bochs Users Manual.
|
||||
================================================================
|
||||
@ -2900,6 +2900,113 @@ in parallel. This is a great idea, but it's not done at present.
|
||||
</para>
|
||||
|
||||
|
||||
</section>
|
||||
<section><title>Setting Up Networking in DLX Linux</title>
|
||||
<para>
|
||||
All Bochs binaries come with a working version of DLX Linux. This section
|
||||
describes how to configure networking in Bochs and enable it within
|
||||
DLX Linux. First you must add a <varname>ne2k</varname> line in your bochsrc
|
||||
file. Then, when you boot the DLX Linux image, you need to type some Linux
|
||||
commands to set up an IP address, a network route, and a name server.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
When you have an <varname>ne2k</varname> line in your bochsrc file, Bochs
|
||||
will emulate a network card called an NE2000. Below are some examples of valid
|
||||
<varname>ne2k</varname> lines for various operating systems. Choose the
|
||||
one that's closest to what you need, add it to your bochsrc file, and
|
||||
edit the values if necessary.
|
||||
<screen>
|
||||
# sample for FreeBSD
|
||||
ne2k: ioaddr=0x280, irq=9, mac=b0:c4:20:00:00:00, ethmod=fbsd, ethdev=xl0
|
||||
# sample for Linux
|
||||
ne2k: ioaddr=0x280, irq=9, mac=b0:c4:20:00:00:00, ethmod=linux, ethdev=eth0
|
||||
# sample for Windows
|
||||
ne2k: ioaddr=0x280, irq=9, mac=00:c4:3B:00:C3:00, ethmod=win32, ethdev=NE2000
|
||||
</screen>
|
||||
You see the pattern. Usually you won't need to change the I/O address, IRQ
|
||||
number, or MAC address. The <varname>ethmod</varname> value depends on your
|
||||
host operating system, and it must be either <constant>null</constant>,
|
||||
<constant>fbsd</constant> (for FreeBSD or OpenBSD), <constant>linux</constant>,
|
||||
or <constant>win32</constant>. The <varname>ethdev</varname> setting is the
|
||||
name of the network interface on your system, and is also OS-dependent. On
|
||||
UNIX systems you can get the name of the network interface by running
|
||||
<command>ifconfig</command>. (Don't choose the loopback interface.) On
|
||||
Windows systems, the correct ethdev setting is not always obvious, so we
|
||||
provide a utility called <command>niclist</command> to list the names of
|
||||
network interfaces to use. When you run <command>niclist</command>, it will
|
||||
suggest an <varname>ne2k</varname> line which is a very good first try.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Next, if you are on a UNIX machine you will need to become the root user.
|
||||
Since bochs is sending and receiving raw network packets, you need to be root
|
||||
to use the network device. To allow normal users to do this would be a
|
||||
security problem.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Now run Bochs to boot DLX Linux. Press enter a few times to accept the default
|
||||
configuration choices. This tells Bochs read the configuration file and then
|
||||
begin. DLX Linux should boot in the Bochs window, and you should see
|
||||
that Linux detects the NE2000 card. Eventually it gets to a login prompt.
|
||||
<screen>
|
||||
ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)
|
||||
NE*000 ethercard probe at 0x280: b0 c4 20 00 00 00
|
||||
eth0: NE2000 found at 0x280, using IRQ 9.
|
||||
</screen>
|
||||
|
||||
<para>
|
||||
At the login prompt, type "root" to log in as root. Then type the ifconfig and
|
||||
route commands to set up networking. The exact IP numbers in the example won't
|
||||
work for you; you must choose an IP configuration that is legal on your
|
||||
network.
|
||||
|
||||
<screen>
|
||||
dlx login: root
|
||||
Linux 1.3.89.
|
||||
dlx:~# ifconfig eth0 192.168.0.99 # set bochs IP address
|
||||
dlx:~# route add -net 192.168.0.0 # first 3 numbers match IP
|
||||
dlx:~# route add default gw 192.168.0.1 # your gateway to the net
|
||||
dlx:~# _
|
||||
</screen>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
The bochs IP address must be an unused IP address on your
|
||||
network. If you duplicate someone else's IP address, your network will
|
||||
become very confused.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
Finally, the network is ready and you can test it out with ping, telnet, or ftp
|
||||
to various machines by their numerical IP address. Keep in mind that for all
|
||||
UNIX host platforms, Bochs networking cannot talk to the host machine. That
|
||||
means the host machine can't be the gateway either. You need another physical
|
||||
machine on the network that bochs can talk to. On Win32 this restriction does
|
||||
not apply.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
When you have a working network configuration, you can make DLX Linux recreate
|
||||
the same settings the next time you boot. Just add the ifconfig and route
|
||||
commands to the end of /etc/rc.d/rc.inet1. I won't try to describe how
|
||||
to use the <command>vi</command> editor in this limited amount of space...
|
||||
</para>
|
||||
</note>
|
||||
|
||||
|
||||
|
||||
<para>
|
||||
To configure a name
|
||||
server, set up <filename>/etc/resolv.conf</filename> with the IP address of
|
||||
your name server as shown.
|
||||
<screen>
|
||||
dlx:~# echo 'nameserver 192.168.0.1' > /etc/resolv.conf
|
||||
</screen>
|
||||
</para>
|
||||
</section>
|
||||
|
||||
</chapter>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user