12 May
2019
12 May
'19
11:56 p.m.
Can anybody tell me the secret to making DECnet work on Ubuntu 14.04
(Precise)? Yes, this release is out of date but it's the one I need to
use for other compatibility reasons.
I installed the dnet-common, dnet-progs and libdnet packages from the
standard repository. I configured the /etc/decnet.conf and dnet.conf files
(and I don't care about decnet.proxy just yet). Nothing seems to give an
error, the dnetd daemon is running, and the MAC of my eth0 has been changed
to match my DECnet address. dneigh shows the correct adjacent routing node
on the network.
But nothing can communicate. All the DECnet commands (sethost, dnping,
etc) give "socket: no such device" errors, and all the other DECnet machines
on the network think the Linux host is unavailable.
I seem to remember that there was some problem with the DECnet startup
with upstart, but I don't remember the details and Google isn't being
helpful today.
Thanks,
Bob
13 May
13 May
12:20 a.m.
If you haven't, echo xx.yyy > /proc/sys/net/decnet/node_address from rc.local at
boot time, where xx.yyy is your DECnet address. It is completely broken after 14.04
anyway. Erik Olofsen wrote some kernel patches for later kernels and he or others might
chime in. My attempt at a write-up is at
http://supratim-sanyal.blogspot.com/2017/09/the-decnet-linux-experience-it-…
On May 12, 2019, at 5:56 PM, Robert Armstrong <bob
at jfcl.com> wrote:
Can anybody tell me the secret to making DECnet work on Ubuntu 14.04 (Precise)? Yes,
this release is out of date but it?s the one I need to use for other compatibility
reasons.
I installed the dnet-common, dnet-progs and libdnet packages from the standard
repository. I configured the /etc/decnet.conf and dnet.conf files (and I don?t care about
decnet.proxy just yet). Nothing seems to give an error, the dnetd daemon is running, and
the MAC of my eth0 has been changed to match my DECnet address. dneigh shows the correct
adjacent routing node on the network.
But nothing can communicate. All the DECnet commands (sethost, dnping, etc) give
?socket: no such device? errors, and all the other DECnet machines on the network think
the Linux host is unavailable.
I seem to remember that there was some problem with the DECnet startup with upstart,
but I don?t remember the details and Google isn?t being helpful today.
Thanks,
Bob
12:40 a.m.
echo xx.yyy > /proc/sys/net/decnet/node_address
Amazing!! That fixes a lot? Now sethost, dndir and dnping OUT of the Linux machine
(e.g. Linux -> VMS) work fine! Thanks, Supratim?
The VMS machine can talk to FAL on the Linux box (e.g. ?$ DIR linux::?) also.
But ?$ SET HOST? from VMS to Linux gives ?No ptys available for connection?. Seems
bogus to me - cat /proc/sys/kernel/pty/max shows 4096 ptys available. And ?NCP TELL linux
SHOW EXEC? from VMS to Linux gives ?no such file or directory?.
Have you seen either of these problems?
Thanks again,
Bob
12:52 a.m.
But ?$ SET HOST? from VMS to Linux gives ?No ptys
available for connection?.
And ?NCP TELL linux SHOW EXEC? from VMS to Linux gives
?no such file or directory?.
Just finished reading your blog, Supratim. Looks like I have to rebuild both these from
sources to get them to work?
Bob
9:34 a.m.
I've not had any success past 9.10.
I was thinking of rolling my own Linux From Scratch version with a suitably
old kernel.
On Sun, 12 May 2019, 22:55 Robert Armstrong, <bob at jfcl.com> wrote:
Can anybody tell me the secret to making DECnet work
on Ubuntu 14.04
(Precise)? Yes, this release is out of date but it?s the one I need to
use for other compatibility reasons.
I installed the dnet-common, dnet-progs and libdnet packages from the
standard repository. I configured the /etc/decnet.conf and dnet.conf files
(and I don?t care about decnet.proxy just yet). Nothing seems to give an
error, the dnetd daemon is running, and the MAC of my eth0 has been changed
to match my DECnet address. dneigh shows the correct adjacent routing node
on the network.
But nothing can communicate. All the DECnet commands (sethost, dnping,
etc) give ?socket: no such device? errors, and all the other DECnet
machines on the network think the Linux host is unavailable.
I seem to remember that there was some problem with the DECnet startup
with upstart, but I don?t remember the details and Google isn?t being
helpful today.
Thanks,
Bob
2020
days inactive
2021
days old
4 comments
3 participants
participants (3)
-
bob＠jfcl.com -
supratim＠riseup.net -
tonyblews＠gmail.com