HomeThe WIN32 (Native Windows) version of JNOS

Requirements

JNOS 2.0 requires the WinPcap software, BUT only if you want to have IP connectivity to it, otherwise it is NOT mandatory (anymore).

Either way, you can find the WinPcap software here ...

Updates to the WinPcap 4.1.2 version of JNOS

If you have already installed the WinPcap 4.1.2 version of JNOS (using the j2dist5.zip below), then you can click here (update10) for an updated executable. Just rename it to jnos2win32.exe after you download it. It was last updated Jun 17, 2013. The changes are documented further below in the Release History section.

How to Install JNOS on Windows XP or Windows 7 with WinPcap 4.1.2

Click here to download a zip file of the latest release. Extract the contents to the C:\JNOS directory.

You MUST edit the 4 files, 'autoexec.nos', 'domain.txt', 'ftpusers', and 'popusers', and REPLACE my callsign and password (maiko) with your own. Also make sure you have correct IP addresses in place for your ax25 tcp/ip servers. If you choose to use a drive other than C: drive, make sure you specify it properly in the 'ftpusers' file. If you are running Windows 7, change the fifth column in the 'attach pcap' autoexec.nos entry, from a '2' to a '1'.

Switch between console sessions using CTRL A, B, and D (sorry, just 3 for now), also note CTRL C kills the program, that is why it is not used to switch sessions.

The windows 7 version might not be as stable as the XP version, it's not clear yet.

How to Install JNOS on Windows XP with WinPcap 4.0.1

Click here to download a zip file of the latest release. Extract the contents to the C:\JNOS directory.

Same instructions as above.

Checksum Offload and Windows Firewall

JNOS will discard incoming IP packets with bad or zero checksum values. The O/S has a feature called 'Checksum Offload', which means it can tell the NIC (network card) to generate the checksum instead of the O/S. I found with my 2010 and 2012 compiles, the incoming checksum was always missing. Not sure if you will run into this with my 2005 executables, but you should know anyways. You may want to disable the 'Checksum Offload' feature of your operating system. Read this forum article for more info. If JNOS is not responding to incoming packets, this is one thing to look at.

If you have the Windows firewall enabled, you may have to play around with it as well ...


Release History


Jun 17, 2013

Another executable (update10) is available, with the following additions :

    . aprs modules
    . added 'start aprs ' to console commands
    . added axip and axudp interfaces (ports)
    . more console commands - aprs, udp, source, attach axip|axudp
Please note - I have not tested the APRS and domain (DNS) modules at all ...

Jun 4, 2013

Another executable (update9) is available, with the following additions :

    . fbb forwarding seems to be working (tested without a rewrite file)
    . added 'start forward' to console commands
    . more console commands - at, comm, domain, tcp, ttylink, write, writeall
The serial port code still has some issues (ongoing) ...

May 20, 2013

Another executable (update8) is available. Serial port code is much 'better', and it will now take the baud rate (any valid rate) as passed in the 'attach' command. I had forgot to mention, the April 9 version hardcoded the baud rate to 1200 (ignoring the value specified in the 'attach' command). I'm still a 'bit' frustrated with the serial port code, most of the time it works wonderfully, every so often it just gives up without warning, which is difficult to track down - also delays my desire to get moving on FBB forwarding tests.

Another item - WinPcap installation is no longer required IF you don't need IP connectivity to windows !

April 9, 2013

A new executable (update7) is available - added a serial port interface for any TNC already in KISS mode.

Add the following to autoexec.nos :

    attach asy COM1 - ax25 axr 4096 256 1200
    #
    ifconfig axr description "145.01 Mhz, 1200 baud"
    #
    param axr 2 256
    param axr 3 1
    param axr 5 1
    param axr 1 20
    #

It seems to work 'okay' from the JNOS console, but shows instability if used from the BBS prompt, or with other JNOS activity on the go. I actually had this working on March 16, but it has been difficult to debug.

March 8, 2013

Another executable is now 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!
Expect bugs, for example USERLOG is not 100 percent, anyways something more to play with ...

February 27, 2013

Microsoft VS C++ 2010 Express and 2012 are presently challenges (heap corruption and crashing) to my project, so for now I am sticking with 2005. The executables seem to run decently on both Windows XP and Windows 7 platforms, and they can use the latest WinPcap 4.1.2, which is good enough for now.

February 22, 2013

I am able to compile (and run) a Windows 7 version using Microsoft VS C++ 2012 Express and the WinPcap 4.1.2 library, but stability is an issue. I may have to go back to Microsoft VS C++ 2005 Express in the meantime.

February 15, 2013

Outgoing 'ping' commands are now working from both console and mailbox sessions.

February 13, 2013

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

    . 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 !

January 25, 2013

After letting it sit for 5 years, the WIN32 version of JNOS is an active project again.

November 14, 2007

Here's an updated demo version. If you have already gone through the first one, then all you have to do is replace your first JNOS demo (j2dist) with this new one. This one has a full mailbox now, and runs the smtp server (no rewrite yet). After you run JNOS, you can telnet into it like before, but now you can send/read/list/kill *local* messages to other people that login to your system (you need to 'smtp kick' to deliver the messages though). This release has 4 files - the original 3 (see below), plus domain.txt (needed for smtp server lookup). The demo uses my callsign (ve4klm) as hostname. You can edit the autoexec and domain.txt files to replace it with your own callsign. This version also automatically creates essential directories like spool, and logs. It also logs to the logs directory now - ie: logs/13Nov07.

November 6, 2007

I am very happy to report to you all - a demo version of JNOS for Windows. This is not a DOS executable. This is a true WIN32 executable, compiled using Visual C++ 2005 Express Edition. The only system requirement is that you have to install the WinPcap (Windows Packet Capture Library). JNOS for Windows uses WinPcap to interface to the network. At some point, I want to be able to include the WinPcap drivers and libraries with the JNOS installation files, so that users don't have to install the WinPcap separately, but not right now.

I think it's important to note that most of the source code for JNOS for Windows is from the original DOS and Linux source. In particular, I am using the original JNOS ip stack. There is no Windows IP stuff in here. It's all original NOS. The only Windows code needed so far is with respect to timers, context switching, and of course the WinPcap interface.

Install WinPcap first. Go to the WinPcap Site, click on the 'Get WinPcap' off the menu on the left side of their webpage, then go to the section entitled 'WinPcap 4.0.1 download', then run the 'Installer for Windows'.

Install the JNOS demo. Download this file, extract it to any directory. There are 3 files - jnos2win32.exe, autoexec.nos, and ftpusers. You must run JNOS as an Administrator or Power User, since the packet capture libraries will need permission to grab any network interfaces you want to work with.

Run JNOS for Windows by opening the folder you extracted the JNOS demo to. Click on the jnos2win32 executable. Once JNOS is running, bring up another Windows command session, then 'telnet 192.168.2.2', you should see a JNOS login prompt. Login with your callsign, use your name as the password. The ftpusers file that comes with the demo is just universal access. While you are telneted in, try some of the limited commands on the main JNOS console - use the ? command to list them all.

The only possible (minor) catch is that when JNOS starts you will see a list of network interfaces displayed on the console. The autoexec.nos assumes that the second entry displayed will be your ethernet card. If NOT, then you will have to edit the sample autoexec.nos, and change the 5th argument of the following line to indicate which interface JNOS (WinPcap) should be attaching to - note the number 2 that follows the mtu value of 1500 :

    attach pcap en0 1500 2 192.168.2.2

That's all. I know it's not much, BUT actually - it is ! As far as I know, this is the first ever release of a WIN32 (Windows) version of NOS. There will be stability issues of course for the first little while. Please do not report bugs, this is a concept release only, and it will most certainly be full of bugs. I will be releasing more demo versions as time permits, and of course more functionality will follow. This work was done over the past few months off and on. It actually was not as big an undertaking as I originally thought.

* last updated on Monday, Jun 17, 2013