June 13, 2017
For those trying to compile JNOS 2.0k.1 on debian-stretch-DI-rc4-i386
replace existing tun.c with this one (kludge fix for now), then 'make'
June 10, 2017
Switched off my sole radio (VHF) port late Saturday night, sad but true ...
coax, antenna, radio, and psu all need to be replaced, and ZERO users for many years now
April 7, 2017
Well, it was bound to happen - lost internet to the house during the last week of March, just not able to align the bridge radio to the AP anymore (7 miles away). It could be interference, or fresnel zone incursions, who knows. It's really too bad, there were many benefits to having this link. It's been operating for 12+ years, but the signal levels just degraded to the point where I finally just got tired of climbing up my 42 ft tower 12 times in less then 2 days. This also took down the DNS for my domain name for a few days, not a big deal, it's all working again.
So for now - the only solution was to get a DSL connection while looking into other options. This effectively kills my AMPRnet connectivity until I find the time to properly configure a working dynamic DNS solution (actually have a working hostname already). At issue is a DSL router with limited routing capabilities. One possible solution is to DMZ to another linux router with better capabilities. I may not bother, outgoing connectivity is just as well good enough.
This has little impact on my JNOS development, it will continue as time permits.
February 10, 2017
Version 2.0k.1 is now available via RSYNC
and here is how I generate those 'pretty' MRTG / RRDTOOL graphs of my JNOS interface traffic ...
July 29, 2016
July 26, 2016
It is time to change 2.0k.rc to just plain 2.0k - now the latest official release. It has been at least 3 weeks, with lots of testing from various people, and I have received nothing but good reports about it.
PLEASE read the release history for important info not documented elsewhere (yet) ...
July 3, 2016
A few changes, most notable being we should now be B1F capable both ways.
June 26, 2016
I am both pleased and terrified to give you a new (linux) version 2.0k.rc - a release candidate. The idea is to let it run for a while, let people try it out, see what kind of reports come in, and if all goes well, it will become just plain 2.0k. This release has been difficult to work on, not just the code, but other aspects (human elements) of the project. There is some finality in it from my perspective, deciding to make changes and not look back on them. For once, I actually feel this is a definitive release.
March 10, 2016
December 8, 2015
June 29, 2015
June 6, 2015
April 14, 2015
For the past 10.5 years I have been running an IBM PC Server 315 - the only OS ever installed on it was Slackware 9.1.0, which came out in September 2003 - with various hardware TNCs to do my packet. This past weekend I moved up in the world and am now running Scientific Linux 7.1 on an older Dell Optiplex 330. The TNC is no more, it's pure soundcard packet now, using Thomas Sailers soundmodem, with a homebrew interface direct to a reconditioned Icom IC28H. This stuff is rock solid. My old TNCs were nothing like this, but in all fairness I'm sure the capacitors were failing, the filters were out of alignment, and so on. I wish I had done this years ago ...
March 17, 2015
In early February, I put together an experimental 'network based JNOS compile and install' utility. One command you run on your linux PC to check for necessary programs and tools, then downloads the latest source, compiles it, then starts a basic JNOS installer program. Maybe just a novelty ? See the home page for all the details ...
The linux version of JNOS is now at 2.0j.7r - new features and bug fixes over the past few months - from 7, then 7p, then 7q.
November 13, 2014
I'm curious where JNOS source is being downloaded to, so I generated a couple of world wide maps (using my own bash scripts, some cut and awk commands, the API from freegeoip.net, and easymapmaker.com) to show where people have been downloading the JNOS 2.0 source code to. Click here for a map showing rsync downloads, and here for a map showing tar.gz downloads. Both maps represent the last 3+ years of activity up to 'now'.
November 2, 2014
July 22, 2014
Version 2.0j.6r, and back on GitHub again, click here for the repository.
June 18, 2014
The linux version of JNOS is now at 2.0j.5 - check release history for details. I have cleaned up the linux download section, no more patch files, just a choice between using rsync or a complete tar file. There are no installer binaries at this time, so you'll have to compile your own if you want to use one.
April 15, 2014
I am trying to focus more on the windows version of JNOS 2.0, and in the interest of keeping up with modern times, I have moved the JNOS WIN32 development to Windows 7 Pro and Visual Studio C++ 2012 Express. For now I am sticking with the Winpcap libraries for network connectivity (my attempt at using raw Winsock calls is failing me miserably).
Linux will always be the main development version, so no worries - nobody is giving up on the linux version anytime soon, but you can only do so much with it, and it may be time to get this working on an O/S that seems to have the biggest 'market share' of potential users if I may word it that way.
One needs the odd challenge from time to time, and so it's not everyday I get to program in the windows environment - actually quite a refreshing change.
Click here if you are interested in this project, and please keep in mind, it is still quite experimental at this stage.
New JNOS (WIN32) installer (now at setupv3.exe). I also confirm AGW Packet Engine, Multipsk, and WINMOR are all working fine. I am able to FBB forward to other systems over ax25, and B2F forward to a RMS system using WINMOR over HF. Cleaned up WIN32 page, much better documentation on how to set stuff up. Sorry, documentation is still minimal, but I'm sure you can figure it out.
What's going on with the linux version ? I want to release a few more 2.0j 'fixes' in the next month or so, the linux downloads section is way out of date - I really want to revamp it, working on a new online installer concept and such, and I am looking at JNOS 2.0k for down the road; a project to rename structures and functions within JNOS that unfortunately share the same names as their O/S counterparts; a project to try and create a common code base for the windows, linux, maybe mac and dos versions, the one big advantage being - less code to maintain.
March 25, 2014
- My first ever WINMOR exchange between JNOS (WIN32) and a real HF station N9LOH-5, a WinLink RMS Trimode system, this very evening on 30 meters. A very good start to getting WINMOR support working properly. I'm very pleased, the WINMOR modem performed perfectly !
- I am experimenting with a network based (linux) installer, which downloads source from my system, then builds a JNOS binary on the remote system it is intended to run on. Click here for a slackware variant (I think it will work on debian systems), or here for an rhel variant. Both installers are 64 bit static binaries, if they don't work, let me know please. This is the first version, a prototype - default config.h, no customization (yet).
March 23, 2014
Found some free time to integrate the WINMOR soundcard modem into JNOS (WIN32). I just need a real station to test with now, and I have to build a VOX circuit to PTT my ICOM rig. The WINMOR software does not include serial or parallel PTT features (which is not the end of the world), and it forces me to keep up on the electronics front anyways ...
March 18, 2014
Updated JNOS (WIN32) installer (setupv2.exe). I made a mistake - the autoexec.nos was not being generated correctly.
March 9, 2014
March 2, 2014
Milestone perhaps - a 'real' windows installer for JNOS (WIN32). The installer is based on the Inno Setup software !
No more zip files, no more first time manual editing of configuration files - just run setup, and start playing ...
By late evening, I have completed live tests on a real radio channel. I confirm the setup where JNOS (WIN32) and Multipsk are both running together on the same Windows 7 Pro SP 1 box - I am able to connect (ax25) from the mailbox prompt in JNOS, to a nearby neighbour of mine VE4BBS running F6FBB via a BPQ node. The connections are working very well, and it's consistent. Please check the WIN32 section for new notes on using Multipsk with JNOS (WIN32). Only the Multipsk (ax25) interface is available, the TNC interface is not stable (yet).
February 24, 2014
Now putting more focus on the windows environment ...
September 14, 2013
The RSYNC (linux) version is now at 2.0j.4 - check release history for details (B1F support) ...
August 6, 2013
The RSYNC (linux) version is now at 2.0j.3 - check release history for details ...
July 16, 2013
I am working on ensuring JNOS <-> Winlink (CMS Telnet) operability. Telpac is obsolete, and no work has been done on telnet forwards to Winlink since those days. Other than a few small items, I simply need to get another (linux) update released - to consolidate changes and remain organized - it's been a while since the last one ...
Jun 17 / Jun 4 / May 20 / Apr 9, 2013
A series of updates to the JNOS WIN32 executable - check the WIN32 downloads section. I have added a serial port interface for any TNC in KISS mode, plus more console commands, including the valuable 'source' command. FBB (compressed) forwarding seems to work, as does AT (timed commands). The domain (DNS) and APRS modules are now available (both have not been tested yet). And finally, you can now attach axip and axudp ports.
March 16, 2013
I've been playing around with a new serial port interface for the WIN32 version of JNOS 2.0 - What you see below is a brief session (last night) with another station nearby, using my PK-232MBX (in kiss mode) on 145.01 Mhz at 1200 baud. This is just to show some progress, the initial code is working quite well, just have to test it a bit more. I hope to have another executable out shortly ...
March 8, 2013
Another JNOS WIN32 executable is available, with the following additions :
. hitting enter by itself on the console now behaves properly and returns another prompt
. more console commands - bulletin, connect, close, convers, finger, help, icmp, reset, and session
. dynamic gateway routes
. ipip (44 net) encapsulation
. ttylink client and server
. finger client
. hop check client (might not work properly)
. mailbox forwarding with RLINE support
. FBB forwarding (includes compressed forwarding)
. no TNC (serial) drivers yet, hope to get moving on that shortly!
Check the WIN32 downloads section to get this latest executables ...
February 27, 2013
WIN32 version of JNOS now runs on Windows XP and Windows 7, with latest WinPcap 4.1.2
February 13, 2013
After letting it sit for 5 years, the WIN32 version of JNOS is an active project again. The amount of progress made since the last week of January has amazed me. Porting this to windows has been surprisingly easy. As of today, the following features are available, and seem to be working on my test setup :
. responds to pings, you can telnet into it
. you can send and receive messages with other local users
. smtp and pop3 servers
. dumb console sessions, console telnet and BBS commands
. basic ax25 stack so you can connect to other stations
. ax25 interfaces to multipsk and agwpe tcp/ip servers
. local convers from mailbox (BBS) prompt
. you can now do outgoing pings from console and mailbox sessions (feb 15)
. my test setup includes the use of Mozilla Thunderbird as a mail client to JNOS
. Thunderbird, Multipsk, AGW Packet Engine, and JNOS all run on the same XP box !
I need people to test this, please click here to get software and instructions ...
January 25, 2013
Yes, I am still alive, but most of my time has gone to my kids, it's just that stage in life. Both of them are on provincial sports teams, and have been for a while. Water polo for one, speed skating for the other, plus high school sports and so on. I have decided to continue work on the WIN32 version of JNOS. It needs to evolve into something more practical and functional, and not just be left on the shelf as a mere concept project.
September 24, 2012
Downloaded the new install medium 2012-09-07 from archlinux.org, installing 3.5.4-1-ARCH onto a VM running inside Oracle's latest Virtual Box 4.2.0 r80737, running on my Slackware 126.96.36.199 host machine, to see if JNOS 2.0 still compiles and runs on a latest linux distro - it seems to be okay.
April 29, 2012
April 26, 2012
A serious bug exists in the new white page feature, and can be fixed by either downloading a patch or using the RSYNC client to update your source. Make sure you read the patch instructions, even if you use the RSYNC client to update your source. In particular, note the change in the directory where the white page database files are stored - the files are now kept in the '/jnos/spool/wp' directory.
Brand new White Page Documentation (quite detailed) is now available and up to date.
March 20, 2012
February 27, 2012
Confirmed that Thomas Sailer's soundmodem still works with JNOS - It works very well - as a matter of fact I used two JNOS (linux) systems talking to each other, one was interfaced to AGW PE running on a Microsoft Vista PC, the other using the latest soundmodem-0.16 driver. Radio channels were simulated using good old fashioned desktop speakers and microphones. I compiled soundmodem from source, available below :
Basic documentation has been updated and moved to here - look under software modems ...
February 24, 2012
December 17, 2011
A couple of new features to note as I work towards another official release. Added a new SMTP gateway mode that allows you to configure JNOS to send all email direct to a gateway FIRST instead of it trying the actual email destinations. One can even configure exceptions to the rule. Also added improved support for the use of UNIX PTY98 (/dev/ptmx, /dev/pts/N) devices. Please read the release history for complete details. Also, important updates have been made to the INP code.
September 24, 2011
July 22, 2011
No time to work on JNOS since my last post. I hope everyone is having a great summer !
I've added a site search feature on the Home page, so now you don't have to go through every single page on this website to look for information on a particular item or topic - should turn out to be a real time saver.
The 'github.com' repository has been deleted - it was too old - a new one is in the works ...
April 28, 2011
- Forgot to mention significant improvements to the dyndns host feature available on axip/axudp interfaces. These improvements were actually done back in early February. The issues from February 9 are now resolved, and I have updated the release history - please give it a read. The latest changes are only available through rsync, as I never got to updating the downloads page. Lastly, I spent a month working on my JNOS 2.0 global mail system (J2GMS) project, alot of design challenges got in the way, to be continued end of summer.
March 25, 2011
- No time whatsoever to work on JNOS since my last post - life is just too busy ...
February 9, 2011
- Even though B2F between two JNOS systems is now working, there are still issues regarding messages (ie, info@ww) not being parsed through the rewrite file properly, and also not getting written to proper areas.
February 3, 2011
- New JNOS SNMP server + MRTG graphs - click here for details, under 'SNMP Server' section
January 23, 2011
Download this patch file, which deals with the following two (2) important issues :
- This is related to the news item of January 20 just below. Any forwarding partners connecting to you, and showing a SID of B1F, are now immediately disconnected before any damage can be done. The JNOS log will tell you how to implement the workaround (as explained in the news item already).
- B2F forwarding between two JNOS 2.0i systems was not working - messages were always rejected. This is fixed, the FA hack seen in the log is gone, and the FC proposal is now properly dealt with. It is cool to watch two JNOS systems B2F forwarding with each other.
Warning - the patch file is ONLY applicable to the latest 2.0i official release !
January 20, 2011
Somewhat of a surprise - an issue with B1F capable systems such as FBB 7.00i - and how to deal with it
November 25, 2010
- JNOS 2.0i is now the latest official release (for linux only). The latest source has been frozen while I try to update the webpage and the documentation (which has fallen behind, no surprises there). Always check the release history for changes from previous versions. Click here to find out how to download.
November 5, 2010
October 27, 2010
Next version of JNOS (for linux only) should be out soon, just cleaning it up a bit more ...
Click here to download a headless (no curses, no console, just a daemon) version to try out.
Use your existing config.h if you like, but you must add all the 'HEADLESS' directives from config.h.default (in the proper spots) before compiling.
August 16, 2010
August 8, 2010
I believe I have fixed the 25 day negative timer issue that has plagued linux JNOS users since day one.
This fix is only available through my rsync server at this time. Use the command below :
rsync -a www.langelaar.net::jnos2 <empty directory for the source>
Put in your own JNOS 2.0h config.h, then do a complete recompile (make clean, clean).
For the technical details, check the 'README.25DayNegTimerFix.07Aug2010' file.
July 11, 2010
Posted an update on 'JNOS and WinLink Interoperability' to the NOS-BBS mailing list ...
you can click here to read the article directly.
June 7, 2010
May 17, 2010
You can now download the latest JNOS (linux) source using an RSYNC client
rsync -a www.langelaar.net::jnos2 <path>
where <path> is an empty directory on your machine where you want the source placed
WINMOR Sound Card TNC support + B2F forwarding with RMS Express (P2P)
* incoming calls only, no 'mbox kick' quite yet - use rsync to get latest code.
documentation is in the works, for now look at rsync MOTD for info ...
March 9, 2010
December 6, 2009
- JNOS 2.0h is now the latest official release (for linux only) - 64 bit compatible !!!
* check the linux Downloads section for brand new installers, source code, and instructions.
If you want to run JNOS 2.0 on newer x86_64 hardware, like a Dell Optiplex 330, or an IBM x3650, and/or if you want to run it on the more recent linux distributions like Arch, Fedora 11, even Scientific Linux 5.3, then JNOS 2.0h is what you should be using. If you are still using older hardware and/or earlier linux distributions like Redhat 9 and Slackware 9.1, no problem - JNOS 2.0h will still work out just fine.
JNOS 2.0g or earlier will not work properly with more recent versions of linux ...
Please read the release history - at least the WARNING concerning indexing of the mail / spool files !
October 22, 2009
JNOS 2.0g critical fix - fixes random crashes and a race condition - click here for patch.
* extract to your jnos source directory, enter command 'make patch' to recompile jnos.
Start of October, 2009
Began work to make JNOS 2.0 compatible with 64 bit environments. Several beta versions
were released along the way to middle of November, including a couple of JNOS installers
for the Arch (Aug 2009) and Fedora 11 linux distributions.
July 25, 2009
May 26, 2009
- JNOS 2.0g is now the latest official release (for linux only) - this is a preliminary release
complete source - instructions - always check release history for changes.
Documentation is being worked on - Please use any past details from previous beta releases
for now - look in the older news archive section (see below). Thank you for your patience.
April 30, 2009
- Getting ready to prepare another official release - essentially JNOS 2.0f4 - with MultiPSK support, the ditching of the GLIBC version of tmpnam, plus a whole bunch of other stuff. I've been working very hard to make JNOS 64 bit compatible, but am not comfortable enough yet to release that part of my efforts. That is just one crossroad that I've hit this past year. Another one was B2F - to add or not to add - that was the question. If the BBS part of JNOS is to integrate with up and coming systems, then I think the answer is clear, although I still have some reservation about having added B2F support - how many JNOS users are actually forwarding with Airmail or Winlink ?
March 4, 2009
- JNOS 2.0 is now able to use MultiPSK (by F6CTE) as a digital modem.
* it does this by connecting to it over tcp/ip - click here for details ...
December 11, 2008
- JNOS 2.0f4 - new beta release (linux only) - click here for details.
* everything that has changed since the last official release of Dec 2007, is now documented.
* use this rudimentary patch to compile '64 bit' - not all 64 bit issues are resolved.
November 25, 2008
- A new BAYCOM driver (direct attach) for JNOS running on top of linux.
* click here for details - no more need to use 'pseudo-tty' and 'net2kiss' software.
September 15, 2008
- A first release of the PK232 hostmode driver is finally ready !
* click here for complete details and instructions.
July 17, 2008
- I'm still alive, and apologize to anyone out there that had expectations
of the pk232 hostmode driver. Sorry, but my kids, summer, and other matters
have sucked up any free time over the last few months. Essentially the rest
of this month, and alot of August are written off, due to holidays, camping,
family obligations, and the list goes on.
Regarding the pk232, it has been a challenge to get it working. At times I have
been completely stuck on specific problems. For instance, hostmode was working
fine, but the PK232 seemed to be *inserting* extra characters in the stream. I
finally got frustrated enough to hook up the PK232 to an AirMail client, and
(with the help of some serial port sniffer software) watch it initialize the
TNC. This was of great help, and I was able to solve several problems right
from the start. But now I am out of time again. Have a good summer !
May 24, 2008
- Another snap shot of my development system - full support for B2F and Airmail telnet module. Tested with the KAM hfdd interface AND with the 'telnet' or 'internet access' module from within the Airmail client. This is beta software - use at your own risk - software patch - details / how to compile
April 10, 2008
- Snap shot of my development system - support incoming B2F & Airmail telnet module. Tested with the KAM hfdd interface AND with the 'telnet' or 'internet access' module from within the Airmail client. I have B2F forwarded stuff FROM the Airmail client TO my JNOS system - including multiple attachements. Note the emphasis of the word TO - I have yet to implement B2F for outgoing forwards (ie, if there is mail waiting for the Airmail client, you will get protocol errors). Please read the 'details / how to compile' below for complete information.
software patch - details / how to compile
February 12, 2008
- Finally - the JNOS 2.0 user manual, click here for details.
January 31, 2008
January 26, 2008
- A third update to the JNOS installer (for linux) - LOCAL mail delivery now works out of the box.
January 25, 2008
January 22, 2008
December 21, 2007
- JNOS 2.0f is now the latest official release, available for Linux only
complete source - instructions - always check release history for changes.
I need to freeze JNOS at this official release for a while, so that I can focus on updating the documentation.
November 14, 2007
November 6, 2007
- The last few months I've been working on a WIN32 version of JNOS - a DEMO is now available !!!
August 8, 2007
- Just got back from our annual holiday. This year it was two weeks in the Maritimes, followed by a long weekend camping trip to Rushing River just east of Kenora, Ontario. It was great - I did not miss JNOS one bit (happens every summer). I spent last night taking down my HF antennas from the tower. I won't be running the Pactor Gateway anymore, since I no longer have an HF radio to dedicate to the task. Nobody ever used it anyways in almost the whole year it was running, so I don't think it will be missed by anyone (except for me) ...
June 26, 2007
- Created a LIVE page to illustrate WEB based access to my particular JNOS system.
- Linux only - A beta version of JNOS 2.0f is now available. Click here to download. To compile, use 'make clean', then 'make' - of course check your config.h settings (or use your own) before compiling. Read the Release History to see what's been done. JNOS 2.0f is basically JNOS 2.0e, the JNOS kernel patch, revamped KAM and PTC code, and a few other things (including a bug fix in which FBB compressed forward is forced off due to that telpac option I added a while ago). Otherwise, the only people that might be interested in this are those that want to run JNOS on the latest linux distributions, or those that want to play with Pactor using a Kantronics KAM (or similar), or SCS PTC hf modem.
- Brand new HFDD documentation for the Beta release, and YES - I have added *.cfg files for the HF modems ...
June 6, 2007
- James Dugal (N5KNX) passed away a few days ago. Jim was the last maintainer of the JNOS software, his last release being JNOS 1.11f - after which I took over under the new JNOS 2.0 banner. According to a local newspaper, James Patrick Dugal, 56, passed away at his residence. Click here for information on Funeral arrangements and obituary.
April 22, 2007
- Starting to try and clean up the Documents sections. Stuff is getting a bit dated. Always an ongoing thing ...
April 5, 2007
- Due to some demand, and the fact that ubuntu is supposedly the most popular desktop linux out there, I felt I should make sure I can compile and run JNOS on such a system. It's terribly easy to do. Click here for complete details.
March 20, 2007
- The newly revamped Kantronics KAM hostmode driver is READY to play with !!! Three things to do :
1) Download source code to PATCH your existing 2.0e source distribution.
2) Download the KAM config file to put in your /jnos runtime area.
3) Download the README and read it thoroughly (please).
March 14, 2007
- The Kantronics KAM hostmode driver (revamped prototype) is almost ready !!!
November 28, 2006
- Linux only - A JNOS kernel patch is now available in the downloads section
of this page. After running the patch for over 26 days, it seems to work fine.
I wrote the patch to deal with the newer GLIBC - the setjmp / longjmp stuff is
broke, and can no longer be reliably used. This could be considered historic,
since JNOS has used the setjmp / longjmp functions from day one ! By applying
this patch, JNOS will abandon that approach, and use the context functions
instead to manage it's process space. Please report any problems. Thank you.
September 24, 2006
- I am making progress with the Pactor server side of JNOS 2.0e - to the point
where I have decided to run a fulltime Pactor mailbox / gateway on the 30 meter
band. Feel free to connect and leave me a message. For more information on my
system, and how to use it, please click here. If you run into problems, please let me know.
September 14, 2006
- Yes, I'm still alive. I figure I better post something to keep this up to date. Summer was great this year!
My family and I spent 3 and a half weeks in the USA on holidays, putting over 10,000 km on our car - Mount Rushmore, Pikes Peak, Grand Canyon South Rim, San Diego, Anaheim, San Francisco, Oregon Coast, San Juan Islands, Bellingham, Salmon Arm, Calgary, just to mention a few places. I even had breakfast with Brian Kantor in San Diego one Sunday morning. After holidays, there was a couple of weekends of camping, the kids were in summer camp for a couple of weeks, renovating my basement, building new cabinets, getting the garage fixed, and lots more to keep us all busy. I just have not had the time - or interest - to work on JNOS this past summer.
So ! What's next ? I'm not sure right now. I got CYGWIN and WIN32 on my mind lately, not so sure about DJGPP. I also want to get the server side of the HF pactor completed and properly working - it never did. I also need to fix a few bugs discovered over the summer, and I believe that I finally have a compilable and working JNOS for Fedora Core 5 distributions - requiring small, yet fundamental changes to the NOS kernel. More later ...
June 29, 2006
- I've been playing with something I call Amateur IP (AIP). This is RAW internet protocol on RF (with an imbedded callsign to make it legal). There is no use of AX25 in this, so make sure you do NOT run it on an AX25 frequency. Check the downloads section (under linux) for a software patch which you can throw on top of your version 2.0e source code, then help me test and benchmark it. This is
purely experimental and my implementation of raw IP over RF. I'm just curious
how good (or bad) it works. Make sure you read the README.AIP document !
May 27, 2006
- A few pre-compiled (linux) binaries of JNOS 2.0e are now available - check downloads section ...
May 10, 2006
- JNOS 2.0e for MAC OS X is ready - check downloads section ...
April 23, 2006
- JNOS 2.0e is now the latest official release, available for Linux only
complete source - instructions - always check release history for changes.
Versions for OSX and DOS will come at a later date. Thanks for your patience.
March 11, 2006
- I think I have JNOS doing successful telpac forwards now. I was able
to forward a message from JNOS to Steve's (K4CJX) winlink server over a
tcpip telpac connection, then pick off the response he left for me later.
Click here for details, including a required software patch.
- Revamping website, specs moved into documents section.
February 5, 2006
- Update - JNOS on Mac OS X now supports TUN - check the downloads section.
February 3, 2006
November 25, 2005
- Dirty port of JNOS running on MacOS X (Darwin Power PC) - check the downloads section.
* development machine (Power PC) running Darwin (GCC 4 compiler) - courtesy Torsten (DL1THM)
* ideas and code taken from WAMPES - MacOS X version courtesy of Bob (N0QBJ)
October 28, 2005
- Prototype JNOS Installer for DOS, Windows XP/2000/NT4/95/98 - check the Downloads section.
October 21, 2005
- Under Documents section - web link to original JNOS 1.11f distribution site, copy of complete JNOS 1.11f documentation (zipfile), and copy of an older JNOS 1.11 user manual.
October 16, 2005
- JNOS 2.0d is now the latest official release, and available for both Linux and DOS platforms - check the Downloads section, and read the release history please.
For those that don't know, the DOS version should run fine on Windows XP, 2000, or NT4, as well as on Windows 98 and 95, and probably OS/2 as well.
Significant items : INP3, NRR, Kantronics Host Mode, up to GCC 4.0.1, and updated DOS version.
Check the Specs section for information on a new packet driver that just came out, which allows JNOS to have network connectivity between itself and the Windows XP, 2000, or NT4 machine that it is running on. This a big piece of news for those that want to run JNOS (in a DOS terminal) on the more modern Win XP environments.
Fixed up the Downloads section - new JNOS binaries (executables), plus JNOS Installer for Linux.
September 22, 2005
- A very brief update. The KAM stuff is on hold since there is no demand for
it, and I have had a VERY busy summer, holidays with my family, etc. My latest
work involves adding INP3 support to JNOS. Progress is VERY good ! My JNOS 2.0
system will now actually handle any NRR (Netrom Record Route) and L3RTT frames
from remote systems running Xnet, and respond accordingly. My prototype will
even send out a RIF record under certain circumstances. More work is left to
do, but INP3 support is coming along VERY well ... More later !
July 21, 2005
- Prototype JNOS installer (linux) for first time users. No editing of
configuration files required, just run and answer the questions, it generates
the configuration for you - user friendly - great for first time JNOS users.
The Kantronics Host Mode driver is slowing coming along ...
July 6, 2005
- Status report - finally doing some serious work on HF digital support for the Kantronics KAM modems ...
June 30, 2005
- New document - Using JNOS with Thomas Sailer's soundcard modem (linux) driver - sound card packet
June 21, 2005
- Update kit available - JNOS 2.0c5a - see download section of this webpage.
- Started a long overdue 'Release History' in the documents section. Every time you upgrade your JNOS, you should read this, so you know what changed from one release to the next (ie, configurations, command syntax, and other things).
- Great News !!! I can consistently forward with a WinLink 2000 (WL2K 2.1.2) system using JNOS 2.0c5 and my Halcomm DXP38 modem. I have had absolutely no problems picking off bulletins and messages waiting to be downloaded from WL2K, and
I am able to upload small bulletins and mails to WL2K as well, without problem.
Important - SCS PTC users must update to JNOS 2.0c5a to get it working as above. HF support for JNOS 2.0c5 was primarily focused on the DXP38 at the time, since it's the only modem I have to work with. There are some minor issues left - such as the odd flakey connect or disconnect, and the rare crash - but they're liveable.
- Added callsign substitution to the 'ax25 xdigi' command. Check documents section for complete documentation on how to use the 'ax25 xdigi' command, including how to use this new callsign substitution feature. Please note, the NOSaprs built in WIDEn-N digipeater (aprs flags +digi) will override any 'ax25 xdigi' rules having a digipeater callsign like WIDEn-N. In other words, if you want to use WIDEn-N as a cross port digipeater, you will have to disable the NOSaprs built in WIDEn-N digipeater (aprs flags -digi). I'm looking into this. Ideas are welcome.
- The 14501 status page (NOSaprs) is slowly evolving. I have added a couple of more forms to it, showing stations heard, users and past users logged in or connected. The form is interactive, you can request stations heard for the different interfaces. The rest of the page has a slightly new look as well, and is a work in progress.
June 1, 2005
- JNOS 2.0c5 is now the latest official release - check the downloads section of this website.
* incremental update is also available for users of JNOS 2.0b and later ...
NEW crossport digipeating rules that allow sysop to create customized digipeating between two ax25 interfaces on any digi call. The APRS people will like this for gating HF APRS frames to their local VHF frequencies. Check the documents section for information on how it works and how to configure it.
For NOSaprs, some file and directory locations have changed. Make SURE you read
the documents section on the APRSdir root directory, and how to properly migrate your files to the new format.
IF you are using NOSaprs in JNOS 2.0c4 and are NOT using the 'aprs logon filter' feature, then you MUST update to this release, which fixes a string termination problem in the connect string used to logon to the APRS internet system. If you
can't update, then at least set the 'aprs logon filter' to *something valid* to
correct the problem.
Other than that, I fixed a few bugs, cleaned up some code, did some more playing
around with the HF digital support using my DXP38 - that's all I have to work
with now. Bad luck or what, I blew my comm ports on my development PC two days
ago, so I am not able to play with my DXP38 again till I get that fixed - good grief !
May 26, 2005
- Another milestone (finally) - stayed up late evening, May 25th, and was able to send and receive private mail and bulletins several times over, with
WU3V's WinLink 2000 (W2LK) system, and consistently for a change !!!
In the end, this comes down to the manner in which changeovers are
implemented by the various software solutions out there. After all the testing
and analysis of logs I have done, I have to conclude there is no standard way
to do this, which does not make it any easier to integrate these programs with
each other on the HF bands.
May 24, 2005
- Added SMTP configuration notes to documents section. I am working on a new
browser based MAP Display for NOSaprs (requires Image Magick libs). I also need
to fix a few bugs reported to me by several users over the past few months, and
I am also working on new 'user configurable cross port digipeating' features.
Some users have asked about gating APRS traffic from HF ports to VHF ports -
the new feature will accomodate that. Lastly, I am still struggling to get the
forwarding to work properly between JNOS and AirMail / WinLink 2000 systems...
April 29, 2005
Status report - Sorry, but I have had NO TIME to work on any of this for
the last month or more. I have too many things going on with my family, the
community centers, and other events that I volunteer my time with. In order
to keep from burning out, I have had to set some priorities. JNOS has been
placed lower on the list for now.
The loaner SCS PTC II Pro has been returned to Jim (WU3V). A big thanks to him
for making it available for the few months I had it. This does not mean that I
can no longer do any development, it just means that I will have to depend on
the JNOS 2.0 users out there to test it for me. I don't think this will be a
huge problem, since in reality no one has been knocking down my door to use
JNOS 2.0 with Pactor - alot of effort, hardly a customer in sight.
Oh well - live and learn - it was still a good experience and lots of fun ...
March 29, 2005
- The DOS source is now at release JNOS 2.0c4 - check the downloads section of this website.
March 18, 2005
- Experimental JNOS 2.0c4 - check download section of this website.
Click here for my autoexec.nos configuration file.
* don't just plop the config file in and run it ! It's heavily documented within, and meant as an example only.
The HF server seems alot more stable now. The documents section has been updated to include a new user manual for the latest HF Digital Device support, as well
as upgrade notes for the latest NOSaprs enhancement - support for the javaAPRS server filter port.
Next thing to fix - forwarding between JNOS and AirMail - which is still not in the greatest shape. I want to get that fixed and working asap, so that I can move on to other things.
March 10, 2005
- The HF server is done and I'm ready for another release, BUT the darn thing is crashing too much, so the release will have to wait until I figure out why. It's been a bit frustrating, as well I haven't had alot of time to work on this lately (family, volunteer commitments, work, etc). Thank you all for your patience.
February 24, 2005
- A milestone of sorts : The server side code is working on a one-shot basis,
meaning after a user ends their session I have to restart it. All that is left
for me to do is get rid of the one-shot part, and make it fully automatic.
- If anyone is wondering - NOSaprs is alive ! I've just been too busy with the
JNOS 2.0 project, that's all. I've bumped up NOSaprs to version 2.0 to stay in
step with the new JNOS version, and I have added a 'logon filter' feature to
the NOSaprs module, so that when you connect to a javaAPRS (Internet System)
server, you can now request filters (ie, only send traffic for stations within
a certain distance, or that have a certain callsign, etc).
The JavaAPRS servers
have a custom port 14580 that you can connect to and use a filter to customize
your data feed. This is great for those wanting to connect to the APRS internet
system, but not get the firehose of data sent back at you. Click here for more information on JavaAPRS and the filter feature.
- Important : Make sure you add 'LISTEN 0' to the list of commands you use, when initializing your SCS PTC for the first time ! If you don't, and your SCS has been sitting on a busy frequency, you will see *old* data appear when you try and start any new session, resulting in a big mess, and possible lockups.
February 16, 2005
- Status on JNOS 2.0c4 - I can now use my DXP in Clover or in P-Mode (Pactor 1), and the server side for the HF digital modes is almost ready - I am just working out a few remaining issues.
This means that JNOS to JNOS forwards over HF are around the corner. Once this code is released, I want to be able to start 'test forwards' with other JNOS systems running this latest HFDD code. Any volunteers ?
A note to the FBB people - JNOS to FBB forwarding works very well right now. I've had virtually NO problems at all doing forwarding with WU3V's FBB system in Montana. The JNOS to AirMail forwarding on the other hand, is not perfect and needs more work.
Oh yeh ! I forgot, I got the KAM hostmode spec, so I'm fooling around with KAM support now :-)
February 9, 2005
- Experimental JNOS 2.0c3 - check download section of this website.
I'm very pleased with the stability of the HFDD code in this release. Also, the DXP code has been updated, so both the SCS and DXP modems are supported the same again.
warning: Disable ax25 and mailfor beacons on your HF interfaces ! The beacons will mess up the serial port comms to your SCS or DXP modems. For example, use ax25 bcport ptcpro off and mbox mport ptcpro off immediately
after you attach the device. IF you don't, you will get very frustrated (like I did) ...
I need to thank the following stations (so far) for providing me with valuable test time ...
* WU3V (Jim), VO1XC (Laurence), N0GQ (Jeff), VE4GLS (Gord), W4DAC (Dwight), VE6HM (Mitch), VE7DHM (Paul).
February 8, 2005
- Just for the fun of it, I had a keyboard to keyboard chat with VE4GLS last nite on 80 meters. I was running the SCS PTC II Pro, he had an MFJ 1278B connected to the AirMail software. I did a user connect to him from the JNOS BBS prompt, and got connected at Pactor, level 1. He would hit CTRL-B to do a changeover on his end, and I would use the ENTER key to do a changeover on my end. Lots of fun !!!
January 30, 2005
- A milestone of sorts : Now able to forward to FBB, AirMail, and WinLink 2000 systems (yes - all 3 of them). Client only at this stage (ie, JNOS must initiate the connect). Server side is in the works, still need to port these latest fixes into the DXP code, and then plan on starting KAM development soon.
- Experimental JNOS 2.0c2 - check download section of this website.
Just for the fun of it, Jim (WU3V) and I did some experimenting this morning
on 40 meters, and managed to get JNOS forwarding with his Winlink 2000 system,
using both our SCS modems, running at level 3 (PT3). I fixed a few issues that
surfaced during these tests, and then ran a few more tests this evening on 40
meters again, and was able to forward both a private message and a bulletin to
Jim's system. The forwards ran perfectly.
NOTE : I think it would be irresponsible of me to leave out the following point
regarding the use of JNOS to forward to Winlink 2000 stations ! The only reason
I bring this up is because my understanding of the Winlink 2000 system is that
it is for emergency traffic, and for those who need to deliver messages of some
importance from remote areas of the world back to their families, etc.
Based on this understanding, I can't see the point in *local* JNOS stations
needing to forward their traffic to any of the Winlink 2000 stations. I tried
it just to see if it worked, and to make sure it was possible, just for those
cases where one might actually find a JNOS system on a boat, yacht, or in some
remote area of the world (one never knows I guess).
I say this only to cover myself and the rest of the JNOS community. I certainly do not want to encourage any non-essential movement of traffic between JNOS systems and the Winlink 2000 system - I think that's fair enough.
January 27, 2005
Released a software patch, after running a series of tests with Laurie (VO1XC),
this morning on 20 meters (conditions were simply awesome). Got JNOS to AirMail
forwarding alot better then it was in the first experimental release from two days ago. Bob (VE3TOK) created an updated 2.0c1 linux binary (check the download
area) that includes this latest fix. This affects the DXP as well, but I don't have a fix for it yet, hopefully in a few days.
January 25, 2005
- Experimental JNOS 2.0c1 - HF forwarding with FBB and Airmail systems ...
January 21, 2005
- Status Report - HF forwarding to FBB and AirMail systems using the SCS PTC modem is working reasonably well (in my test environment anyways), and I have also been able to do some forwarding with the HalComm DXP38 running in Clover mode
(it's quite something to watch). Forwarding with AirMail was easier than I thought, and aside from the annoying lines beginning with the ';' character, it is quite compatible with the JNOS FBB forwarding.
The biggest challenges have been in tweaking the disconnect and timeout scenarios. They work, but not perfectly. I hope to have a beta out soon for everyone to play with, stay tuned ...
January 4, 2005
- Release JNOS 2.0b - GOTO(less), TUN fixed, PTC 'proof of concept'
- I am kind of dreading the release of this version, but it has to be done ! I
have removed all occurances of the GOTO compiler tags, replacing them instead
with function equivalents, and creative while loops with conditional variables.
You *should* now be able to compile this on the newer gcc compilers, like the
one distributed with Fedora Core 3.
note: there is a *slight* chance that some stuff may have been broken
during the changes. This was labour intensive, and took alot of time, so please
report any problems asap !
- I fixed a serious memory leak in the TUN interface. Bob (ve3tok) noticed
this when his Linux started shutting down services because of no memory.
- This is the cool one - I have a working client interface that will let
you connect to other Pactor stations using the SCS PTC II Pro. You can also
run a BBS mode, which will allow people to connect to your JNOS system. Please
check out the Documents section for complete
details on how to use JNOS with your SCS, and what you can do so far.
note: This is very experimental, and is more a 'proof of concept' release
than anything else. It was labour intensive, and I have spent alot of time on it
during the month of December (probably more time than I should have, considering
it was the christmas holidays, and perhaps I should have spent more time with wifey in the evenings, she's so patient with me).
Thanks to Laurie (VO1XC) and Jim (WU3V) for the large amount of test time they provided. I also got a couple of exchanges done with W4DAC on 80 meters. Click here for a few screen grabs of successfull connects.
note: The way the interface is defined has changed, as is the way you make connections. These changes affect the JNOS client interface for both the DXP38 and the SCS PTC devices, so make sure you read the notes in the Documents section for the new command syntax, etc.
December 2, 2004
- I have added 2.2 kernel support to the TUN driver, and Bob (VE3TOK) reports that it is working, although later in the month he reported a memory leak, which has been resolved in version 2.0b.
- The loaner PTC II Pro and Kam have arrived (many thanks to Jim, WU3V) !!! Now I can start work on HF digital interfaces for those modems. I think this will be very exciting, and I can hardly wait to get this stuff working.
November 28, 2004
- Release JNOS 2.0a - it's time to pay attention to release identification.
- The TUN driver is ready for use. See documents section for details.
* requires kernel headers to compile. Only works for 2.4 kernels at this time !!!
- The feature which lets you specify a dynamic gateway in the 'route add ...' command is now working properly (there was no major design flaw as I originally
thought - the problem was similar to the mistake I had made for the dyndns code
in the axudp and axip interfaces). All of the dyndns stuff now seems to be working properly.
- Check out the new Documents section. User manuals, configuration notes, etc - added to as time permits
- The DOS source is finally up to date. It too is at release JNOS 2.0a.
- BIG NEWS : Expecting arrival of a loaner PTCPro and KAM for development purposes !
November 23, 2004
- Just an update (no software) - My test system is now running the new TUN driver that I started working on a week ago (November 18). No more SLIP interface,
no more SLATTACH - There are a few issues I need to work on, but for the most part it seems to be running quite well. I want to stress test this for several more days before I update the source code on this website. Thank's for your patience.
November 20, 2004
- Compiled and linked on DOS using Borland C++ Version 3.1 (1992) compiler.
November 14, 2004
- I would consider this a CRITICAL update (see part about HIGH cpu usage).
- First a warning ! Do NOT use domain names for the gateway parameter in the
'route add' command - just use IP numbers like you normally would. The feature
letting you specify a dynamic gateway in the 'route add ...' command is majorly
flawed ! I am in the process of redesigning and rewriting it.
- The HF digital (Clover) client has been tweaked abit, and now works as good
as it can with all the testing I've done so far. The next step is to move on to
other modes and hardware.
- I've removed the '-O2' compile option from makefile.std and makefile.aprs,
since for debugging purposes there should be no optimization in place.
- Fixed a problem in ax25.c that was causing JNOS to suddenly go into HIGH
cpu usage. Anyone using AXUDP or AXIP interfaces with a domain name for the
remote host was affected by this. It was a design flaw on my part, and should
now work properly.
- Fixed several instances of calls to getpeername(), where the peernamelen
parameter was not being properly initialized before calling the function ! The
most noticeable problem associated with this was in the use of the STATUS line
on the JNOS console. For example JNOS would consistently crash if you tried
connecting to a station that was not there, then going back to the console,
hitting enter, then boom ! I'm sure there were many other scenarios similar
to this one. Anyways, a very irritating bug finally fixed !
This should significantly stabilize JNOS where the status line is in use, as
well as stabilize the 44825 (aprs client) server and the 45845 (aprs browser
messaging) server. People have in the past reported problems in these areas,
crashing for *no* apparent reason.
November 2, 2004
- Fixed a mistake in 'main.c' which prevented the new '-a' option from being
recognized. This is for configuring the maximum number of (axudp + axip)
interfaces. Also fixed a mistake plus a few compiler warnings in 'smtpserv.c'.
- Added support for IP routes having dynamic (dyndns type) gateways. If you
specify a domain name instead of ip address for the gateway parameter when doing the 'route add ...' command, then JNOS will periodically re-resolve that domain name and change the ip address of the gateway if it has changed.
See the new '#define DYNGWROUTES' in config.h for compiler control.
- The maximum number of IP routes that can have dynamic gateways is not hardcoded. It can be dynamically
assigned by passing the '-R' (capital) option to the JNOS executable at runtime - for example :
jnos -R 12 -a 5 -d /jnos
October 30, 2004
- Finally, a working JNOS client for an HF digital interface. The prototype
allows me to connect to a remote station using a HalComm DXP38 modem (clover)
from the JNOS bbs prompt - I've done keyboard-keyboard with a few stations
already while doing development on this. I'm very happy with the results.
Added the following (or similar) to your 'autoexec.nos' file :
attach asy ttyS2 - ax25 pactor 4096 256 9600 f
ifconfig pactor description "pactor port on hf"
Make sure your DXP38 is connected to /dev/ttyS2 (in this example), power
it on and off to set the default setting of 9600 baud on the serial port,
then from the BBS prompt (not the console, it's not the same command), type
something like 'tip pactor ve7dhm' to connect. It's not perfect, needs more
work, but it does work, and this is just the start !
The ultimate goal is to do FBB forwarding between JNOS and FBB running an
HF digital mode like Pactor or something along that line.
October 26, 2004
- Compiled and linked on DOS using Borland C++ Version 3.0 (1991) compiler.
October 25, 2004
- Fixed a cosmetic in the display when issuing the 'route' command.
- The maximum number of (AXIP + AXUDP) interfaces is no longer hardcoded. It can now be dynamically
assigned by passing the '-a' option to the JNOS executable at runtime - for example :
jnos -a 3 -d /jnos
- Added the hooks for NOSaprs stuff, and put in the latest development version of NOSaprs (not the official one).
- There are now 2 makefiles in the archive - 'makefile.std' and 'makefile.aprs'. There is no 'makefile' for starters.
Copy (or link) either of the above makefiles to 'makefile' first, then you're ready to compile.
October 19, 2004
- Fixed a cut and paste mistake in the REMOTE server code. I have removed the 'route protocol udp' command - I never should have added it in the first place.
Instead, pass the 'udp' option at the end of the 'route add' command, like K2MF
did from the beginning. See the updated notes from October 17 for proper syntax. Also the 'route' command will now tell you if a particular encap route is using UDP (meaning IP over UDP).
* WARNING - the 'route protocol udp' command has been removed already !!!
October 17, 2004
- JNOS 2.0 is based on JNOS 1.11f - first thing I did was take the 1.11f
source distribution and check it into an RCS repository. Sorry, I'm not going
to setup a CVS right now due to limited bandwidth and my slow server box.
- As I add past and future enhancements, I am also fixing stuff that the
compiler warns me about, such as missing initializers, uninitialized variables,
comparisons between unsigned and signed, fixing bugs, and so on. For example,
the deprecated 'sys_errlist' I have replaced with 'strerror()' instead. I
still need to work on the 'tmpnam()' linker warning (not really serious).
- Merged the AXUDP code into the AXIP code, since they are almost the same,
no point duplicating code if it's not required. To attach an AXUDP interface,
use something like the following :
attach axudp bcm 256 192.168.1.130 BCM 95 95
The 95 and 95 above are source and destination UDP ports. These are optional, and if not specified, the AXUDP defaults to using UDP port 93 for source and destination. Note, the source and destination ports can be different.
* WARNING - this 'attach axudp' has one less argument than the original AXUDP update kit. I have removed the '-' argument that would have been present between the BCM and 95 in the above example. Hope that makes sense.
- Support for DYNDNS type remote hosts for BOTH AXUDP and AXIP wormholes.
If you specify a domain name instead of ip address for remote host, JNOS will periodically re-resolve the
domain name to see if ip address has changed. For example :
attach axudp ax0 256 pretend.dyndns.org AX0
- IPUDP tunneling (K2MF) - now you can do 44 encap traffic through your
cheap firewall routers.
The standard way to add a 44 encap route is something like the following :
route add 44.0/8 encap a.b.c.d
By default the above route uses IPIP - IP encapsulated in IP.
If you want to use the new IPUDP - IP encapsulated in UDP, then all you need
to do is specify an extra 'udp' argument at the end of the route command :
route add 44.D.E.F/32 encap 64.x.y.z udp
- REMOTE client/server updated with a 'udpadd' (routing using IPUDP), in
case one is not able to use the existing 'add' (routing using IPIP). Those
with dialup, or DSL/Cable with dynamic IP addresses will find this useful
in conjunction with the IPUDP tunneling. You'll need a static host (that
supports IPUDP) and is willing to host you.
* last updated on Tuesday, June 13, 2017