[HECnet] Another sillyness. More information in the nodename database on MIM.

[Johnny Billquist]

On 2013-05-16 23:12, Paul_Koning at Dell.com wrote:

On May 16, 2013, at 5:07 PM, Sampsa Laine wrote:


On 16 May 2013, at 23:06, Paul_Koning at Dell.com wrote:


On May 16, 2013, at 4:38 PM, Sampsa Laine wrote:

DECnet/Python? What's this exactly?

sampsa

A project of mine, inspired by the user mode router project Rob Jarratt is doing.   It's the DECnet protocol stack implemented in Python. ...

Oh cool, was just thinking about writing stuff in Python for DECNET. Let me know when the stack is stable.

The routing part looks pretty good right now.   I don't have it active all the time yet, but I hooked it into Multinet and it appeared to be stable.   The main issue is that point to point DECnet over UDP is architecturally invalid; the initialization state machine isn't designed for that.   The result is that it takes a while for both sides to agree that the circuit is "Up".   I've been thinking of workaround for the misbehavior.   A cleaner solution is to run Multinet over TCP, which appears to exist -- if someone can figure out how to do that and what the packet formats look like for that case, I'll implement it.   Alternatively, the SIMH DMC11 protocol works very well, it would clearly be a superior solution for Hecnet.

I haven't looked enough to really make sensible comments, but in which way is point-to-point over UDP invalid? I would have thought that wouldn't be any different than if you had an ethernet segment with just two nodes on it (I'm assuming Multinet UDP tunnels act like ethernet, but I might be wrong on that one as well...)

	Johnny

-- 
Johnny Billquist                                   || "I'm on a bus
                                                                  ||   on a psychedelic trip
email: bqt at softjar.se                         ||   Reading murder books
pdp is alive!                                         ||   tryin' to stay hip" - B. Idol