[HECnet] Configuring py-decnet.
David Moylan
djm at wiz.net.au
Sun Aug 23 15:42:45 PDT 2020
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] 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>
> To: "hecnet" <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 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
> > ----------------------------------------------
> >
> >
> >
> >
> > Den lör 22 aug. 2020 kl 17:50 skrev David Moylan <djm at wiz.net.au
> > <mailto:djm at wiz.net.au>>:
> >
> > I used to be a hardcore Slackware head. I ran everything from the
> > earliest releases on a 0.99 kernel back in the 90’s and used it for
> > all of my Linux work exclusively until around 2015.____
> >
> > In the past few years I was forced to move across to something
> > different – PHP was the thing that forced me to move across.____
> >
> > __ __
> >
> > Slackware has the “you run the entire distribution and the latest
> > version” approach which is fine, but as I was using Linux more and
> > more for application server work, I starting hitting problems with
> > PHP. Slackware was moving up to newer releases of PHP all the time,
> > but I had some application code that only worked under earlier
> > releases of PHP. ____
> >
> > __ __
> >
> > It’s not possible to run multiple releases of PHP side by side under
> > Slackware without hard custom installs, but Linux distributions such
> > as Debian and Ubuntu handle it with ease.____
> >
> > __ __
> >
> > Back in the day I really enjoyed doing everything by hand, building
> > everything from source and custom configurations for clients, but
> > now I’m using Linux more and more for customer application and
> > appliance work, and I don’t have the time to mess around and need to
> > get on with the job as efficiently as possible.____
> >
> > __ __
> >
> > Slackware has a very basic packaging system, and no dependency
> > management. You are also reliant on other people writing package
> > install scripts (Slackbuilds) or you do it yourself. We’ve all
> > encountered compatibility issues, or library conflicts, or other
> > issues that require remediation. With a good package management
> > system (such as apt) you can remove the incorrect libraries and
> > replace them with new ones in minutes, but under Slackware I would
> > be manually cleaning things up and compiling new packages again. Fun
> > as a hobbyist, but a total time killer when you are performing tasks
> > commercially.____
> >
> > __ __
> >
> > I’ve had this occur with deployment work I have done – for example -
> > run up PHP 7.3 and finish the job, to find out that you really need
> > to be running PHP 7.2 for some required dependency and I can fix the
> > problem in minutes with a good package manager.____
> >
> > __ __
> >
> > Fundamentally Slackware is not designed to be “modular” whereas
> > Debian/Ubuntu and others have thousands of premade packages to drop
> > in place. Not to mention many commercial vendors who won’t release
> > code and binaries only and the bulk of them will support Debian,
> > Ubuntu and Redhat as their primary or only release platform.____
> >
> > __ __
> >
> > Sometimes this is a really good thing. Take projects like Unraid for
> > example – this is all based on Slackware. When you are producing and
> > supporting a storage appliance you want a reliable and solid OS
> > underneath.____
> >
> > __ __
> >
> > --____
> >
> > __ __
> >
> > Anyhow – back to our current topic. All of my original simh and
> > DECnet was all done under Slackware and I still have heaps of notes
> > on how I set it all up.____
> >
> > __ __
> >
> > Thord – if this is the platform you are running, let me know – and
> > also if you are running this as bare metal or under a hypervisor
> > (VMware ESXi, HyperV, Virtualbox etc). I can build up a Slackware VM
> > and config it up so I can provide you with very specific notes.____
> >
> > __ __
> >
> > PDP11 and VAX use the same networking in respect to the SIMH side of
> > things. I can’t assist with anything RSTS/E related, but I would
> > assume that someone on the list would be able to assist us if
> > something on your actual simulated machine required changing that
> > you were aware of how to do.____
> >
> > __ __
> >
> > Let me know your configuration and whether I can assist.____
> >
> > __ __
> >
> > 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:* Saturday, 22 August 2020 10:11 PM
> > *To:* hecnet at update.uu.se <mailto:hecnet at update.uu.se>
> > *Subject:* Re: [HECnet] Configuring py-decnet.____
> >
> > __ __
> >
> > I believe he is running slackware 14.2 with 5.2.2 kernel and a
> > pretty recent ____
> >
> > Simh 6fdc4474____
> >
> >
> >
> > ____
> >
> > Lots of people seem to prefer Slackware as the host ... someday need
> > to try it____
> >
> > ---____
> >
> > Supratim Sanyal, W1XMT____
> >
> > 39.19151 N, 77.23432 W____
> >
> > QCOCAL::SANYAL via HECnet
> <http://www.update.uu.se/~bqt/hecnet.html>____
> >
> > __ __
> >
> >
> > On Aug 22, 2020, at 7:38 AM, David Moylan <djm at wiz.net.au
> > <mailto:djm at wiz.net.au>> wrote:____
> >
> > PyDECnet certainly does GRE. That's why we all love Paul's work
> > so much. It contains support for GRE, Multinet and your bridge
> > code all in the one product.
> > I was able to move from my old Cisco router across to PyDECnet
> > and maintain all of my existing GRE tunnels with no reconfiguration.
> >
> > From what I interpret, Thord is running an emulated RSTS/E
> > system on simh and wants to run PyDECnet on the same host to
> > establish a connection upstream.
> >
> > Thord - I have a similar setup, but I'm running VMS. Here's how
> > I have it setup:
> >
> > - my host running is Ubuntu 18.04.2
> > - physical Ethernet (it's called "ens160" because I run VMware)
> > - tap interfaces for each of my VMS simh machines
> > - a tap interface for PyDECnet
> > - I bring all of my tap interfaces and my physical ethernet
> > together into a bridge interface
> > - the bridge interface has my IP address bound to it.
> >
> > PyDECnet is setup with the first circuit connected to the tap
> > adapter I reserved for PyDECnet above.
> > I then have circuit entries for each of the connections to the
> > other area routers and end nodes I am connected to on HECnet.
> >
> > I assume that you should be able to achieve the same with RSTS/E
> > on simh.
> >
> > Let me know if you want more specific details (and let me know
> > what your OS version etc is). I can provide more granular
> > configuration information on my setup which you should be able
> > to use as a template for your own setup.
> >
> > Cheers, Wiz!!
> >
> >
> > ____
> >
> > -----Original Message-----____
> >
> > From: owner-hecnet at Update.UU.SE
> > <mailto:owner-hecnet at Update.UU.SE> [mailto:owner-
> > <mailto:owner->____
> >
> > hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>] On Behalf
> > Of Johnny Billquist____
> >
> > Sent: Saturday, 22 August 2020 9:27 PM____
> >
> > To: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>____
> >
> > Subject: Re: [HECnet] Configuring py-decnet.____
> >
> > __ __
> >
> > Indeed I did. I must admit that the picture is unclear. If
> > we're talking____
> >
> > GRE using pydecnet (does it do GRE?), then why the ethernet
> > jump between____
> >
> > pydecnet and GRE? There do need to some something between
> > the____
> >
> > ethernet____
> >
> > and GRE tunnel. My assumption was probably premature.____
> >
> > __ __
> >
> > Johnny____
> >
> > __ __
> >
> > On 2020-08-22 13:23, David Moylan wrote:____
> >
> > I think you assumed he has a Cisco router :-)____
> >
> > __ __
> >
>
> --
> 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
More information about the Hecnet-list
mailing list