Hello,
after a little break, I am back again to this list.
We finally managed to get Linux (Kernel 2.0.36) and xfbbd up and
running. Besides a small problem with xfbbd (seems there is
trouble in its communcation with the kernel sockets, sometimes)
that I put an inquiry for solution for in the xfbb mailing list,
NET/ROM gives us some headaches.
When we boot up our Linux Box, we set the NET/ROM routes that
are necessary to have up for us, eg. for FBB forwarding, using the
nrparms command as described in the AX.25-HOWTO.
Unfortunately, the NET/ROM part of the kernel seems to have
difficulties to recognize these routes.
An example:
nrparms -nodes radio
should set up the NET/ROM subsystem in a way that a
cat /proc/net/nr_nodes
shows an entry with VK2XLZ-10 in it. But sometimes, this entry is
missing, allthough the nrparms command seemed to be processed
without an error.
We actually have the NET/ROM routes setup in our Packet Radio
initialization script that runs at boot time, after setting and
initializing the NET/ROM ports and loading netromd, of course. In
most cases the correct route entries are achieved if we enter the
nrparms commands manually after a console login.
Does it take the NET/ROM subsystem a longer time to initialize
than we expect? If not, what other reason is possible for this
behaviour of NET/ROM?
The background for asking you this is that we want to have this box
running without any user or root intervention to be necessary for
running the AX.25 services.
Thank you for any hint in advance!
Best regards, 73
Gerd
