• If you have a problem & I ask you for more data go here

• Verify that the AX.25 config & TNC to radio & TNC to computer connections are working properly.
• Receive tests

• mheard is found in the ax25-tools package or tar ball
• Display information about most recently heard AX.25 calls

mheard
man mheard

• listen is found in the ax25-apps package or tar ball
• Monitor network AX.25 traffic heard by the system.

listen -a
man listen

• Compose an e-mail with your e-mail client & send e-mail
  • set up an e-mail client
• A file should appear in the paclink-unix outbox waiting for a pending transport operation via wl2ktelnet, wl2kax25 or wl2kserial

ls -salt /usr/local/var/wl2k/outbox

• Verify that the permissions in your wl2k directory are OK ie. user username and group mail
• For example for user gunn and group mail:

     Directory of /usr/local/var/wl2k
  drwxrwsr-x    3 gunn     mail         4096 Nov  2  2013 ./
  drwxr-sr-x    4 root     staff        4096 Nov  2  2013 ../
  drwxrwsr-x    2 gunn     mail         4096 Dec  7  2013 outbox/
  -rw-------    1 gunn     mail        12288 Jan  5 14:55 mid.db

• verify that user is in group mail by executing:

groups

• or

id

• wl2ktelnet will test your mail & paclink-unix config and does not touch your TNC or radio.
  • You must have an internet connection to make this work as it uses the telnet internet protocol
• Compose a message addressed to your callsign, verify that a file appears in the outbox and send with telnet.

wl2ktelnet
man wl2ktelnet

• Run the wl2ktelnet program again, you should receive the message you just composed to yourself.
  • Receiving mail addressed to yourself only works if the mail.wl2k program uses the '-m' argument.

• Repeat the above test but use the wl2kax25 program instead of wl2ktelnet.
  • This uses your radio and TNC rather than the internet.
• locate a nearby RMS gateway by using mheard, listen or the Winlink Universal RMS Map
• <someRMSGateway> will be a valid ham callsign with usually but not always having a sid of 10
  • ie. n7nix-10
• <someDigitpeater> will be any alphanumberic restricted to 8 characters in length
  • ie. digi
  • digipeater callsigns are sometimes aliases & will not necessarily look like valid callsigns.

wl2kax25 -c <someRMSGateway>
# or
wl2kax25 -c <someRMSGateway> <someDigipeater>
man wl2kax25

• Type:

groups

• Note if you ever send mail as root you will screw up the permissions.
  • Check your permissions in your outbox directory like this:

ls -salt /usr/local/var/wl2k/outbox/
total 16
4 drwxrwsr-x 2 gunn mail 4096 Sep 21 16:48 .
4 -rw------- 1 gunn mail  214 Sep 21 16:48 V1IRQZ_N7NIX
4 drwxrwsr-x 3 gunn mail 4096 Sep 21 15:55 ..
4 -rw------- 1 gunn mail  196 Sep 21 15:55 H51W38_N7NIX

ls -salt /usr/local/var/wl2k/
total 20
4 drwxrwsr-x 2 gunn mail   4096 Sep 21 16:48 outbox
4 drwxrwsr-x 3 gunn mail   4096 Sep 21 15:55 .
8 -rw------- 1 gunn mail  12288 Sep 21 15:55 mid.db
4 drwxr-sr-x 4 root staff  4096 Jul  7 12:49 ..

• Note hactar is the local machine & brox is a machine on my local net.
  • The last line is important

# cat transport
#
localhost      :
hactar       local:
hactar.localnet  local:
brox smtp:[brox.localnet]
brox.localnet smtp:[brox.localnet]
#
*         wl2k:localhost

• Example:

wl2k      unix  -       n       n       -       1      pipe
  flags=XFRhu user=gunn argv=/usr/local/libexec/mail.wl2k -m

• In one console window type:

tail -f /var/log/mail.log

• In another console window type:

echo "test mail from command line" | mutt -s "Test12:56" n7nix@winlink.org

• or using the mail program

# from command line or script
echo “This will go into the body of the mail” | mail -s '//WL2K cmd line test' -a "From: yourcallsign@winlink.org" -a "Reply-To: yourcallsign@winlink.org" some_regular_email_address

• Link to set up mutt or mail
• Look for problems in the /var/log/mail.log file
  • Open up another console window and do this:

tail -f /var/log/mail.log