]>
Commit | Line | Data |
---|---|---|
1 | ||
2 | Here are a few quick points about DECnet support... | |
3 | ||
4 | o iproute2 is the tool of choice for configuring the DECnet support for | |
5 | Linux. For many features, it is the only tool which can be used to | |
6 | configure them. | |
7 | ||
8 | o No name resolution is available as yet, all addresses must be | |
9 | entered numerically. | |
10 | ||
11 | o Remember to set the hardware address of the interface using: | |
12 | ||
13 | ip link set ethX address xx:xx:xx:xx:xx:xx | |
14 | (where xx:xx:xx:xx:xx:xx is the MAC address for your DECnet node | |
15 | address) | |
16 | ||
17 | if your Ethernet card won't listen to more than one unicast | |
18 | mac address at once. If the Linux DECnet stack doesn't talk to | |
19 | any other DECnet nodes, then check this with tcpdump and if its | |
20 | a problem, change the mac address (but do this _before_ starting | |
21 | any other network protocol on the interface) | |
22 | ||
23 | o Whilst you can use ip addr add to add more than one DECnet address to an | |
24 | interface, don't expect addresses which are not the same as the | |
25 | kernels node address to work properly with 2.4 kernels. This should | |
26 | be fine with 2.6 kernels as the routing code has been extensively | |
27 | modified and improved. | |
28 | ||
29 | o The DECnet support is currently self contained. It does not depend on | |
30 | the libdnet library. | |
31 | ||
32 | Steve Whitehouse <steve@chygwyn.com> | |
33 |