Virtual Distributed Ethernet extended across countries or continents over SSL, works awesome for over 6 years now. SimH supports it natively from the beginning. My virtual switches carry DECnet and AppleTalk Phase-2, no problem. https://supratim-sanyal.blogspot.com/2018/12/netbsd-vax-pi.html



On Nov 9, 2022, at 8:37 PM, Johnny Billquist <bqt@softjar.se> wrote:

And by the way, with that setup under RSX, you can run a DECnet endnode. The only active DECnet link is the multinet link. The ethernet also should be active, but it is only used by TCP/IP.

 Johnny

On 2022-11-10 02:34, Johnny Billquist wrote:
If people want to run DECnet with RSX (or VMS) under simh, using WiFi, there is also another solution.
The primary problem here is that when DECnet is running, the machine is forced to have a MAC address that isn't the native MAC of the WiFi, which means WiFi isn't working that well, especially broadcasts can be a problem.
However, with RSX and VMS, you can set the machine up to just have DECnet over IP links. This don't change the problem with the changed MAC address. However, simh have another trick up the sleeve, which is that it can actually act as a NAT router. Which means the ethernet from the simulated machine is actually local to inside simh, and then you get IP packets routed out to the WiFi interface. Obviously this does not help at all for DECnet, but since you are carrying DECnet inside of IP, it then actually starts working fine. No direct ethernet connections, but otherwise all good.
What you put in the ini-file is something like this:
attach xu nat:tcp=21:10.0.2.15:21,tcp=23:10.0.2.15:23
That tcp= stuff is just because I wanted telnet and ftp to get through from the outside so I could connect to my simh instance from other machines on the WiFi. Done then, obviously, by connecting to the machine where simh is running.
  Johnny
On 2022-11-10 00:07, David Brown wrote:
A way around that I have used when I want to run both TCP/IP and Decnet to a wifi connected node (given that Pydecnet only forwards Decnet frames), is to use VXLAN between the Wifi connected machines and an Ethernet Connected machine.  On the Wifi end, I build a bridge, then put the VXLAN and tap interfaces on that.  On the Ethernet end, again put the Vxlan, ethernet and probably pydecnet.

This was you can avoid running Pydecnet on each machine and you can still do RSX TCP.



On Nov 9, 2022, at 4:10 PM, Paul Koning <paulkoning@comcast.net <mailto:paulkoning@comcast.net>> wrote:

That should be fine.  You can attach an AP to a real Ethernet and have DECnet nodes on the real (wired) section, just not on the Wifi part because of the way it limits addressing.  That assumes, of course, that the AP correctly handles multicast.  There were some reports that some APs get this wrong.  I don't know of any specifics; if such devices exist the solution is to avoid them.  (Anyone who can't understand multicast probably makes other fatal errors, too.)

paul

On Nov 9, 2022, at 11:01 AM, cyb 2600 <cyb2600@gmail.com <mailto:cyb2600@gmail.com>> wrote:

The only machines I use with HECNET are a couple of real VAXen, an Itanium server and a PDP-11 running RSX-11 so simh isn't an issue. They're all connected to a switch along with a wireless access point.

On Wed, Nov 9, 2022 at 10:47 AM Robert Armstrong <bob@jfcl.com <mailto:bob@jfcl.com>> wrote:

    >Paul Koning <paulkoning@comcast.net
    <mailto:paulkoning@comcast.net>> wrote:
    >You can use any of the PyDECnet interface types except "real"
    Ethernet.

      Not really sure if that's what he wants to do or not.     Actually, not
    really sure what configuration he wants, but ...

      Another way of saying this would be that real DECnet over WiFi is
    problematic and the only option is to wrap it in some other
    protocol and
    tunnel it.   If he's got several other computers on his WiFi that
    all want
    to speak DECnet (presumably using simh) then he's going to have
    to run
    pyDECnet on each one of those computers to connect to the RISC
    board running
    pyDECnet.  If he's running Multinet or the RSX TCP stack on those
    simh
    instances then he could possibly avoid using pyDECnet on that
    end, but you
    still have to tunnel the DECnet one way or another.

    Bob

    _______________________________________________
    HECnet mailing list -- hecnet@lists.dfupdate.se
    <mailto:hecnet@lists.dfupdate.se>
    To unsubscribe send an email to hecnet-leave@lists.dfupdate.se
    <mailto:hecnet-leave@lists.dfupdate.se>

_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se <mailto:hecnet@lists.dfupdate.se>
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se <mailto:hecnet-leave@lists.dfupdate.se>

_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se <mailto:hecnet@lists.dfupdate.se>
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se <mailto:hecnet-leave@lists.dfupdate.se>


_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se

--
Johnny Billquist                  || "I'm on a bus
                                 ||  on a psychedelic trip
email: bqt@softjar.se             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol
_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se