[HECnet] Configuring py-decnet.
jy at xtra.co.nz
jy at xtra.co.nz
Tue Aug 25 16:24:15 PDT 2020
Hi Thord,
Congratulations, I can see you're up at:
http://akdesign.dyndns.org:8080/map/data
I just tried a set host elvira and set hsot 59.53 but I'm getting "network object unknown at remote node".
Cheers, John
> On 26 August 2020 at 11:14 Thord Nilson <thordn at gmail.com> wrote:
>
> Hi all!
> Update!
> Basic connections are now working, so for a limited time you can:
> set host elvira::
> login as 99,99 psw: testing
> Nothing much to see though.
> Thanks to all for your help!
>
> /Thord.
>
>
>
> Den tis 25 aug. 2020 kl 00:35 skrev Thord Nilson < thordn at gmail.com mailto:thordn at gmail.com >:
>
> > > Hi!
> > Yes, I missed the part about the special mac-address, will test that now!
> > Thanks all!
> >
> >
> > Den mån 24 aug. 2020 kl 03:47 skrev David Moylan < djm at wiz.net.au mailto:djm at wiz.net.au >:
> >
> > > > >
> > > If anyone else has responded to this e-mail and hasn’t received back a response from the list – it’s because the e-mail is too large.
> > >
> > >
> > >
> > > Reply back to this message as I’ve trimmed it down.
> > >
> > >
> > >
> > > Supratim – I went to reply back to your message below. Apparantly “LOL” translated into Swedish is still “LOL” J
> > >
> > >
> > >
> > > Cheers, Wiz!!
> > >
> > >
> > >
> > >
> > >
> > > From: owner-hecnet at Update.UU.SE mailto:owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE mailto:owner-hecnet at Update.UU.SE ] On Behalf Of Supratim Sanyal
> > > Sent: Monday, 24 August 2020 9:54 AM
> > > To: hecnet at Update.UU.SE mailto:hecnet at Update.UU.SE
> > > Subject: Re: [HECnet] Configuring py-decnet.
> > >
> > >
> > >
> > > On 8/23/20 6:57 PM, Peter Lothberg wrote:
> > >
> > > > > > >
> > > > http://supratim.sanyal.org/decnet-mac-address-scssystemid-converter.html?i=1
> > > >
> > > >
> > > >
> > > > Jag sa att man inte hade ARP..
> > > >
> > > >
> > > >
> > > > de sissta 16 bitarna {r 6-bitar area + 10 bitar nodummer i mac adressen
> > > >
> > > > > > >
> > > yippee mitt lilla javascript är mer populärt än powerdog industrier (och google translate förhoppningsvis fungerar!)
> > >
> > >
> > >
> > >
> > >
> > > > > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > >
> > > > From: "David Moylan" <djm at wiz.net.au> mailto:djm at wiz.net.au
> > > >
> > > > To: "hecnet" <hecnet at Update.UU.SE> mailto:hecnet at Update.UU.SE
> > > >
> > > > Sent: Sunday, August 23, 2020 6:42:45 PM
> > > >
> > > > Subject: RE: [HECnet] Configuring py-decnet.
> > > >
> > > >
> > > >
> > > > Hi Thord,
> > > >
> > > >
> > > >
> > > > You also have two GRE definitions which looks wrong.
> > > >
> > > >
> > > >
> > > > You should have one circuit definition for PyDECnet to listen on the tap interface and another for your tunnel to Peter.
> > > >
> > > > I don't know what this line is for:
> > > >
> > > >
> > > >
> > > > circuit gre-0 GRE 192.168.12.161 <-- This is real address to host machine.
> > > >
> > > >
> > > >
> > > > You also have two network adapters on your emulated machine - if you setup a local bridge, there is no requirement for this.
> > > >
> > > >
> > > >
> > > > RSTS > xq > tap interface > bridge
> > > >
> > > > PyDECnet > tap interface > bridge
> > > >
> > > > Ethernet interface > bridge
> > > >
> > > > Configure IP address on bridge
> > > >
> > > >
> > > >
> > > > Then configure PyDECnet to listen on the tap interface and run the GRE tunnel to Peter.
> > > >
> > > >
> > > >
> > > > You can also use pcap as you have configured below which I understand works fine. I personally use the tap interface directly with the PyDECnet patch as posted earlier.
> > > >
> > > >
> > > >
> > > > In my case, I have tap91 going to my emulated vax (I chose this because the vax is 35.91 and I wanted to use a numbering system that reflected this).
> > > >
> > > > I have tap1023 configured for PyDECnet.
> > > >
> > > >
> > > >
> > > > In my vax.ini file I have:
> > > >
> > > >
> > > >
> > > > ; this is decnet phase iv node 35.91
> > > >
> > > > set xq mac=AA-00-04-00-5B-8C
> > > >
> > > > attach xq tap:tap91
> > > >
> > > >
> > > >
> > > > and an example pydecnet.conf:
> > > >
> > > >
> > > >
> > > > circuit tap-1023 Ethernet tap:tap1023 --random-address
> > > >
> > > > circuit gre-12 GRE 11.22.33.44 --cost 5
> > > >
> > > >
> > > >
> > > > as posted just below, the MAC address must be the correct one for your DECnet host.
> > > >
> > > > The example above uses my MAC address for my 35.91 node.
> > > >
> > > >
> > > >
> > > > There is a conversion page here that you can use:
> > > >
> > > > http://powerdog.com/addrconv.cgi
> > > >
> > > >
> > > >
> > > > and Peter has already done one of the calculations for you below.
> > > >
> > > >
> > > >
> > > > cheers, Wiz!!
> > > >
> > > >
> > > >
> > > > > > > > >
> > > > > -----Original Message-----
> > > > >
> > > > > From: owner-hecnet at Update.UU.SE mailto:owner-hecnet at Update.UU.SE [mailto:owner-
> > > > >
> > > > > hecnet at Update.UU.SE mailto:hecnet at Update.UU.SE] On Behalf Of Peter Lothberg
> > > > >
> > > > > Sent: Monday, 24 August 2020 6:43 AM
> > > > >
> > > > > To: hecnet
> > > > >
> > > > > Subject: Re: [HECnet] Configuring py-decnet.
> > > > >
> > > > >
> > > > >
> > > > > 59.53 is aa00.0400.35ec
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > >
> > > > > From: "bqt" <bqt at softjar.se> mailto:bqt at softjar.se
> > > > >
> > > > > To: "hecnet" <hecnet at Update.UU.SE> mailto:hecnet at Update.UU.SE
> > > > >
> > > > > Sent: Sunday, August 23, 2020 4:32:37 PM
> > > > >
> > > > > Subject: Re: [HECnet] Configuring py-decnet.
> > > > >
> > > > >
> > > > >
> > > > > Um, Thord. You do know that DECnet expects very specific MAC addresses
> > > > >
> > > > > to work, right?
> > > > >
> > > > >
> > > > >
> > > > > Johnny
> > > > >
> > > > >
> > > > >
> > > > > On 2020-08-23 22:29, Thord Nilson wrote:
> > > > >
> > > > > > > > > > >
> > > > > > Hi!
> > > > > >
> > > > > > Great!
> > > > > >
> > > > > > The System is Slackware 14.2 with kernel 4.10.13 running on bare iron.
> > > > > >
> > > > > > (moved to another machine not to mess so much with network on main
> > > > > >
> > > > > > > > > > >
> > > > > machine)
> > > > >
> > > > > > > > > > >
> > > > > > There is traffic on the virtual interface dnettap0 (see below) but rsts
> > > > > >
> > > > > > does not seem to see the py-router.
> > > > > >
> > > > > > Is there some "magical" command to enable this or is it automatic?
> > > > > >
> > > > > > Any ideas?
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > > Thord.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > The config i have now is, in simh:
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > > ; DECnet 59.53
> > > > > >
> > > > > > set xq enable
> > > > > >
> > > > > > set xq type=DELQA mac=DE-18-6B-DB-21-F6
> > > > > >
> > > > > > att xq tap:dnettap0
> > > > > >
> > > > > > ;set xqb enable
> > > > > >
> > > > > > set xqb disable
> > > > > >
> > > > > > set xqb type=DELQA mac=96-72-A1-2A-E7-40
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > > The dnettap0 virtual interface looks like this:
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > > $ /sbin/ifconfig dnettap0
> > > > > >
> > > > > > dnettap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> > > > > >
> > > > > > inet 192.168.12.162 netmask 255.255.255.0 broadcast
> > > > > >
> > > > > > 192.168.12.255
> > > > > >
> > > > > > inet6 fe80::a3d3:3542:9b47:9a19 prefixlen 64 scopeid 0x20<link>
> > > > > >
> > > > > > ether de:18:6b:db:21:f6 txqueuelen 1000 (Ethernet)
> > > > > >
> > > > > > RX packets 35373 bytes 5842616 (5.5 MiB)
> > > > > >
> > > > > > RX errors 0 dropped 442 overruns 0 frame 0
> > > > > >
> > > > > > TX packets 19809 bytes 7619336 (7.2 MiB)
> > > > > >
> > > > > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > > In rsts i can do:
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > > $ sho dev _xh0:
> > > > > >
> > > > > > Device _XH0: (DELQA) Control QNA-0 CSR 774456 Def Addr:
> > > > > >
> > > > > > DE-18-6B-DB-21-F6
> > > > > >
> > > > > > $ ncp
> > > > > >
> > > > > > NCP>show known nodes
> > > > > >
> > > > > > Known Node Volatile Summary as of 23-AUG-20 09:04:05
> > > > > >
> > > > > >
> > > > > >
> > > > > > Executor Node = 59.53 (ELVIRA)
> > > > > >
> > > > > >
> > > > > >
> > > > > > State = On
> > > > > >
> > > > > > Identification = DECnet/E V4.1
> > > > > >
> > > > > > Active Links = 0
> > > > > >
> > > > > >
> > > > > >
> > > > > > Remote Node = 59.20 (KICKI)
> > > > > >
> > > > > >
> > > > > >
> > > > > > Circuit = QNA-0
> > > > > >
> > > > > >
> > > > > >
> > > > > > Remote Node = 59.40 (VERA)
> > > > > >
> > > > > >
> > > > > >
> > > > > > Circuit = QNA-0
> > > > > >
> > > > > > NCP>
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > > The nodes kicki and vera are the ones i defined during install.
> > > > > >
> > > > > > The pydecnet configuration file looks like this:
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > > # Test for now.
> > > > > >
> > > > > > # Configuration file
> > > > > >
> > > > > > #circuit tap-0 Ethernet tap:/dev/dnettap0 --console Plugh --random-
> > > > > >
> > > > > > > > > > >
> > > > > address
> > > > >
> > > > > > > > > > >
> > > > > > #circuit tap-0 Ethernet tap:/dev/tap0 --console Plugh --random-address
> > > > > >
> > > > > > circuit tap-0 Ethernet pcap:dnettap0 --console Plugh --hwaddr
> > > > > >
> > > > > > de-18-6b-db-21-f6 --cost 10
> > > > > >
> > > > > > #circuit tap-0 Ethernet pcap:tap0 --console Plugh --random-address
> > > > > >
> > > > > > #circuit eth-1 Ethernet pcap:en1
> > > > > >
> > > > > > #circuit dmc-0 SimhDMC http://127.0.0.1:11042 <http://127.0.0.1:11042> http://127.0.0.1:11042
> > > > > >
> > > > > > #circuit dmc-0 Multinet localhost:7000
> > > > > >
> > > > > > #circuit dmc-0 Multinet localhost:700:connect
> > > > > >
> > > > > > #circuit dmc-1 SimhDMC localhost:11043:secondary
> > > > > >
> > > > > > #circuit dmc-2 DDCMP tcp:12345:localhost:32154 --cost 3
> > > > > >
> > > > > > #circuit dmc-2 DDCMP udp:12345:localhost:32154 --cost 3
> > > > > >
> > > > > > #circuit dmc-0 DDCMP serial:/dev/tty.usbserial-FTVSKM26:19200 --t3 120
> > > > > >
> > > > > > --qmax 2
> > > > > >
> > > > > > circuit gre-0 GRE 192.168.12.161 <-- This is real address to host machine.
> > > > > >
> > > > > > circuit gre-1 GRE remote.addr.to.peter
> > > > > >
> > > > > >
> > > > > >
> > > > > > routing 59.100 --type l1router
> > > > > >
> > > > > >
> > > > > >
> > > > > > node @nodenames.dat
> > > > > >
> > > > > >
> > > > > >
> > > > > > system --ident "Sample PyDECnet configuration"
> > > > > >
> > > > > >
> > > > > >
> > > > > > # This replaces the default built-in mirror object which is
> > > > > >
> > > > > > # implemented as a Python module within PyDECnet by a functionally
> > > > > >
> > > > > > # equivalent one that runs as a subprocess.
> > > > > >
> > > > > > object --number 25 --name MIRROR --file ../decnet/applications/mirror.py
> > > > > >
> > > > > > ----------------------------------------------
> > > > > >
> > > > > >
> > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > >
> > >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20200826/ca5c7991/attachment-0001.html>
More information about the Hecnet-list
mailing list