Kevin,

You need to change 'gunn' which is my user name to your user name
probably pi. ie.

#
[N7KJK VIA udr1]
  NOCALL * * * * * * L
  default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

Also make sure there are NO blank lines in your ax25d.conf file.
Look in /var/log/syslog for any wl2kax25d entries.

/Basil

Kevin K. - N7KJK <kkutzera@...> writes:

> Thanks Basil,
> So I've read the MAN pages for both wl2kax25d and ax25d. Somewhat illuminating..
>
> A friend of mine tried to connect using both N7KJK, and N7KJK-10 (my Winlink Gateway address).
> He tried these both as Packet P2P, and Packet WinLink. He only had one connection using the callsign with SSID. It didn't accept of send email and he had to force the disconnect.
>
> I think I am beginning to understand how to control this. So Here's my new configuration of ax25d.conf.
> My radio is connected to the DIN port farthest away from the GPS sma antenna port. I see traffic (beacons) all day long (mostly with invalid or Unknown APRS Type Indicator.. (no big deal).
>
> My assumption is that if a station is trying to call me with my SSID they are treating my PI as an RMS-Gateway. I send their traffic through to the gateway software.
> If the station is trying to call me without the SSID they are attempting Packet P2P and local email will be forwarded as indicated in the man page.
>
> [N7KJK-10 VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
> #
> [N7KJK VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - gunn /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
>
> The version I was running during the test had N7KJK-10 listening on udr0. I don't have a second radio listening on that port but the hand off to rmsgw was given the wrong port so my station didn't reply properly.
>
> So my friend will test again tomorrow. I'll update this thread success of failure so we have info to share with others.
>
> Next on my punch list is to get this to beacon periodically like other stations do...
> 73
> Kevin / N7KJK

Ok,

Understood.  Not sure why I didn't catch that in the man page.

Thanks

On Thu, Aug 1, 2019 at 9:00 PM Basil Gunn <basil@...> wrote:

Kevin,

You need to change 'gunn' which is my user name to your user name
probably pi. ie.

#
[N7KJK VIA udr1]
  NOCALL * * * * * * L
  default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

Also make sure there are NO blank lines in your ax25d.conf file.
Look in /var/log/syslog for any wl2kax25d entries.

/Basil

Kevin K. - N7KJK <kkutzera@...> writes:

> Thanks Basil,
> So I've read the MAN pages for both wl2kax25d and ax25d. Somewhat illuminating..
>
> A friend of mine tried to connect using both N7KJK, and N7KJK-10 (my Winlink Gateway address).
> He tried these both as Packet P2P, and Packet WinLink. He only had one connection using the callsign with SSID. It didn't accept of send email and he had to force the disconnect.
>
> I think I am beginning to understand how to control this. So Here's my new configuration of ax25d.conf.
> My radio is connected to the DIN port farthest away from the GPS sma antenna port. I see traffic (beacons) all day long (mostly with invalid or Unknown APRS Type Indicator.. (no big deal).
>
> My assumption is that if a station is trying to call me with my SSID they are treating my PI as an RMS-Gateway. I send their traffic through to the gateway software.
> If the station is trying to call me without the SSID they are attempting Packet P2P and local email will be forwarded as indicated in the man page.
>
> [N7KJK-10 VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
> #
> [N7KJK VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - gunn /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
>
> The version I was running during the test had N7KJK-10 listening on udr0. I don't have a second radio listening on that port but the hand off to rmsgw was given the wrong port so my station didn't reply properly.
>
> So my friend will test again tomorrow. I'll update this thread success of failure so we have info to share with others.
>
> Next on my punch list is to get this to beacon periodically like other stations do...
> 73
> Kevin / N7KJK

--

Kevin J. Kutzera CISSP, CISM, CEH

Cell: 206-850-7762

kkutzera@...

https://www.linkedin.com/in/kjkutzera

In your mail apps you address messages using p2p, telnet or ax.25
exactly the same way <some_call_sign>@winlink.org. Do not change this
for p2p.

As I said before once messages are composed and existing in your outbox
directory /usr/local/var/wl2k/outbox, you can send them using p2p
(nearby winlink machine), telnet (CMS) or ax.25 (winlink RMS
Gateway). The messages and how they are addressed are exactly the same
for all the different transports.

To send a message via p2p use wl2kax25 & drop the SSID from the call sign,
that's all there is to it. ie. wl2kax25 -c n7nix

Kevin K. - N7KJK <kkutzera@...> writes:

> OK so the reinstall fixed the PLUWEB.. Thanks..
>
> On the P2P Packet. My friend and I are now reliably handshaking, and
> it appears we're transferring messages. I'm sending to his plain call
> sign (no @domain) and he's sending to my call sign.  He reported the
> following information to me.

You are using an unqualified email address. If you did this using mutt
email client it would automatically append the winlink domain.

> **
> n7kjkpi.localnet says it could not deliver my message, msg "unknown user k7rmz@...
> **
> I am of course N7KJK. Not sure where that email address at the end of his report is coming from .
>
> In RainLoop I can't compose a message to him because it requires @domain in the email address.
> Claws lets me compose an email to the call sign. (all messages show up in the Sent items folder even before I try to send).

All the email apps require an @domain, specifically <some_callsign>@winlink.org

> Somehow while typing this reply, my friend sent me an email directly (no gateway) addressed to N7KJK@.....
> Not sure how that worked...

Did you receive it via internet or radio?

> I think something similar to the issue with my email address instead
> of pi@localhost. My system doesn't know what to do with a message
> addressed to N7KJK (no ssid, no domain, no @)

Correct, the address you use must be a valid email address,
name_or_callsign@<some_actual_domain>

> 73
> Kevin
> N7KJK
>
> I can send whatever log segments might help . I'll just not sure which
> one's you want to see. I'll certainly update this thread if I find
> some interesting information.

Send me the file you are about to send from /usr/local/var/wl2k/outbox.
Looking at that file I can tell you whether it has a chance of being
sent properly.

Exercise for you:
Compose a single message to k7rmz@... and copy it to a temporary directory.

Send it using: wl2ktelnet

Copy message from temporary directory to /usr/local/var/wl2k/outbox
Send it using: wl2kax25 -c k7rmz-10

Copy message from tmp directory to /usr/local/var/wl2k/outbox
Make sure k7kmz is set to receive via p2p.
Send it using wl2kax25 -c k7kmz

Cut & paste the console output from those 3 transactions in a regular
email to me.

/Basil n7nix