17 Jul
2025
17 Jul
'25
11:23 p.m.
Um... No, PyDECnet does not tunnel DECnet ethernet packets over IP.
You're thinking of my bridge program now, and for sure PyDECnet can also
handle such connections. But PyDECnet can also talk DECnet itself, has
its own node number, and is actually routing DECnet packets,
encapsulating them in TCP, in a way that is completely unrelated to
ethernet. And this is how most people use PyDECnet, and these kind of
links are what we refer to when we say "Multinet" links.
Johnny
On 2025-07-17 23:02, Tony Nicholson wrote:
On Thu, 17 Jul 2025 at 17:53, Michael Brown <mbrown(a)b5.net
<mailto:mbrown@b5.net>> wrote:
On 17/7/25 16:04, Tony Nicholson wrote:
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Michael,
I “upgraded” to phase IV DECnet on all my HECnetmachines - to be
consistent across each of the VAX/Alpha/x86 OpenVMS and PDP-11
operating systems (and I can use my 40-plus years of burnt-in NCP
command memory to manipulate the configurations).
I see, so no DECnet+ peering. Maybe I'll have to explore other options,
I'll look into pydecnet.
If you only want EtherType packets for IPv4 (0x8000) on your network,
then I’m not sure that pydecnet can do this. It normally accepts DECnet/
MOP and LAT (EtherTypes 0x8003, 0x8002 and 0x8004) Ethernet frames
and tunnels them in IPv4 to another router. (It may also do it over IPv6,
but I’ve not tried this).
DECnet-plus runs a phase IV compatibility mode that puts out DECnet
EtherType packets on the “wire” using DECnet MAC addresses. These will
be seen by pydecnet so it will work. What complicates things is the need
to setup compatible phase-IV style naming inside DECnet-plus.
Wiz (aka David Moylan)
Sorry I dyslexised his address.
Tony
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se