| 1 | .TH INET 8
|
|---|
| 2 | .SH NAME
|
|---|
| 3 | inet, inet.conf \- TCP/IP server
|
|---|
| 4 | .SH SYNOPSIS
|
|---|
| 5 | .B inet
|
|---|
| 6 | .SH DESCRIPTION
|
|---|
| 7 | .de SP
|
|---|
| 8 | .if t .sp 0.4
|
|---|
| 9 | .if n .sp
|
|---|
| 10 | ..
|
|---|
| 11 | .B Inet
|
|---|
| 12 | is the TCP/IP server. It is a device driver that interfaces between the
|
|---|
| 13 | file server and the low level ethernet device driver. The interface to this
|
|---|
| 14 | server is described in
|
|---|
| 15 | .BR ip (4).
|
|---|
| 16 | .PP
|
|---|
| 17 | .B Inet
|
|---|
| 18 | starts as a normal process, reads a the configuration file
|
|---|
| 19 | .B /etc/inet.conf
|
|---|
| 20 | to see what it should do, and uses a few special low level system calls
|
|---|
| 21 | to turn itself into a server. The format of the configuration file is as
|
|---|
| 22 | follows:
|
|---|
| 23 | .SS Configuration
|
|---|
| 24 | The inet configuration file is fairly simple, here is an example:
|
|---|
| 25 | .PP
|
|---|
| 26 | .RS
|
|---|
| 27 | .ft C
|
|---|
| 28 | .nf
|
|---|
| 29 | eth0 DP8390 0 { default; };
|
|---|
| 30 | psip1;
|
|---|
| 31 | .fi
|
|---|
| 32 | .ft P
|
|---|
| 33 | .RS
|
|---|
| 34 | .PP
|
|---|
| 35 | It tells that network 0 (the one containing devices
|
|---|
| 36 | .BR eth0 ,
|
|---|
| 37 | .BR ip0 ,
|
|---|
| 38 | .BR tcp0
|
|---|
| 39 | and
|
|---|
| 40 | .BR udp0 )
|
|---|
| 41 | uses the ethernet device driver handled
|
|---|
| 42 | by task "DP8390" at port 0. This network is marked as the default
|
|---|
| 43 | network, so most programs use it through the unnumbered devices like
|
|---|
| 44 | .B /dev/tcp
|
|---|
| 45 | or
|
|---|
| 46 | .BR /dev/udp .
|
|---|
| 47 | Network 1 is a Pseudo IP network that can be used for
|
|---|
| 48 | a serial IP over a modem for instance.
|
|---|
| 49 | .PP
|
|---|
| 50 | The configuration file may look like a common configuration file as
|
|---|
| 51 | described by
|
|---|
| 52 | .BR configfile (5),
|
|---|
| 53 | but it is currently just a simple subset allowing only what you see here.
|
|---|
| 54 | The following network definitions are possible:
|
|---|
| 55 | .PP
|
|---|
| 56 | .BI eth N
|
|---|
| 57 | .I task port
|
|---|
| 58 | .RI { options };
|
|---|
| 59 | .RS
|
|---|
| 60 | This sets up an ethernet with device name
|
|---|
| 61 | .BI /dev/eth N\fR,
|
|---|
| 62 | built on the given ethernet device driver at the given port at that driver.
|
|---|
| 63 | (If a network driver manages two network
|
|---|
| 64 | cards then they are at port 0 and 1.)
|
|---|
| 65 | .br
|
|---|
| 66 | .RE
|
|---|
| 67 | .PP
|
|---|
| 68 | .BI eth N
|
|---|
| 69 | .B vlan
|
|---|
| 70 | .I id
|
|---|
| 71 | .BI eth M
|
|---|
| 72 | .RI { options };
|
|---|
| 73 | \0\0\0\0
|
|---|
| 74 | .RS
|
|---|
| 75 | The ethernet
|
|---|
| 76 | .BI eth N
|
|---|
| 77 | uses VLAN number
|
|---|
| 78 | .I id
|
|---|
| 79 | and is built on ethernet
|
|---|
| 80 | .BI eth M\fR.
|
|---|
| 81 | A packet given to this network has a VLAN tag prefixed to it and is then
|
|---|
| 82 | handed over to another ethernet for transmission. Likewise a packet on
|
|---|
| 83 | that ethernet carrying the appropriate VLAN tag has this tag removed and is
|
|---|
| 84 | sent on to this network. The VLAN ethernet behaves like an ordinary ethernet
|
|---|
| 85 | as far as applications are concerned.
|
|---|
| 86 | .RE
|
|---|
| 87 | .PP
|
|---|
| 88 | .BI psip N
|
|---|
| 89 | .RI { options };
|
|---|
| 90 | .RS
|
|---|
| 91 | Creates pseudo IP network
|
|---|
| 92 | .BI /dev/psip N\fR,
|
|---|
| 93 | usable for IP over serial lines, tunnels and whatnot.
|
|---|
| 94 | .RE
|
|---|
| 95 | .SH OPTIONS
|
|---|
| 96 | Some options can be given between braces.
|
|---|
| 97 | .PP
|
|---|
| 98 | .BR default ;
|
|---|
| 99 | .RS
|
|---|
| 100 | Mark this network as the default network. Exactly one of the networks must
|
|---|
| 101 | be so marked.
|
|---|
| 102 | When
|
|---|
| 103 | .B inet
|
|---|
| 104 | is started it will check and create all the necessary network devices before
|
|---|
| 105 | becoming a server. To know what major device number to use it checks
|
|---|
| 106 | .BR /dev/ip ,
|
|---|
| 107 | so that device must already exist. It can be created by
|
|---|
| 108 | .B MAKEDEV
|
|---|
| 109 | if need be.
|
|---|
| 110 | .RE
|
|---|
| 111 | .PP
|
|---|
| 112 | .BR "no ip" ;
|
|---|
| 113 | .br
|
|---|
| 114 | .BR "no tcp" ;
|
|---|
| 115 | .br
|
|---|
| 116 | .BR "no udp" ;
|
|---|
| 117 | .RS
|
|---|
| 118 | These options turn the IP, TCP, or UDP layer off. Inet will not enable the
|
|---|
| 119 | devices for these layers, and will deactivate code for these layers.
|
|---|
| 120 | Disabling IP will also disable TCP or UDP, because they need IP to function.
|
|---|
| 121 | An ethernet without an IP layer can be used as for stealth listening. An IP
|
|---|
| 122 | network without TCP or UDP can be used to pester students into creating the
|
|---|
| 123 | missing functionality. Keeps them off the streets, and maybe they'll learn
|
|---|
| 124 | something.
|
|---|
| 125 | .RE
|
|---|
| 126 | .SH "SEE ALSO"
|
|---|
| 127 | .BR ip (4),
|
|---|
| 128 | .BR boot (8).
|
|---|
| 129 | .SH NOTES
|
|---|
| 130 | The number of networks that can be defined are 2 (Minix-86), 4 (Minix-386)
|
|---|
| 131 | or 16 (Minix-vmd). This limits both the total number and the highest
|
|---|
| 132 | device number you can use.
|
|---|
| 133 | .PP
|
|---|
| 134 | Getting a network administrator to give you a trunk or multi-VLAN port to
|
|---|
| 135 | run multiple networks on can be a challenge. It questions their idea that
|
|---|
| 136 | VLANs are separate networks, while in reality it is just one big ethernet.
|
|---|
| 137 | .SH ACKNOWLEDGMENTS
|
|---|
| 138 | Cindy Crawford, for providing invaluable help debugging this server.
|
|---|
| 139 | .SH AUTHOR
|
|---|
| 140 | .ta \w'Manual:'u+2n
|
|---|
| 141 | Code: Philip Homburg <philip@cs.vu.nl>
|
|---|
| 142 | .br
|
|---|
| 143 | Manual: Kees J. Bot <kjb@cs.vu.nl>
|
|---|
| 144 |
|
|---|
| 145 | .\"
|
|---|
| 146 | .\" $PchId: inet.8,v 1.6 2001/10/08 19:01:35 philip Exp $
|
|---|
