[Xastir] xastir message via Internet

[Curt, WE7U]

On Sun, 3 Jul 2011, Eric wrote:

> I've been having problems with Xastir sending messages from the Internet
> servers to the RF network. I have a passcode, and when I check the
> aprs-is servers (I'm using rotate.aprs.net:14580) the server I'm on
> shows my verified status. I have transmitting enabled, I have Igate
> options set to "allow RF-Inet and Inet-RF traffic." Am I missing
> anything?

Perhaps enable sending your position?  Also check:  There are Xastir igate settings in File->Configure->Defaults and in the Properties area for each of your RF interfaces.  This allows you do have a global config, then to restrict it further on a per-interface basis.


> I am able to send messages from my TH-d72 through RF to my xastir
> station. From what I've read all I should need to do is make the path
> from xastir to RF TCPIP* and things should work. When I do this I see
>
> TX -> K0JEG>APX200,TCPIP*::K0JEG-2  :TEST MESSAGE
>
> I have tried other paths such as nothing, which only shows APX200, which
> I'm assuming is the AX25 network stack?

No.  It means Xastir v2.0.0


> I've also tried specifying a
> full path similar to TCPIP*,WIDE2-2,OLYS (nearby digi) and other
> variants without luck.
>
> It is my understanding that Internet gateways should normally pass
> messages from verified users. Could it be as simple as any local gateway
> owner doesn't allow Internet traffic to pass to RF? Is that SOP?

Yes on that last, some igates are set up to go RF->INET only and don't gate in the other direction.  It's impossible to do two-way messaging using those stations, but often there are other igates (perhaps with a longer RF path) that can pick up the slack.

I'm not sure what you're trying to do from the description.  Are you:

*) Using your own Xastir station as the INET->RF gateway?  In this case if you have your setting right, you're in complete control of the igating and which directions the igating is enabled for.

*) Using other INET->RF gateways for your messaging, with your Xastir instance only on INET?  This is where you might have trouble with other igates set to receive only.

*) Using Xastir to talk directly to your D72?  Looks like you've done that.  For your RF path you should use "WIDE2-1" (1 hop) or "WIDE2-2" (2 hops).  From your mobile/portable you should probably use "WIDE1-1,WIDE2-1" (2 hops using mountaintop -or- home fill-in digis for the first hop).

For communicating over the internet with Xastir, path settings are not needed but you do need to be a verified user.  They used to allow communication between unverified INET-only stations but they disabled that feature in the INET system a while back.

Back to paths, for my RF interface (an AX.25 kernel interface) I have:

                Path1:  WIDE2-1
     Igate -> RF Path:  WIDE2-1

-- 
Curt, WE7U.        http://www.eskimo.com/~archer
Additional pages:  http://wetnet.net/~we7u