Remote Packet Station

I’m busy building a remote packet station.

  1. Airgrid AG-HP-5G23 For remote control the Pi 5Ghz Point to Point
  2. USB DC-DC step down module 4,5V-40V to 5 Volt 2A USB – Power for the Pi
  3. W1401 12V Digital Thermostat Temperature Controller Switch Module NTC Sensor
  4. Power supply Mean Well (150W, 12V,12.5A)
  5. 3x Fan 80x80x25 mm 12 volt
  6. Raspberry Pi 2
  7. 3D Sound card
  8. 2x Ground loop isolater
  9. Trx President Lincoln 2
  10. Antenna  Siro tornado 27 5/8
  11. 10Mtr EcoFlex 15

Connect the Pi to the Trx

Tcp Access Control Jnos

Jnos works with an access control list. Here a small example what you can put in there. There are things double in it, this is just an example what is possible

# ACCESS CONTROL
#===============
#Allow a specific Hostname (eerst ff wachten "now+0001" tot de dns online is)
at now+0001 "tcp access permit packet-radio.net all"
# Localhost (altijd handig)
tcp access permit 127.0.0.1 all
# Ampr.org (Compleet ampr.org netwerk)
tcp access permit 44.0.0.0/8 all
# Nederlands Ampr.org netwerk
tcp access permit 44.137/32 all
# Eigen Ampr.org netwerk
tcp access permit 44.137.31.64/27 all
# Lokaal netwerk
tcp access permit 192.168.1.0/24 all
# Lokaal netwerk met toegewezen poort
tcp access permit 192.168.1.175/24 25 110
# Friendjes :)
tcp access permit 82.176.45.213 all
# blacklist bad logins for 15 minutes (900 seconds)
mbox blacklist 900
# run expiry process every 20 minutes
tcp access expiry 20
# Acces deny (Bad boy)
tcp access deny 81.21.45.213
# Subnet access to ports 1 through 25,
tcp access permit 23.1.46/24 1 25
tcp clean

 

Examples forward JNOS/BPQ/LinFBB

Here below some examples how the configuration of the forward in different systems works.

Thanks in particular to Bob (VE3TOK) and Gus (I0OJJ) for example configs !

Copyright ©  http://www.langelaar.net/jnos2/

Example Configuration for JNOS 2.0k side
   ----------------------------------------

      a) autoexec.nos

         # regular listener (no IAC) for remote JNOS and BPQ systems
         start telnet

         # another listener (IAC) on different port for LINFBB and OBCM systems
         start telnet 6300 iac

         # for winlink secure login, you have to configure your callsign
         mbox winlinkcall ve4klm

      b) spool/forward.bbs

         -------
         ve3tok
         # Here we are talking to a remote LINFBB system
         telnet 44.x.y.z 6300 iac
         +Callsign :
         .ve4klm
         +Password :
         .BLAHBLAHBLAH
         ve3tok
         -------
         va3tok
         # Here we are talking to a remote BPQ system
         telnet 44.x.y.z 8011 cronly
         .ve4klm
         .BLAHBLAHBLAH
         +BPQ
         .BPQBBS
         va3tok
         -------
         wl2k
         # Here we are talking to Winlink CMS server
         telnet winlink.org 8772 cronly
         +Callsign :
         ..VE4KLM
         +Password :
         .BLAHBLAH
         wl2k
         -------
         i0ojj 0023 P
         # Here we are talking to obcm v1.07b12
         # NOTE : OBCM supports FC proposal, so it will use B2F, but wonder if
         # I should force a B1F response so RLINE and Headers work properly ?
         telnet 44.x.y.z 4719 iac
         @10
         +login:
         .ve4klm
         @10
         +password:
         .BLAHBLAH
         @10
         <areas to forward>
         -------
         ir0aab 0023 P
         # Here we are talking to linfbb v7.0.8-beta2
         telnet 44.x.y.z 6300 iac
         @
         +Callsign :
         .ve4klm
         +Password :
         .BLAHBLAH
         @
         <areas to forward>
         -------

      c) setting up MY winlink authentication

         cd /jnos

         mkdir users		* you only need to do this one time

         ./jnospwmgr -a <callsign> -w

         it will ask you to enter the phrase that you would have received
         from your winlink notice (the challenge/response phrase).         

       * for now please read release notes (search December 8) for more info.

   Remote LINFBB host
   ------------------

     For forwarding to VE4KLM I added the following line to 'bbs.sys' :

       < FWD\VE4KLM

     A forward file for that particular bbs is placed in FBB's 'fwd' directory,
     so an example of forward file, 've4klm' (contents might be different for
     other FBB owners.)

       A VE4KLM

         P A
         C C ve4klm ve4klm.ampr.org 6300
         V login$Wpassword$W

       #  Forward file -- To VE4KLM BBS (JNOS)
       #
       #  Personal mail
       #
       B VE4KLM
       F VE4KLM
       #
       # Reverse fowarding to take place
       R
       # Forward rest of North-America to VE4KLM
       H  VE4KLM.#WPG.MB.CAN.NOAM
       H *.NOAM
       #

   Remote BPQ host
   ---------------

     This is needed as telnet connect script for bpq in forwarding with jnos.
     It is entered in the "connect script" box of the forwarding config web
     page of the bpq mail server.

       TIMES 0000-2359
       Idletime 60
       attach 3
       c ve4klm.ampr.org 23 NEEDLF .login pass

     General:

       attach p - p is a port number cfg'd as telnet port in your bpq32.cfg

       c Hostname TCPport [NEEDLF] User Password [Command]

     Here :

       attached 3 - I configured port 3 as telnet port
       NEEDLF     - Causes a Line Feed to be sent after user and password.
       .login     - The period before the login user name will tell jnos to use
                    a transparent TCP session instead of ordinary telnet.

     See: http://www.cantab.net/users/john.wiseman/Documents/TelnetServer.htm

     This example line below is needed in bpq32.cfg so that jnos can login into
     bpq and initiate forwarding as bbs.
 
       USER=ve4klm,password,login,BBS

   Remote OBCM host
   ----------------

     ; From obcm v1.07b12
     ;
     ; INIT IR0RM file (JNOS-2.0k+)
     ;          0                  1                  2
     ;          012345678901234567890123
     IR0RM PPPPPPPPPPPPPPPPPPPPPPPP TELNET:44.x.y.z:6300
      -d -k -l -o -u
     ;

   Remote LINFBB host
   ------------------

     # From linfbb v7.0.8-beta2
     #
     IF H 00-23
      S connected failure busy
      C C IR0RM-1 44.x.y.z 6300
      V i0ojj$Wpassword$W
     ENDIF
     #

 

Direwolf Soundmodem

Direwolf source

Direwolf example config

Arecord -l

#############################################################
#                                                           #
#               Configuration file for Dire Wolf            #
#                                                           #
#                   Linux version                           #
#                                                           #
#############################################################
# card number reported by "arecord -l" command.

ADEVICE  plughw:0,1
ACHANNELS 1

#############################################################
#                                                           #
#               CHANNEL 0 PROPERTIES                        #
#                                                           #
#############################################################

CHANNEL 0

MYCALL PI1LAP-8
MODEM 1200 1200:2200 E+
PTT /dev/ttyUSB0 DTR
TXDELAY 20
TXTAIL 10
KISSPORT 8001
FIX_BITS 1

PBEACON delay=1  every=30 overlay=S symbol="digi" lat=51^33.52N long=003^48.15E power=4 height=15 gain=6 comment="PI1LAP-10 RX\TX iGate Kortgene,ZLD JO11VN" via=WIDE1-1,WIDE2-1 
DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE 
#FILTER 0 1 t/wn 
IGSERVER aprs.pa4tw.nl:14580
IGLOGIN PI1LAP 20391
PBEACON sendto=IG delay=0:30 every=30:00 symbol="igate" overlay=T lat=51^33.52N long=003^48.15E 
#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=T lat=42^37.14N long=071^20.83W 
IGTXVIA 0 WIDE1-1 WIDE2-1
IGFILTER m/250 
FILTER IG 0 t/m

# Finally, we don't want to flood the radio channel.  
# The IGate function will limit the number of packets transmitted 
# during 1 minute and 5 minute intervals.   If a limit would 
# be exceeded, the packet is dropped and message is displayed in red.

IGTXLIMIT 6 10

Nieuwe firmware

Vandaag de pk-88 van Roland PD2RLD voorzien van een frisse eprom.

Dit modem kan nu weer gewoon in kiss gebruikt worden.

Leuke van Roland zijn pk-88 is dat er een dcd printje in zit, iets wat ze standaard niet hebben!

Als bedankje mocht ik de oude eprom houden met wa8ded firmware, deze had ik nog niet voor de pk-88 dus daar was ik weer erg blij mee 🙂

(X)Net IP.NET

A small example of IP.NET from (X) Net

#
# Default route
ipr add default SLIP 192.168.1.201
#
iproute add 192.168.1.200/24 slip 192.168.1.201
#
### Set route naar Bbs en Convers
route local add 4 pi8lap-8 nd lapcon
route local add 3 pi8lap nd lapbbs
#
#### Start services
start tcpd
#### Start telnet server (zie file teluser.net)
start telnetd
#### Start httpd (index.htm)
start httpd
#### Start de ftp server (zie file ftpuser.net)
start ftpd
#### Start statd
start rstatd 192.168.1.112
start statd
start statd 60 		min.sta
start statd 3600 	hour.sta
start statd 86400 	day.sta

(X)Net Crontab

Here a small example of the crontab of (X) Net

# -------    ------------
# Minuten      0-59
# Uren         0-23
# Dagen        1-31 Dagen van de maand
# Maanden      1-12
# Weekdagen    0-6 (Zondag = 0, Maandag = 1, etc...)

# 30 4 1,15 * 5 msg all Goedemiddag allemaal
# Wordt om 4.30 uur op de 1e en de 15e van de maand en op elke vrijdag uitgevoerd.

# Minuten	uren	dagen	maanden	weekdagen	WAT	Text
# Gelukkig nieuwjaar wensen.
   0 		0 	1 	1 	* 		msg all Iedereen een gelukkig Nieuwjaar!
# Ronde van PI4Z begint zo
   55		11	*	*	0		msg all	Ronde van PI4Z begint over 5 minuten.
   55		11	*	*	0		fbeacon pi4z.txt 0 BEACON
   54		11	*	*	0		fbeacon pi4z.txt 1 BEACON
# Backup autoexec/autoboot 1 keer per dag
   0		0	*	*	0,1,2,3,4,5,6	cp autoexec.net /usr/local/xnet/backup/autoexec.res
   0		0	*	*	0,1,2,3,4,5,6	cp autoboot.net /usr/local/xnet/backup/autoboot.res
# Extra Beacon
   0,15,30,45 	* 	* 	* 	* 		fbeacon beacon.txt 0 BEACON
   1,16,31,46	*	*	*	*		fbeacon beacon.txt 1 BEACON
#