blob: 4d7453aa308b27adfef8b216ce81a78b75e9f930 [file] [log] [blame]
osdl.org!shemmingeraba5acd2004-04-15 20:56:59 +00001
2Here are a few quick points about DECnet support...
3
4 o No name resolution is available as yet, all addresses must be
5 entered numerically.
6
7 o The neighbour cache may well list every entry as having the address
8 0.170. This is due to a problem that I need to sort out kernel side.
9 It is harmless (but don't try and use neigh add yet) just look in
10 /proc/net/decnet_neigh to see the real addresses for now.
11
12 o The rtnetlink support in the kernel is rather exprimental, expect a
13 few odd things to happen for the next few DECnet kernel releases.
14
15 o Whilst you can use ip addr add to add more than one DECnet address to an
16 interface, don't expect addresses which are not the same as the
17 kernels node address to work properly. i.e. You will break the DECnet
18 protocol if you do add anything other than the automatically generated
19 interface addresses to ethernet cards. This option is there for future
20 link layer support, where the device will have to be configed for
21 DECnet explicitly.
22
23 o The DECnet support is currently self contained. You do not need the
24 libdnet library to use it. In fact until I've sent the dnet_pton and
25 dnet_ntop functions to Patrick to add, you can't use libdnet.
26
27 o If you are not using the very latest 2.3.xx series kernels, don't
28 try and list DECnet routes if you've got IPv6 compiled into the
29 kernel. It will oops.
30
31 o My main reason for writing the DECnet support for iproute2 was to
32 check out the DECnet routing code, so the route get and
33 route show cache commands are likely to be the most debugged out of
34 all of them.
35
36 o If you find bugs in the DECnet support, please send them to me in the
37 first instance, and then I'll send Alexey a patch to fix it. IPv4/6
38 bugs should be sent to Alexey as before.
39
40Steve Whitehouse <SteveW@ACM.org>
41