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

In which case, via /etc/network/interfaces, auto tap1 tap2 eth0 bridge1 iface tap1 inet manual pre-up ip tuntap add tap1 mode tap user simh iface tap2 inet manual pre-up ip tuntap add tap2 mode tap user simh iface eth0 inet manual iface bridge1 inet manual bridge_ports tap1 tap2 eth0 bridge_fd 0 I'm assuming you're keeping wlan0 unbridged and dhcp'd Connect tap1 to pydecnet, tap2 to a simh instance and eth0 for anything externally decnet. The 'user simh' addition to the tap device creation means that a non-root user, in this case 'simh' has more or less full control over its side of the network device.# Pydecnet.conf: circuit tap-0 Ethernet tap1 --mode tap --random-address SIMH.ini: set xu enable,mac=something-or-other att xu tap:tap2 K -----Original Message----- From: Robert Armstrong [mailto:bob@jfcl.com] Sent: 07 November 2022 19:46 To: 'The Hobbyist DECnet mailing list' <hecnet(a)lists.dfupdate.se> Subject: [HECnet] Re: Ad-hoc connection to hecnet? It should be mentioned that a pyDECnet talking to eth0 won't be able to talk to a simh instance talking to eth0 on the same machine. It's a limitation of the way pcap works - you can't see messages sent to yourself. The solution is to set up a TAP device and connect simh and pyDECnet to that, in addition to eth0. Bob _______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se