[nos-bbs] JNOS linux fed by BPQ32 on Windows

Bill V WA7NWP wa7nwp at gmail.com
Wed Jun 3 16:35:47 EDT 2009

Well it happened again..   I started out with plans to get a Windows
implementation of JNOS on the air and after a few weeks of development
the I've come to the same conclusion.   It works fine but it's just so
limited compared to the Linux version that it's not reasonable to stay
the course.

Windows JNOS running on an XP box with BPQ32 works fine.  The
connection between JNOS and BPQ32 is pretty much painless once the
learning curve is past the normal two or three little tricks.   I was
sharing the TNC/serial port and only time was keeping me from working
with other applications like Airmail and Outpost on the same setup.

Then I tried to test message forwarding with a WL2K RMS/AccessPoint.
It replied, as expected, use B2F.  So, to make a short story even
shorter, a little digging led me to the details that I use running
JNOS 2.0 C4, 2.0F4 was the existing version with B2F and the latest
Windows version is 2.0F - apparently with no B2F.   (Yes - the latest
version is actually 2.0G - Thank you Maiko:
http://www.langelaar.net/projects/jnos2/documents/changes.txt  )

After a few moments of contemplating just moving the Linux 2.0G source
to the windows box and digging in to make it work, I came to my senses
and went to bed.  Moving to a pure Linux setup just makes so much more
sense then fighting the memory limitations.

Ok - now there's one last issue and the reason for my posting.  I'd
like the Linux JNOS 2.0G to have the same transparent interface to the
BPQ32 data on the windows box as I do now.   I know I can do basic
packet connectivity with AXUDP but I'd really like to have the flow of
raw packets seen by the TNC available for monitoring.

So - is there anyway to get the packet data from BPQ32 on a windows
box to JNOS on Linux?   Maybe one of the AGWPE shims?

Thanks - and see you all at Seapac.  :-)

Bill - WA7NWP

More information about the nos-bbs mailing list