networking
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
networking [2021/09/19 18:00] – external edit 127.0.0.1 | networking [2022/04/16 18:16] (current) – fixed typos wiki_admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Hardware ===== | + | ===== Hardware |
- | By default | + | Out of the box Amix only supports the [[http:// |
- | With Gateway UNIX CD's drivers the Village Tronic Ariadne | + | With the {{http:// |
+ | |||
+ | The A2065 only has a BNC (coaxial 10Base2) and an DB15 (AUI) ports. If you buy an AUI Transceiver and plug it into the AUI port, you can have RJ45 connectivity. Ardiane, being four years newer, has RJ45 on board making it easier to plug in into modern networks. Modern switches might however | ||
+ | |||
+ | If you're into vintage networking you can also go ahead and build your own coaxial 10Base2 network! Old 10BaseT (RJ45) | ||
===== Basic installation ===== | ===== Basic installation ===== | ||
- | During the installation, | + | During the installation, |
You can check the status of the network and the currently used IP address with **ifconfig aen0** | You can check the status of the network and the currently used IP address with **ifconfig aen0** | ||
Line 13: | Line 17: | ||
===== DNS ===== | ===== DNS ===== | ||
- | Out of the box, Amiga UNIX doesn' | + | Out of the box, Amiga UNIX doesn' |
+ | |||
+ | To enable DNS access: | ||
< | < | ||
ln -f / | ln -f / | ||
- | |||
mv / | mv / | ||
- | |||
ln -f / | ln -f / | ||
</ | </ | ||
- | If you put your nameserver into / | + | If you put your nameserver into / |
- | forwarders 192.168.1.1 | + | To easily configure your system, download couple of config files from here: |
+ | {{https:// | ||
+ | |||
+ | Place named.boot in /etc, and everything else into /var/named. Edit / | ||
+ | |||
+ | **forwarders 192.168.1.1** | ||
Then start named by running in.named with no arguments. Edit the file / | Then start named by running in.named with no arguments. Edit the file / | ||
- | nameserver 127.0.0.1 | + | **nameserver 127.0.0.1** |
You can verify this is working by using nslookup to find google.com' | You can verify this is working by using nslookup to find google.com' | ||
Line 62: | Line 71: | ||
telnet 192.168.0.44 | telnet 192.168.0.44 | ||
- | If backspace doesn' | + | If backspace doesn' |
===== General weirdness ===== | ===== General weirdness ===== | ||
- | Oh yeah, there' | + | Oh yeah, there' |
- | domainname nodomain | + | **domainname nodomain** |
- | ===== Connecting to an NFS share ===== | ||
- | One of the easiest ways to share files between your Amix machine and other machines, is to use an NFS share. It is an old standard and still widely supported (even some modern NAS boxes offer it out-of-the-box). | + | ===== Installing drivers for Village Tronic' |
- | First you need to have a compatible network card and configured it correctly. Then, create an NFS share on your network. Easiest way is to create it without username/password. Or create an user with identical credentials as your Amix user account. Then on your Amix machine, create a directory where you want the network share to appear (here /home/joe/ | + | // Copied for safekeeping from [[https:// |
- | On your Amix machine | + | Download and copy the drivers |
- | mount -F nfs (IP-address):/ | + | |
- | Example: | + | |
- | (Where 192.168.0.68 is a machine | + | |
- | Now you can access | + | * After the script execution you need to compile a new kernel. So type: **cd /usr/sys** |
+ | and start compiling with **make** | ||
+ | * This file must be copied to /stand: **cp / | ||
+ | and then be installed into the boot partition: | ||
+ | * **make bootpart KERNEL=relocunix** | ||
+ | * After the installation you need to reboot the system: **cd /** and **shutdown | ||
- | Notes: some NAS/network gear let you adjust the MTU (maximum transmission unit) to enhance transfer speeds. At least one user reported that raising this value (from the default value of 1500) caused problems with Amix: a mount was possible but any access to files on the NFS share caused "NFS not responding, still trying" | + | * After reboot, Ariadne can be found under /dev/aen0. Without |
- | + | should display something like this: | |
- | For those interested, there is also a short tutorial on [[http://amigadev.elowar.com/ | + | |
- | + | ||
- | ===== Using Amix as a NFS File Server ===== | + | |
- | + | ||
- | By David Miller - Unix Technical Support Specialist, CATS | + | |
- | + | ||
- | //Copied for safekeeping from [[http:// | + | |
- | // | + | |
- | + | ||
- | You've just added an A3000UX to your ethernet and you can rcp and ftp files between UNIX and AmigaDOS using the AS225 TCP/IP software. Great! But what about the AS225' | + | |
- | Under AmigaDOS, the NFS software lets your Amiga mount the drives of a NFS server as normal DOS volumes, but how do you set up a server? | + | |
- | + | ||
- | NFS allows one machine to share files with other machines connected to a network. NFS lets multiple machines access the same files, so only one copy of the data is necessary. A client machine (a client is any machine that can mount a shared directory) can free some of its disk space by moving common programs to the server' | + | |
- | + | ||
- | There are however limitations when sharing files between machines with different operating systems. For example; | + | |
- | + | ||
- | * Filenames - UNIX S5 filesystem does not support filenames longer than 14 characters. If you copy files from AmigaDOS to UNIX, make sure that they are unique in the first 14 characters. And don't forget about the " | + | |
- | + | ||
- | | + | |
- | + | ||
- | | + | |
- | + | ||
- | The following notes will walk you step-by-step through the process of configuring and administering NFS on the A3000UX. | + | |
- | + | ||
- | To keep this article brief, I'm making the following assumptions: | + | |
- | + | ||
- | | + | |
- | | + | |
- | + | ||
- | If you don't, read the Learning Amiga UNIX and Using Amiga UNIX manuals which come with the A3000UX. | + | |
- | + | ||
- | The five examples illustrate how to do some simple file sharing with NFS. Using the concepts discussed in these examples you will be able to select the options necessary to share files while maintaining system security and integrity. But, first, you need to start the networking software on the A3000UX, if it's not already running. | + | |
- | + | ||
- | < | + | |
- | + | ||
- | This changes the operating to run-level 3, the networking run-level. Other run-levels include: | + | |
< | < | ||
- | S - single user maintenance mode | + | aen0: flags=23<UP, BROADCAST, NOTRAILERS> |
- | 0 - system power off | + | |
- | 1 - single user mode | + | |
- | 2 - multiuser mode w/o networking | + | |
- | 3 - multiuser mode w/ networking | + | |
- | 4 - user defined | + | |
- | 5 - system reboot | + | |
- | 6 - system reboot | + | |
- | </ | + | |
- | + | ||
- | To find out what your machine' | + | |
- | + | ||
- | < | + | |
- | + | ||
- | The output will look something like this: | + | |
- | + | ||
- | < | + | |
- | + | ||
- | Here's what all of that means: | + | |
- | + | ||
- | < | + | |
- | | + | |
- | | + | |
- | | | | | | | + | |
- | This is the | + | |
- | current state | | | | | + | |
- | of your machine | + | |
- | | + | |
- | This is when the current ______| | + | |
- | run-level was entered | + | |
- | | | | | + | |
- | This is the current run-level ____________| | + | |
- | | + | |
- | This is the number of times | | | + | |
- | your machine has been in this _________________| | + | |
- | run-level before. | + | |
- | | | + | |
- | This is the previous run-level _____________________| | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | This is the host table (/ | + | |
- | + | ||
- | < | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | 127.0.0.1 | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # IP Number | + | |
- | # | + | |
- | 192.9.120.1 | + | |
- | 192.9.120.2 | + | |
- | 192.9.120.3 | + | |
- | 192.9.120.4 | + | |
- | 192.9.120.5 | + | |
- | 192.9.120.6 | + | |
- | 192.9.120.7 | + | |
- | 192.9.120.8 | + | |
- | 192.9.120.9 | + | |
- | 192.9.120.10 | + | |
- | </ | + | |
- | + | ||
- | The host table contains a list of IP addresses with node names for each of those addresses. The machine uses this list to find other nodes by their name, rather than their numeric IP address. | + | |
- | + | ||
- | **Example 1** | + | |
- | + | ||
- | Hydrogen has a directory called / | + | |
- | + | ||
- | < | + | |
- | + | ||
- | where: | + | |
- | + | ||
- | share is the command to share files between hosts. | + | |
- | -F nfs tells the program share to use the NFS filesystem. | + | |
- | -o rw tells the program share to allow all systems both read and write access to the shared files. This is the default if you don't supply any options. I've just included it here for completeness. | + | |
- | / | + | |
- | + | ||
- | **Example 2** | + | |
- | + | ||
- | Hydrogen also has a large disk attached as /storage. To allow other hosts to use this as extra disk space type the following: | + | |
- | + | ||
- | < | + | |
- | share -F nfs -o rw=Helium / | + | |
- | share -F nfs -o rw=Lithium / | + | |
- | ... | + | |
- | share -F nfs -o rw=Ne / | + | |
- | </code> | + | |
- | where: | + | |
- | + | ||
- | -o rw=name tells share to allow < | + | |
- | + | ||
- | This establishes private storage areas for each host. This way all of the hosts can share the disk without having their files readable by everyone on the network. | + | |
- | + | ||
- | Note the use of the nickname Ne for the host Neon. Nicknames must be explicitly entered in the host table and may be used interchangeably with the full name of the host. | + | |
- | + | ||
- | **Example 3** | + | |
- | + | ||
- | A group of hosts on the first floor of your building are all being used on one big project, so they need a common work area to store files. The administrator could create a work area in /storage called, for example, ff-project, for first-floor-project, | + | |
- | + | ||
- | <code> share -F nfs -o rw=Boron: | + | |
- | + | ||
- | where: | + | |
- | + | ||
- | -o rw=name[: | + | |
- | + | ||
- | / | + | |
- | + | ||
- | **Example 4** | + | |
- | + | ||
- | Hydrogen has a directory called / | + | |
- | + | ||
- | < | + | |
- | + | ||
- | where: | + | |
- | + | ||
- | -o ro tells share to make the shared filesystem readable to all hosts and writable by no one. The ro stands for read-only and | + | |
- | + | ||
- | / | + | |
- | + | ||
- | The files are shared read-only for two reasons. The first is that it prevents temporary files from being created in the shared partition. Also it prevents accidental or malicious removal of shared files. | + | |
- | + | ||
- | **Example 5** | + | |
- | + | ||
- | Now, coincidentally, | + | |
- | + | ||
- | < | + | |
- | + | ||
- | where: | + | |
- | + | ||
- | -o ro=name[: | + | |
- | + | ||
- | / | + | |
- | + | ||
- | These options may be combined to allow different types of access. For example: | + | |
- | + | ||
- | * -o rw=Helium: | + | |
- | + | ||
- | * -o rw, | + | |
- | + | ||
- | * -o rw=C:O,ro=N Carbon and Oxygen have read and write access, Nitrogen has read access, and the others have no access. | + | |
- | + | ||
- | To summarize: | + | |
- | + | ||
- | * -o ro Gives everyone read-only access to the shared files | + | |
- | * -o rw Gives everyone read/write access | + | |
- | * -o ro=... | + | |
- | * -o rw=... | + | |
- | + | ||
- | If a host appears in both a rw= and a ro= list, the host will be given read and write access. The ordering of the options does not matter. | + | |
- | + | ||
- | Since you probably want these directories to be shared automatically every time you start Amiga UNIX, you need to perform the following steps: | + | |
- | + | ||
- | < | + | |
- | 1. Edit the file / | + | |
- | + | ||
- | | + | |
- | to | + | |
- | | + | |
- | + | ||
- | This will make your machine go directly to run-level 3 when you boot | + | |
- | the UNIX Operating System. | + | |
- | + | ||
- | + | ||
- | 2. Edit the file / | + | |
- | to be shared. | + | |
- | + | ||
- | share -F nfs -o ro / | + | |
- | + | ||
- | So, the complete dfstab for the 5 examples given above would look | + | |
- | | + | |
- | + | ||
- | # | + | |
- | # For Example 1 | + | |
- | # | + | |
- | share -F nfs -o rw / | + | |
- | + | ||
- | # | + | |
- | # For Example 2 | + | |
- | # | + | |
- | share -F nfs -o rw=Hydrogen / | + | |
- | share -F nfs -o rw=Helium / | + | |
- | share -F nfs -o rw=Lithium / | + | |
- | share -F nfs -o rw=Beryllium / | + | |
- | share -F nfs -o rw=Boron / | + | |
- | share -F nfs -o rw=Carbon / | + | |
- | share -F nfs -o rw=Nitrogen / | + | |
- | share -F nfs -o rw=Oxygen / | + | |
- | share -F nfs -o rw=Fluorine / | + | |
- | share -F nfs -o rw=Neon / | + | |
- | + | ||
- | # | + | |
- | # For Example 3 | + | |
- | # | + | |
- | share -F nfs -o rw=Boron: | + | |
- | + | ||
- | # | + | |
- | # For Example 4 | + | |
- | # | + | |
- | share -F nfs -o ro / | + | |
- | + | ||
- | # | + | |
- | # For Example 5 | + | |
- | # | + | |
- | share -F nfs -o ro=He: | + | |
- | + | ||
- | + | ||
- | 3. Run the command: | + | |
- | + | ||
- | | + | |
- | + | ||
- | which will share all of the NFS filesystems, | + | |
- | + | ||
- | | + | |
- | + | ||
- | which will make the NFS filesystems unavailable. | + | |
- | </ | + | |
- | + | ||
- | For those interested in more information on UNIX SVR4 networking, either as a user or an administrator, | + | |
- | + | ||
- | < | + | |
- | If you have any suggestions for the new Amiga UNIX section of Amiga Mail, please send it to me either via email: | + | |
- | + | ||
- | davidm@cbmvax.commodore.com | + | |
- | or | + | |
- | ...!{rutgers, | + | |
- | + | ||
- | or US Mail: | + | |
- | + | ||
- | ATTN: David Miller | + | |
- | Commodore Applications and Technical Support | + | |
- | Commodore Business Machines, Inc. | + | |
- | 1200 Wilson Drive | + | |
- | West Chester, PA 19380 | + | |
- | + | ||
- | or FAX: | + | |
- | + | ||
- | David Miller | + | |
- | Commodore Business Machines | + | |
- | +1 215 431 9156 | + | |
- | + | ||
- | or BIX: | + | |
- | david.miller | + | inet 127.0.0.1 netmask FF000000 broadcast 127.255.255.255 |
</ | </ |
networking.1632067216.txt.gz · Last modified: 2021/09/19 18:00 by 127.0.0.1