For all those who have tunnels to my Cisco 1841, I have switched ISPs and
as such my static IP address has changed. In my configuration I have the
following endpoints configured:
David Moylan (Area 35)
Tomas Prybil (Area 34)
Supratim Sanyal (Area 31)
Brian Hechinger (Area 52)
Ian McLaughlin (Area 42)
Cory Smelosky (Area 9)
Dave McGuire (Area 61)
Peter Lothberg (Area 59)
Mark Darvill (Area 22)
Mark G Thomas (Area 23)
If you are on that list could you please update your tunnel to use my new
address, which is 18.104.22.168.
Mark Berryman, my IPv6 address is unchanged, for the moment.
Why? Because I felt like it and it wasn't too hard.
I have a PyDECnet version that can handle not just IPv4 but also IPv6. It's on node PYTHON right now and on the map server 28NH (at akdesign.dyndns.org). This applies both to the web interface and also to the various IP-based datalink protocols. I've tested Multinet, GRE, Ethernet (UDP bridge) and DDCMP.
If anyone is interested in using this with PYTHON, let me know.
Unfortunately dyndns.org doesn't support IPv6 records well; I can enter one manually but it disappears after a while for reasons I do not understand. It's there now. You can access the mapper's web page (akdesign.dyndns.org:8080) that way if you like.
It appears once upon a time there was some sort of a VMS-like shell on
DOS called PCVMS from Wendin Software. Sampsa asked for it from the last
person to work on it 11 years ago at
Wondering if Sampsa or anyone has floppy images.
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
Do VMS cluster group numbers need to be coordinated on HECnet? If so, is anybody taking care of the coordination yet? I'm getting ready to set up a VAX cluster in my little patch of area 2.
Mark J. Blair, NF6X <nf6x at nf6x.net>
After checking your website SEO metrics and ranks, we determined that you
can get a real boost in ranks and visibility by using any of our plan below
cheap and effective SEO plan
onpage SEO included
For the higher value plans, DA50 DR50 TF20 SEO metrics boost is inlcuded
support at cheapseosolutions.co
Recently I have found, and fixed, a number of bugs in the DECnet for Linux kernel module. Some of
these bugs may be relevant for members of this mailing list who are using DECnet for Linux,
especially on a Raspberry Pi.
Major bugs fixed:
- Ethernet Listen Timer was not implemented
In addition, the check for an address change for the designated router (DR) was missing
although there was a check if the DR?s priority had changed.
Note: this code changes the format of /proc/net/decnet_dev to include the listen timer value.
nml/nml2 needs to be rebuilt to understand the changed format.
- System panic when using the loopback device (lo)
The DECnet code was missing a destructor routine which is used to avoid data copying.
- The neighbour (adjacent node) code could be broken by kernel changes
The code made use of a now deprecated feature (zero length array at the end of a structure)
in order to access data in a surrounding structure. This happened to work ?by chance?
until kernel 5.4.42 on 32-bit processors.
- Interrupt message flow control was broken
The flow control was a mixture of using the SEND/DONTSEND status of the data
subchannel and a message count. This seems to work between Linux systems but is broken
when communicating with other systems - during the life of a logical link, the remote system
could only send a single interrupt message while the Linux system could pretty much send
as many interrupts as it wanted possibly overrunning the remote systems buffers.
- Optional data on received connect confirm message was corrupted
The code was getting the optional data from the wrong offset in the message.
- Next hop cache problem
30 seconds after a logical link was taken down, the next hop cache entry was deleted. As
part of this deletion, the link was taken ?down? which caused a neighbour entry to be
created for the same node address but accessed via the loopback device. Sometimes this
would cause the designated router to become accessible via the loopback device and
subsequent connections would fail.
- Intra-ethernet bit ignored
The intra-ethernet bit in the routing flags is ignored on inbound traffic. If there was a neighbour
entry for the remote node at connection time, everything would work correctly. If there wad no
entry, all outbound traffic would be sent through the designated router for the duration of
the logical link.
- Promiscuous mode alters DECnet behaviour
If the ethernet NIC used for DECnet had promiscuous mode enabled (e.g. using tcpdump
for traffic tracing), the DECnet code would start seeing endnode hello?s, populating
neighbour structures and causing the problems described above for the intra-ethernet bit
to go away.
DECnet Test Send and DECnet Test Receiver (DTS/DTR)
Test programs created via reverse engineering the protocol exchanges. Used to find a
number of the bugs described above.
New implementation of the Network Management Listener. Supports SUMMARY, STATUS
and CHARACTERISTICS for NODES, CIRCUITS and AREAS. It does not support LINKS
and OBJECTS which were in the old version but are system specific operations which
were only visible from DECnet-VMS systems.
The old version is still the default during installation. The new version can be installed by:
sudo make install
which will overwrite the installed executable and man page.
As of 06/29/2020 the code has been tested with:
Raspbian 2020-05-27 release with kernels 4.19.126 and 5.4.44 (32-bit only)
Pi OS 2020-05-27 32-bit release with kernel 4.19.126 and 5.4.44
pI OS 2020-05-27 (fully updated on 06/26/2020) with kernel 5.4.49
The source code and installation instructions are available at: