[Simh] ts10 and mse (my new emulator) (WAS: RE: Klh10 vs Simh)

[Mark Pizzolato]

I’m not familiar with what device connectivity TS10 and MSE have implemented.

Is it simulating Ethernet devices?

Point to Point network devices?

Are these tun/tap connections merely used to connect simulators to each other
in the same system or are they also expected to be part of how connectivity I
achieved between simulators and the host system and/or the outside world?

I ask these questions since they’ve all been solved on Windows and Unix hosts
in the simh codebase.  The simh Ethernet functionality provides Ethernet frame
delivery to/from the local LAN and/or to/from the host system directly.  Ethernet
frames can also be delivered to remote networks via UDP and thus direct
participations in HECnet is possible.  More than likely, the simh sim_ether code
wouldn’t fit directly into TS10 or MSE, but the details of how this problem has
already been solved would certainly be a useful in getting to where you’re going.

Step back from the focus on tun/tap and/or Winsock and think packet delivery
and reception.  Tun/tap is one solution to that problem on some platforms.
Simh’s Ethernet layer can talk via tun/tap on Unix hosts.  It can talk directly
to a LAN interface on Unix and Windows hosts.

10 Years ago, on Windows, we thought we needed some sort of package like
OpenVPN in combination with pcap to facilitate bridging.  As it turned out
(only on Windows), we didn’t need that at all once it was realized that we
could talk back and forth with the host system (using pcap) if we padded
pcap received packets to the minimum ethernet frame size.  We received
short packets since pcap captured them before they’d made it to the LAN
driver which would normally have padded them to the minimal frame size.

If you explore these ideas, feel free to ask questions here or directly to me.


-          Mark

From: Simh [mailto:simh-bounces at trailing-edge.com] On Behalf Of Jason Stevens
Sent: Monday, February 20, 2017 10:55 AM
To: simh at trailing-edge.com; Tim Stark <fsword7 at verizon.net>
Subject: Re: [Simh] ts10 and mse (my new emulator) (WAS: RE: Klh10 vs Simh)

DECnet for Windows? Yeah, if you have patchworks installed it is another socket transport. I ported a telnet client and SBBS 3.0 to DECnet. Not terribly useful today, but you can take windsock programs and alter them to run over DECnet with tweaking.... Not that there's an audience for that kind of thing
On February 21, 2017 12:37:52 AM GMT+08:00, Tim Stark <fsword7 at verizon.net<mailto:fsword7 at verizon.net>> wrote:
Ok, thanks for some information. I will look into that and am now figuring how to implement TAP/TUN access on my MSE emulator for Windows.
Will DECnet work on TAP/TUN for Windows?


I am using MinGW64/MSYS and LLVM environments and Eclipse/CDT IDE editor. I already implemented WinSock2 API access into it.


I learned that WinSock2 API provides DECnet access.  Does anyone have any experience with DECnet for Windows?


I plan to adding SDL2 API access for graphics console terminal (VAX emulation) later.




From: Jason Stevens [mailto:jsteve at superglobalmegacorp.com]
Sent: Sunday, February 19, 2017 11:36 PM
To: simh at trailing-edge.com<mailto:simh at trailing-edge.com>; Tim Stark <fsword7 at verizon.net<mailto:fsword7 at verizon.net>>
Subject: Re: [Simh] ts10 and mse (my new emulator) (WAS: RE: Klh10 vs Simh)


Part of OpenVPN has tun/tap for Windows. And windows does software bridges which you can bridge the tap to an Ethernet, or even among other taps.. there is code in Qemu that'll talk to the tap driver.

As a footnote here is how it's done

https://virtuallyfun.superglobalmegacorp.com/2015/01/22/getting-qemus-netware-3-12-onto-the-lan-with-tuntap/

I hate to be "that guy" and ask what license is ts10 under, as you could possibly just copy the code just in.. or at least see how it's done.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20170220/c9f65a1a/attachment-0001.html>