hosted by langelaar.net  /   Robust Packet Stuffjnos 2.0contact

Updated 11Jan2021 - got confirmation from a user, the WinRPR interface is working just as good as their old TNC setups.

Updated 30Dec2020 - HUGE progress, had a couple of connected sessions with KO0OOO this morning on 30 meters, dial 10.146.60 mhz, usb, around 1300 UTC using 20 watts into a south facing sloper 1/2 wave dipole cut for 30 meters - Winnipeg to Las Vegas ! The connection was solid, and it worked flawlessly. I've once again updated the winrpr.c source file in the rsync area and my github repository - hopefully this is it for a while ...

... will get a screen shot in here some time soon ...

I discovered WinRPR early November. Thanks to Jan (PA3GJX) for bringing it to my attention. I was so excited about this, I actually wrote a new KISS over TCP/IP interface in a few hours, basically a stripped down version of my AGWPE driver from early 2012. Below is a screen shot of WinRPR in action the morning of November 14, 2020, my radio on 10.147.30 USB, with a 1/2 wave dipole (sloper) favouring the south / south east, but signals from the east and west are obviously coming in as well. Like any software modem out there nowadays, this is pretty cool, but even cooler is the fact that it is now another AX.25 interface (port) on my JNOS 2.0 system. The ultimate goal is to use this new RPR interface for message forwarding, but for now I am simply gating packets to the APRS Internet System using NOSaprs (which is part of the JNOS 2.0 software) - see below.

autoexec.nos

attach winrpr rp0 10.8.10.6 8001
#trace rp0 0x211 rp0.log 1000

 note : 10.8.10.6 is the ip address of my windows box running WinRPR

aprs log aprs/master.log
aprs interface rp0
# make sure to use YOUR callsign here !
aprs logon call VE4KLM
#
# Tell APRS internet system I only want stuff within 300
# kilometers (or miles, I don't remember) of my location.
# Winnipeg is at Lat 49d54m, Long -97d7m
#
aprs logon filter r/50/-97/300
#
aprs hsize 20
#
aprs bc stat "JNOS 2.0 Internet Gateway RPR 10.147.30 Mhz"
# make sure to use YOUR coordinates here !
aprs bc pos "4953.22NI09718.35W&"
aprs bc timer 60
#
aprs server add rotate.aprs2.net 14580
#
aprs listen on
#

JNOS log

22:30:34  - using new [tun5] device
22:30:34  - JNOS 2.0m.5D (Linux) was started
22:30:34  - tun_rx - listening for packets
22:30:34  - winrpr listener [10.8.10.6:8001]
22:30:34  10.8.10.6:8001 (1024) - winrpr [10.8.10.6] - connected

sample from trace file

Wed Nov 11 10:21:16 2020 - rp0 recv:
AX25: W4TTU->APOT30 UI pid=Text
0000  82 a0 9e a8 66 60 e0 ae 68 a8 a8 aa 40 e1 03 f0  . .(f``.h((*@a.p
0010  21 33 39 30 32 2e 36 33 4e 2f 30 37 37 32 32 2e  !3902.63N/07722.
0020  34 37 57 26 53 75 67 61 72 6c 61 6e 64 20 52 75  47W&Sugarland Ru
0030  6e 2c 20 56 69 72 67 69 6e 69 61 c0              n, Virginia@

November 12, 2020

Just after 6:20 pm (Winnipeg Time) - my 'first' Igate of a Robust Packet APRS signal.

  Seen on http://www.findu.com/cgi-bin/raw.cgi?call=WA7GMX-10

  WA7GMX-10>APWW11,WIDE1-1,qAR,VE4KLM:@002232h4726.25N\12235.26W&(FORCE)RP Igate in test. Olalla, Wa?

  jnos> aprs status
  Ver: NOSaprs 2.0h, Uptime: 0:04:36:04, Call: VE4KLM, Interface: rp0

  Server connection:
       Server            Port  Connected   Pkts In   Bytes     Pkts Out  Bytes
  * rotate.aprs2.net     14580 0:04:36:05  2485      219402    3         203

  APRS traffic heard:
  Callsign      DTI     Since     Pkts  Other Info (I=Interface, P=Path)
  wa7gmx-10      @    0:00:00:04  1     P wide1-1

* last updated Wednesday midday, December 30, 2020 ...