Setting up a JNOS Packet Server

Once again I'm working on a JNOS packet server.   Yes - it's a BBS but it's so much more.   I'll keep notes in this living blog page to save all those little things that I have to learn and relearn when doing this.

Keep an eye on this - it's a work in progress.   Much can be done to make this easier to set up.  Hmmm - is it time for a jnosconfig.py script?   I'm using .py scripts like that for everything else.

* make sure the linux box has the required software development tools
  * sudo apt-get install devel-tools  ncurses5
 * go to maik/JNOS2 site and use git to fetch the current source
 * edit the config file as needed.  I changed:   xxxxx
  * recompile

* Create the files JNOS needs.  I'm still working on the scheme of putting all the configuration files in $JNOS/etc
* Create etc/Domain.txt
* etc/hosts

* AX1 is the only current TNC port

Hook up the TNC and Radio.   New, to me, IC229 from the Country Store at SeaPac 2012.  Today I interfaced it to the KAM TNC via the MFJ Mic/Packet switch box.
* JNOS: param 255 - takes the KAM out of KISS mode
* KAM:  interface kiss : reset - puts the KAM back into KISS mode
* JNOS:  tip ax1 - gives a simple terminal interface to the TNC.  Great for debugging and putting it into kiss mode.
* Simple beacon commands:
  * ax25 bctext "It's good to be back on the air with JNOS"
  * ax25 bcinterval 1800   # one beacon every 30 minutes
  * ax25 route add ID ax1 K7IK  # for the ID packets from the beacon to use the K7IK digipeater

To Do.
Make JNOS put the TNC into Kiss mode itself...
Make JNOS beacon with APRS style beacons.
Verify that the BBS allow logins and guest logins
Set the IP address on the AX1 port to a valid number in the 145.63 LAN
Get AXIP working to the BPQ32 BBS - that will allow BPQ to use the 145.63 port while JNOS can then access all the other ports on the PBQ32 switch.