^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) .. SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) Linux DECnet Networking Layer Information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) 1. Other documentation....
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) - Project Home Pages
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) - http://www.chygwyn.com/ - Kernel info
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) - http://linux-decnet.sourceforge.net/ - Userland tools
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) - http://www.sourceforge.net/projects/linux-decnet/ - Status page
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) 2. Configuring the kernel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) =========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) Be sure to turn on the following options:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) - CONFIG_DECNET (obviously)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) - CONFIG_PROC_FS (to see what's going on)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) - CONFIG_SYSCTL (for easy configuration)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) if you want to try out router support (not properly debugged yet)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) you'll need the following options as well...
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) - CONFIG_DECNET_ROUTER (to be able to add/delete routes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) - CONFIG_NETFILTER (will be required for the DECnet routing daemon)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) Don't turn on SIOCGIFCONF support for DECnet unless you are really sure
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) that you need it, in general you won't and it can cause ifconfig to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) malfunction.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) Run time configuration has changed slightly from the 2.4 system. If you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) want to configure an endnode, then the simplified procedure is as follows:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) - Set the MAC address on your ethernet card before starting _any_ other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) network protocols.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) As soon as your network card is brought into the UP state, DECnet should
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) start working. If you need something more complicated or are unsure how
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) to set the MAC address, see the next section. Also all configurations which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) worked with 2.4 will work under 2.5 with no change.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) 3. Command line options
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) =======================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) You can set a DECnet address on the kernel command line for compatibility
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) with the 2.4 configuration procedure, but in general it's not needed any more.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) If you do st a DECnet address on the command line, it has only one purpose
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) which is that its added to the addresses on the loopback device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) With 2.4 kernels, DECnet would only recognise addresses as local if they
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) were added to the loopback device. In 2.5, any local interface address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) can be used to loop back to the local machine. Of course this does not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) prevent you adding further addresses to the loopback device if you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) want to.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) N.B. Since the address list of an interface determines the addresses for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) which "hello" messages are sent, if you don't set an address on the loopback
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) interface then you won't see any entries in /proc/net/neigh for the local
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) host until such time as you start a connection. This doesn't affect the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) operation of the local communications in any other way though.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) The kernel command line takes options looking like the following::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) decnet.addr=1,2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) the two numbers are the node address 1,2 = 1.2 For 2.2.xx kernels
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) and early 2.3.xx kernels, you must use a comma when specifying the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) DECnet address like this. For more recent 2.3.xx kernels, you may
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) use almost any character except space, although a `.` would be the most
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) obvious choice :-)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) There used to be a third number specifying the node type. This option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) has gone away in favour of a per interface node type. This is now set
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) using /proc/sys/net/decnet/conf/<dev>/forwarding. This file can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) set with a single digit, 0=EndNode, 1=L1 Router and 2=L2 Router.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) There are also equivalent options for modules. The node address can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) also be set through the /proc/sys/net/decnet/ files, as can other system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) parameters.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) Currently the only supported devices are ethernet and ip_gre. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) ethernet address of your ethernet card has to be set according to the DECnet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) address of the node in order for it to be autoconfigured (and then appear in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) /proc/net/decnet_dev). There is a utility available at the above
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) FTP sites called dn2ethaddr which can compute the correct ethernet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) address to use. The address can be set by ifconfig either before or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) at the time the device is brought up. If you are using RedHat you can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) add the line::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) MACADDR=AA:00:04:00:03:04
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) or something similar, to /etc/sysconfig/network-scripts/ifcfg-eth0 or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) wherever your network card's configuration lives. Setting the MAC address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) of your ethernet card to an address starting with "hi-ord" will cause a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) DECnet address which matches to be added to the interface (which you can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) verify with iproute2).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) The default device for routing can be set through the /proc filesystem
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) by setting /proc/sys/net/decnet/default_device to the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) device you want DECnet to route packets out of when no specific route
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) is available. Usually this will be eth0, for example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) echo -n "eth0" >/proc/sys/net/decnet/default_device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) If you don't set the default device, then it will default to the first
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) ethernet card which has been autoconfigured as described above. You can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) confirm that by looking in the default_device file of course.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) There is a list of what the other files under /proc/sys/net/decnet/ do
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) on the kernel patch web site (shown above).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) 4. Run time kernel configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) ================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) This is either done through the sysctl/proc interface (see the kernel web
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) pages for details on what the various options do) or through the iproute2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) package in the same way as IPv4/6 configuration is performed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) Documentation for iproute2 is included with the package, although there is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) as yet no specific section on DECnet, most of the features apply to both
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) IP and DECnet, albeit with DECnet addresses instead of IP addresses and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) a reduced functionality.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) If you want to configure a DECnet router you'll need the iproute2 package
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) since its the _only_ way to add and delete routes currently. Eventually
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) there will be a routing daemon to send and receive routing messages for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) each interface and update the kernel routing tables accordingly. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) routing daemon will use netfilter to listen to routing packets, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) rtnetlink to update the kernels routing tables.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) The DECnet raw socket layer has been removed since it was there purely
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) for use by the routing daemon which will now use netfilter (a much cleaner
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) and more generic solution) instead.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) 5. How can I tell if its working?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) =================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) Here is a quick guide of what to look for in order to know if your DECnet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) kernel subsystem is working.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) - Is the node address set (see /proc/sys/net/decnet/node_address)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) - Is the node of the correct type
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) (see /proc/sys/net/decnet/conf/<dev>/forwarding)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) - Is the Ethernet MAC address of each Ethernet card set to match
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) the DECnet address. If in doubt use the dn2ethaddr utility available
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) at the ftp archive.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) - If the previous two steps are satisfied, and the Ethernet card is up,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) you should find that it is listed in /proc/net/decnet_dev and also
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) that it appears as a directory in /proc/sys/net/decnet/conf/. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) loopback device (lo) should also appear and is required to communicate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) within a node.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) - If you have any DECnet routers on your network, they should appear
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) in /proc/net/decnet_neigh, otherwise this file will only contain the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) entry for the node itself (if it doesn't check to see if lo is up).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) - If you want to send to any node which is not listed in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) /proc/net/decnet_neigh file, you'll need to set the default device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) to point to an Ethernet card with connection to a router. This is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) again done with the /proc/sys/net/decnet/default_device file.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) - Try starting a simple server and client, like the dnping/dnmirror
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) over the loopback interface. With luck they should communicate.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) For this step and those after, you'll need the DECnet library
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) which can be obtained from the above ftp sites as well as the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) actual utilities themselves.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) - If this seems to work, then try talking to a node on your local
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) network, and see if you can obtain the same results.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) - At this point you are on your own... :-)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) 6. How to send a bug report
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) ===========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) If you've found a bug and want to report it, then there are several things
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) you can do to help me work out exactly what it is that is wrong. Useful
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) information (_most_ of which _is_ _essential_) includes:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) - What kernel version are you running ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) - What version of the patch are you running ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) - How far though the above set of tests can you get ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) - What is in the /proc/decnet* files and /proc/sys/net/decnet/* files ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) - Which services are you running ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) - Which client caused the problem ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) - How much data was being transferred ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) - Was the network congested ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) - How can the problem be reproduced ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) - Can you use tcpdump to get a trace ? (N.B. Most (all?) versions of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) tcpdump don't understand how to dump DECnet properly, so including
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) the hex listing of the packet contents is _essential_, usually the -x flag.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) You may also need to increase the length grabbed with the -s flag. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) -e flag also provides very useful information (ethernet MAC addresses))
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) 7. MAC FAQ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) ==========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) A quick FAQ on ethernet MAC addresses to explain how Linux and DECnet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) interact and how to get the best performance from your hardware.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) Ethernet cards are designed to normally only pass received network frames
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) to a host computer when they are addressed to it, or to the broadcast address.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) Linux has an interface which allows the setting of extra addresses for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) an ethernet card to listen to. If the ethernet card supports it, the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) filtering operation will be done in hardware, if not the extra unwanted packets
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) received will be discarded by the host computer. In the latter case,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) significant processor time and bus bandwidth can be used up on a busy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) network (see the NAPI documentation for a longer explanation of these
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) effects).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) DECnet makes use of this interface to allow running DECnet on an ethernet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) card which has already been configured using TCP/IP (presumably using the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) built in MAC address of the card, as usual) and/or to allow multiple DECnet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) addresses on each physical interface. If you do this, be aware that if your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) ethernet card doesn't support perfect hashing in its MAC address filter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) then your computer will be doing more work than required. Some cards
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) will simply set themselves into promiscuous mode in order to receive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) packets from the DECnet specified addresses. So if you have one of these
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) cards its better to set the MAC address of the card as described above
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) to gain the best efficiency. Better still is to use a card which supports
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) NAPI as well.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) 8. Mailing list
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) ===============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) If you are keen to get involved in development, or want to ask questions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) about configuration, or even just report bugs, then there is a mailing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) list that you can join, details are at:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) http://sourceforge.net/mail/?group_id=4993
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) 9. Legal Info
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) =============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) The Linux DECnet project team have placed their code under the GPL. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) software is provided "as is" and without warranty express or implied.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) DECnet is a trademark of Compaq. This software is not a product of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) Compaq. We acknowledge the help of people at Compaq in providing extra
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) documentation above and beyond what was previously publicly available.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) Steve Whitehouse <SteveW@ACM.org>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243)
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags