On 2013-05-16 22:42, Cory Smelosky wrote:
On Thu, 16 May 2013, Paul_Koning wrote:
My nodes:
9.54 (PYTHON) DECnet/Python router
9.55 (NI1D) DECnet/E, RSTS/E V10.1 on simh
(in area 9 all of my SIMH instances run on Solaris)
9.1 (GEWT) VAX/VMS 7.3 SIMH
9.2 (MINDY) TOPS-20 (Panda) KLH10
9.3 (MISSY) Tru64 AlphaServer ES40
9.4 (MANDY) RSX-11M+ SIMH
9.10 (MARLEY) TOPS-10 7.05 KLH10
9.1023 (A9RTR) Virtual Cisco
also for Connor:
32.1 (FDR) SIMH on Windows Server 2003
DB updated. :-)
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
On 2013-05-16 22:16, Jordi Guillaumes i Pons wrote:
Al 15/05/13 22:52, En/na Cory Smelosky ha escrit:
What does it use for network device?
It's using the NI right now, as it's KLH10.
Speaking of devices... has anyone been succesful configuring KLH10 to
use a tap interface? I have not been able to do that, so I have to share
the host real ethernet, thus making not posible to run two instances of
KLH10 in the same host (unless I run those inside a VM, which is a
little bit overkill).
Oh, and a weird thing... I have a simulated TOPS-10 under KLH10 with
DECNET up and running... but it can talk only to its adjacent nodes. It
seems like the routing node (a simh 780 running VMS 4.7) does not route
traffic (in either direction) when the destination or the source is the
KLH10... Weird.
Are you sure it talks ok with the routing node? I mean, have you actually used any protocol to test, or just noted the adjacency up messages? The reason I ask is that the adjacency up messages are not really enough to be sure that the link really is working.
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
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: 16 May 2013 17:29
To: hecnet
Subject: [HECnet] Another sillyness. More information in the nodename
database on MIM.
This is a totally volontary thing. I've finally come to the point where I
think
that there are a few more pieces of data on nodes that would be
nice/useful
to have from time to time.
So I've extended the nodename database on MIM for this.
The fields that I have added are CPU, OS and location. You can see an
example of values by going to
http://madame.update.uu.se/~bqt/hecnet?node=mim
So, feel free to submit data to me for nodes you know. Or look up
information. Or suggest interfaces that you'd like to get to extract this
information, and I'll try and comply. :-)
Johnny
The following are always on:
5.0123 A5RTR DECnet User Mode Router running on Windows Server 2003
5.8 VAX780 SIMH VMS 5.4 on Raspberry Pi
The following only run occasionally, I have more but the details are not to
hand.
5.10 MICRO1 MicroVAX II VMS 5.4
5.24 MICRO4 MicroVAX II MicroVMS 4.6
5.20 VAX6 VAX 4000-200 running VMS 5.4
5.2 VLC1 VAXstation 4000 VLC running VMS 7.3
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE] On Behalf Of Paul_Koning at Dell.com
Sent: 16 May 2013 22:06
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Another sillyness. More information in the nodename
database on MIM.
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. So it
should be
portable (right now it runs on Mac OS and Linux). And it's easy to
implement
because of the power of Python (for example, the on-NI cache is about 10
lines of code).
Right now I have datalink (Ethernet, SIMH DMC11 emulation, Multinet over
UDP), Routing (Phase IV endnode, L1 router, L2 router, over both datalink
types), MOP (Ethernet only, including console carrier), primitive
monitoring
via HTTP, and about 3% of NSP.
My goal is to make this a pretty complete DECnet implementation (Phase II
through IV all in one). Ideally, that will include an API so you can
write
DECnet applications that use this stack as the protocol implementation.
In
other words, something that looks similar to DECnet sockets API, but
inside
the library it talks to the DECnet/Python daemon, NSP and below live
there.
YOu can see the work in progress at
svn://akdesign.dyndns.org/pydecnet/trunk/pydecnet . No documentation
to speak of yet, I should work on that...
paul
You seem to have got much further than I have. Although I do have enough of
NSP and NICE to allow SH KNOWN CIRCUIT and SH ADJACENT NODES.
Regards
Rob
On May 16, 2013, at 4:16 PM, Jordi Guillaumes i Pons wrote:
Al 15/05/13 22:52, En/na Cory Smelosky ha escrit:
What does it use for network device?
It's using the NI right now, as it's KLH10.
Speaking of devices... has anyone been succesful configuring KLH10 to use a tap interface? I have not been able to do that, so I have to share the host real ethernet, thus making not posible to run two instances of KLH10 in the same host (unless I run those inside a VM, which is a little bit overkill).
Oh, and a weird thing... I have a simulated TOPS-10 under KLH10 with DECNET up and running... but it can talk only to its adjacent nodes. It seems like the routing node (a simh 780 running VMS 4.7) does not route traffic (in either direction) when the destination or the source is the KLH10... Weird.
Are events logged on either node when the packets are dropped? What does Wireshark say is in the packet headers? What does the VAX say in "show node tops10 status" ?
paul
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.
paul
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. So it should be portable (right now it runs on Mac OS and Linux). And it's easy to implement because of the power of Python (for example, the on-NI cache is about 10 lines of code).
Right now I have datalink (Ethernet, SIMH DMC11 emulation, Multinet over UDP), Routing (Phase IV endnode, L1 router, L2 router, over both datalink types), MOP (Ethernet only, including console carrier), primitive monitoring via HTTP, and about 3% of NSP.
My goal is to make this a pretty complete DECnet implementation (Phase II through IV all in one). Ideally, that will include an API so you can write DECnet applications that use this stack as the protocol implementation. In other words, something that looks similar to DECnet sockets API, but inside the library it talks to the DECnet/Python daemon, NSP and below live there.
YOu can see the work in progress at svn://akdesign.dyndns.org/pydecnet/trunk/pydecnet . No documentation to speak of yet, I should work on that...
paul
Oh cool, was just thinking about writing stuff in Python for DECNET. Let me know when the stack is stable.
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. So it should be portable (right now it runs on Mac OS and Linux). And it's easy to implement because of the power of Python (for example, the on-NI cache is about 10 lines of code).
Right now I have datalink (Ethernet, SIMH DMC11 emulation, Multinet over UDP), Routing (Phase IV endnode, L1 router, L2 router, over both datalink types), MOP (Ethernet only, including console carrier), primitive monitoring via HTTP, and about 3% of NSP.
My goal is to make this a pretty complete DECnet implementation (Phase II through IV all in one). Ideally, that will include an API so you can write DECnet applications that use this stack as the protocol implementation. In other words, something that looks similar to DECnet sockets API, but inside the library it talks to the DECnet/Python daemon, NSP and below live there.
YOu can see the work in progress at svn://akdesign.dyndns.org/pydecnet/trunk/pydecnet . No documentation to speak of yet, I should work on that...
paul
On Thu, 16 May 2013, Jordi Guillaumes i Pons wrote:
Al 15/05/13 22:52, En/na Cory Smelosky ha escrit:
What does it use for network device?
It's using the NI right now, as it's KLH10.
Speaking of devices... has anyone been succesful configuring KLH10 to
use a tap interface? I have not been able to do that, so I have to share
the host real ethernet, thus making not posible to run two instances of
KLH10 in the same host (unless I run those inside a VM, which is a
little bit overkill).
Does running two instances work if you specify the mac addresses in the config file? Try dedic=0 enaddr=<mac> ifc=eth0 decnet=1
I don't notice that issue, but I'm binding them to different interfaces on a Sun Quad Fast Ethernet card.
Oh, and a weird thing... I have a simulated TOPS-10 under KLH10 with
DECNET up and running... but it can talk only to its adjacent nodes. It
seems like the routing node (a simh 780 running VMS 4.7) does not route
traffic (in either direction) when the destination or the source is the
KLH10... Weird.
Weird. What's the node number?
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Thu, 16 May 2013, Paul_Koning wrote:
My nodes:
9.54 (PYTHON) DECnet/Python router
9.55 (NI1D) DECnet/E, RSTS/E V10.1 on simh
(in area 9 all of my SIMH instances run on Solaris)
9.1 (GEWT) VAX/VMS 7.3 SIMH
9.2 (MINDY) TOPS-20 (Panda) KLH10
9.3 (MISSY) Tru64 AlphaServer ES40
9.4 (MANDY) RSX-11M+ SIMH
9.10 (MARLEY) TOPS-10 7.05 KLH10
9.1023 (A9RTR) Virtual Cisco
also for Connor:
32.1 (FDR) SIMH on Windows Server 2003
paul
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments