* Disclaimer - I know the rules, and I'm sure you know them too ... (no https, ssl, or any form of encryption)
a video will be uploaded in the near future, just too busy right now ...
(note the screen shot showing peak 7050 bps - at the end of this page)
In this demonstration, the ve4klm JNOS router listens for client TCP/IP connects on port 14504. When a client connects, the router will try to establish a VARA connection (via the Window 10 PC) to the ve4pkt system. The ve4pkt JNOS router itself is configured to TCP/IP connect to a particular host on port 14504 upon any VARA connection made to it (via the Windows 7 PC). Once all 3 connections are in place, you essentially have a water hose of sorts, over which you can then pass raw TCP/IP data direct from the client on the VE4KLM side to the host on the VE4PKT side. Note; just the data is passed. The underlying TCP/IP protocol is handled on both ends by the JNOS routers, acting as proxy servers. Also note the TCP/IP connects are raw socket connects, not telnet sessions, which would corrupt any passed data.
Even though the demo is using the same linux host for both the client end and the remote side, the important thing to note is that the client and/or host on each side can be anywhere on their respective LAN, WAN, VPN, or Cloud, as long as they have IP routing available to their respective JNOS routers. The plan for later is to support not just VARA, but other software modems and TNCs (basically any JNOS port), think 'forward.bbs' for instance, but that's down the road ...
The demo is simple. Start the netcat 'server' first (another xterm session), then run the netcat 'client' second (xterm session). When the demo is done you can ctrl-C the client side, then diff the files to make sure they match. IF you want to repeat the demo, you should kill the server side and run it again. The way I have setup the netcat server arguments, it's a one time use. I have run the demo several times already, the best I can give you at this moment is a screen shot (below)
You should know; you can easily write a TCP/IP proxy in linux or windows. You don't have to use JNOS to do any of this stuff, it's just that JNOS has been my platform for amateur radio research for 20 years, and I am most productive on it - just saying ...
There is also the KLMproxy project from 20 years ago, which I plan to update so it can use the VARA software. The KLMproxy software would run on the same PC as the VARA software, negating the need to setup a separate JNOS router on a linux host for that side of the connection. Not sure when I will get to it, but it's on my todo list.
Lastly, this whole idea is not just bound to the VARA modem. One should be able to use any software modem or TNC that is available on their JNOS system to do this - just think forward.bbs for a second (for those who know what I'm referring to) ...
* last updated on Thursday, December 1, 2022 ...