[HECnet] Hecnet Peering

[Mark Darvill]

Back to the problem in hand. Any ideas?

Can ping you 12.1023 and 12.2 from the router which is good; can ping 22.10 from the router which is also good; but for some reason i cannot connect from VAX (22.10) on FastEthernet0/1 to 12.2.

This must be a local issue.

Is there anything else I need to setup above what I have for FE0/1 and decnet on my router?

decnet routing 22.100
decnet node-type area

interface FastEthernet0/1
  ip address 10.22.1.254 255.255.255.0
  speed auto
  full-duplex
  lat enabled
  decnet cost 4

and my tunnel to you which I don   t think is the problem

interface Tunnel57
  description HECnet tunnel for Tim Sneddon (Area 12) [Version:274]
  no ip address
  decnet cost 20
  tunnel source FastEthernet0/1
  tunnel destination 120.146.225.243
  tunnel path-mtu-discovery

Mark


On 2 Jan 2015, at 19:38, Hans Vlems <hvlems at zonnet.nl> wrote:
I'll try to find v3.2 tomorrow Paul

Verzonden vanaf mijn BlackBerry 10-smartphone.
   Origineel bericht   
Van: Paul_Koning at Dell.com
Verzonden: vrijdag 2 januari 2015 20:23
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Hecnet Peering


On Jan 2, 2015, at 2:08 PM, Hans Vlems <hvlems at zonnet.nl> wrote:

It would be nice to move the connection off a Linux box to a VMS system.
There is a libpcap version for VMS, it's used by simh.
The problem is Python. AFAIK that i   s just v2.7 for VMS. I know my systems run that kit, but I don't use it much so a newer version may be available. 
Hans

The Python 3.3    what   s new    document says that VMS is no longer supported    due to lack of a maintainer   . So it may be possible to build Python 3.2 on VMS. The current DECnet/Python code wants 3.3, but earlier on I used 3.2 and there isn   t much that needs 3.3. (In other words, it would not be all that hard to change it back to allow 3.2.)

paul