[HECnet] Re: Ad-hoc connection to hecnet?

Presumably, you’ll have two Ethernet ports wlan0 and eth0 with wlan0 configured for tcp/ip and eth0 uncommitted. You could then configure pydecnet for an Ethernet circuit connected to eth0 and a multinet tcp circuit to an endpoint x.y.z.t:p, something like: routing a.h --type l2router logging console circuit mul-0 Multinet --mode connect --destination a.a.a.a --destination-port p circuit eth-0 Ethernet eth0 --mode pcap where a.h is the area and host number of your pydecnet area router and a.a.a.a:p is the address of the hecnet uplink listening for a multinet connection. I think that’s roughly right for the Ethernet connection. I use tap devices associated with a bridge connecting eth0 rather than eth0 directly. You shouldn’t need a separate PC – wifi for the uplink and wired Ethernet for DECnet. From: Mark Wickens [mailto:mark@wickensonline.co.uk] Sent: 07 November 2022 17:42 To: The Hobbyist DECnet mailing list &lt;hecnet(a)lists.dfupdate.se&gt; Subject: [HECnet] Re: Ad-hoc connection to hecnet? Thanks for all the help. I've installed pydecnet onto my HP microserver. It is running Ubuntu linux: Linux hpm 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Also running on this machine is a simh instance called SIMVAX which is my 4.1 area router. It is configured as DECnet Phase IV. At some point in the past I was connected to Steve Davidsons bridge.declab.net:4711<http://bridge.declab.net:4711> via the bridge.c software, however I suspect that hasn't been working for some time. If I could get some help configuring pydecnet to work in a way which means I can then take the HP Microserver with me and create a wifi to lan bridge, probably using a separate PC, that would be great. Sorry, I've very rusty with all this and have been having to rely on finger memory for some of the VMS commands it's been that long! Regards, Mark. On Mon, 7 Nov 2022 at 14:25, Paul Koning <paulkoning@comcast.net<mailto:paulkoning@comcast.net>> wrote: So I'm puzzled. Why would IS-IS not work? If multicast semantics are implemented correctly (i.e., the multicast messages are delivered to all stations other than the sender), it should all just work. Multicast is no different from broadcast, and of course broadcast works. Is this just a case of some badly designed access points that don't understand how LANs work? FWIW, I have once or twice turned on PyDECnet on a Wifi link. Of course that doesn't work because of the HIORD stuff, but the multicast definitely do get delivered, I get adjacency up and all that. paul _______________________________________________ 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> -- M0NOM/P<https://www.qrz.com/db/M0NOM/P> ADIF Processor<https://bit.ly/adifproc>