9 Nov
2022
9 Nov
'22
5:23 p.m.
Sorry I possibly was a bit vague.
*Last time* I attempted this I think I used a Draytek router with a USB stick running
across 3G. It was a bit unreliable but did work. I configured ports as required in the
router.
I took my HP Microserver which runs the 4.1 area router as a SIMH instance and was able to
then see MIM and others via the bridge software running on the Microserver.
I’m pretty sure I also did something with the 3G USB dongle and a linux laptop, but that
is more vague.
If that is still my easiest option then I could maybe look to do that again.
Thanks for all the info, it’s been a very interesting discussion.
Mark.
--
M0NOM/P ADIF Processor
On 9 Nov 2022 at 16:11 +0000, Paul Koning <paulkoning(a)comcast.net>et>, 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(a)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.
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se On Wed, Nov 9, 2022 at 10:47 AM Robert Armstrong
<bob(a)jfcl.com> wrote:
> >Paul Koning <paulkoning(a)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(a)lists.dfupdate.se
> To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se