I-GATE problem on last version

205 views
Skip to first unread message

IW3IJQ

unread,
May 12, 2013, 12:22:38 PM5/12/13
to aprx-s...@googlegroups.com
I'm running APRX (digi and Tx igate) for a long time.
Since last version I can't relay packets from APRSIS to RF.

This appens:

.. igate from aprsis
interface_receive_3rdparty() aif=0x806c4e0, aif->digicount=1
.. parse_aprs() rc=OK  type=0x8008 srcif=APRSIS tnc2addr='WLNK-1>APRS::IW3IJQ   :rejK'  info_start=':IW3IJQ   :rejK'
## produce 3rd-party frame for transmit:
.. parse_aprs() rc=OK  type=0x08 srcif=APRSIS tnc2addr='IQ3VQ>APRX27,WIDE2-2:}WLNK-1>APRS,TCPIP,IQ3VQ*::IW3IJQ   :rejK'  info_start='}WLNK-1>APRS,TCPIP,IQ3VQ*::IW3IJQ   :rejK'
## process source filter
historydb_insert_heard(APRSIS) v=0xb77423f0
 filter_match_on_callsignset(ref='IQ3VQ', keylen=5, filter='P/WLNK* P/EMAILTV*/IK3SVW*')
 .. reflen=0x84 r2='WLNK'
 .. reflen=0x87 r2='EMAILTV'
 .. reflen=0x86 r2='IK3SVW'
filter says: 0 (indifferent)
No history entry for receiving call: ''  DISCARDING.
historydb_insert_heard(APRSIS) v=0xb77423f0
DISCARDED! (filter_discard=0, discard_this=1)


I have the filters:

P/WLNK*
P/EMAILTV*/IK3SVW*

in aprsis section.

A workarount is adding digi call to P/ but I don't know if is so correct...

.. igate from aprsis
interface_receive_3rdparty() aif=0x806c4e0, aif->digicount=1
.. parse_aprs() rc=OK  type=0x8008 srcif=APRSIS tnc2addr='WLNK-1>APRS::IW3IJQ   :rejM'  info_start=':IW3IJQ   :rejM'
## produce 3rd-party frame for transmit:
.. parse_aprs() rc=OK  type=0x08 srcif=APRSIS tnc2addr='IQ3VQ>APRX27,WIDE2-2:}WLNK-1>APRS,TCPIP,IQ3VQ*::IW3IJQ   :rejM'  info_start='}WLNK-1>APRS,TCPIP,IQ3VQ*::IW3IJQ   :rejM'
## process source filter
historydb_insert_heard(APRSIS) v=0xb77730fc
 filter_match_on_callsignset(ref='IQ3VQ', keylen=5, filter='P/WLNK* P/IQ3VQ P/EMAILTV*/IK3SVW*')
 .. reflen=0x84 r2='WLNK'
 .. reflen=0x05 r2='IQ3VQ'
filter says: 1 (accept)
No history entry for receiving call: ''  DISCARDING.
historydb_insert_heard(APRSIS) v=0xb77730fc
Send to digipeater
digipeater_receive() from APRSIS, is_aprs=1 viscous_delay=3
1368375637 ENTER VISCOUS QUEUE: len=1 pbuf=0xb777b000
1368375639 LEAVE VISCOUS QUEUE: dupe=0xb7784600 pbuf=0xb777c1a8
1368375640 LEAVE VISCOUS QUEUE: dupe=0xb7784800 pbuf=0xb777b000
 out-hdr: 'IQ3VQ>APRS,WIDE2-2:' data='}WLNK-1>APRS,TCPIP,IQ3VQ*::IW3IJQ   :rejM'
interface_transmit_ax25(aif=0x8c803e0[IQ3VQ], .., axlen=64)
kiss_kisswrite(->IQ3VQ, axlen=64) .. put 69 bytes of KISS frame on IO buffer


KJ4AJP

unread,
May 13, 2013, 5:09:51 AM5/13/13
to aprx-s...@googlegroups.com
Similar issue noted in thread I started May 10 under subject "Reverse-Gating", thought it was just me!.  I'm using b/call and o/obj filters without success.
--
Roger  KJ4AJP

*********************

IW3IJQ

unread,
May 14, 2013, 5:14:04 AM5/14/13
to aprx-s...@googlegroups.com
I've not watched into svn commits yet, I think that something changed in filter logic.

Debug messages tell:


 interface_receive_3rdparty() aif=0x806c4e0, aif->digicount=1
.. parse_aprs() rc=OK  type=0x8008 srcif=APRSIS tnc2addr='WLNK-1>APRS::IW3IJQ 
  :rejK'  info_start=':IW3IJQ   :rejK'
## produce 3rd-party frame for transmit:
.. parse_aprs() rc=OK  type=0x08 srcif=APRSIS tnc2addr='IQ3VQ>APRX27,WIDE2-2:}WLNK-1>APRS,TCPIP,IQ3VQ*::IW3IJQ   :rejK'  info_start='}WLNK-1>APRS,TCPIP,IQ3VQ*::IW3IJQ   :rejK'
## process source filter
historydb_insert_heard(APRSIS) v=0xb77423f0
 filter_match_on_callsignset(ref='IQ3VQ', keylen=5, filter='P/WLNK* P/EMAILTV*/IK3SVW*')


So aprx take packet from APRSIS, prepare packet to transmission and apply filter on this.
Source of this is always the igate call.... so all following logig is broken.

Filter have to be applied before producing 3rd-party frame, I think...

IW3IJQ

unread,
May 14, 2013, 5:57:30 AM5/14/13
to aprx-s...@googlegroups.com

There was a lot of changes in interface.c and seems that now aprx make 3d-party frame and after apply filter.

Question for OH2MQK:

Is right this and we have to move filter on another place or there is a issue on source code?

KJ4AJP

unread,
Jun 18, 2013, 9:16:18 AM6/18/13
to aprx-s...@googlegroups.com
Stefano - Did you find a work-around for this? 

--
Roger  KJ4AJP

9W2TPT (MHM)

unread,
Jun 18, 2013, 6:21:56 PM6/18/13
to aprx-s...@googlegroups.com

So I wasn't alone it seems :)  Add the same filter you've in aprsis section into the digipeater section too. This workaround works for me.

--
You received this message because you are subscribed to the Google Groups "Aprx software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

KJ4AJP

unread,
Jun 19, 2013, 11:49:03 AM6/19/13
to aprx-s...@googlegroups.com
But after private emails we discovered you are still running 2.06, where reverse-gating did work for me (I had the filters in <aprsis> and <digipeater/source> in both 2.06 and in 2.07). 

In 2.07 the reverse-gating appears broken.

Has anyone found a work-around for the reverse-gating issue in 2.07?
--
Roger  KJ4AJP

***********************

Mohd Hamid Misnan

unread,
Jun 19, 2013, 10:25:59 PM6/19/13
to aprx-s...@googlegroups.com
Hi Roger,

It seems to work okay with 2.07 too, at least for me. Just upgraded my aprx to the latest 2.07 compiled by oz1ekd for openwrt and tested this morning. fowsr is directly feeding aprs-is server with the WX data and my igate backfeed it to RF.

Here is the log:

2013-06-20 02:15:02.819 APRSIS    R 9M2TPT-13>APRS,TCPIP*,qAS,9M2TPT:@200215z0312.81N/10133.17E_270/000g001t094r000p000h53b10087 WH1080+fowsr+NoseyWX SgBuloh/Malaysia
2013-06-20 02:15:02.819 9M2TPT-1  T 9M2TPT-1>APRS:}9M2TPT-13>APRS,TCPIP,9M2TPT-1*:@200215z0312.81N/10133.17E_270/000g001t094r000p000h53b10087 WH1080+fowsr+NoseyWX SgBuloh/Malaysia

Things that I observed:

1. If I don't put the filter into <digipeater><source> .. none from APRS-IS will get digipeated into RF
2. If I use /p filter, using my SSID (9M2TPT-13) for my WX, this won't get digipeated into RF either, but somehow it works if I use p/9M2TPT-1* 

There might have been some major changes from 2.05 I believe when the last time I don't even need to put filter in the <digipeater> section.

73, Hamid/9M2TPT

IW3IJQ

unread,
Jun 24, 2013, 3:44:41 AM6/24/13
to aprx-s...@googlegroups.com
Hi,
I didn't find any workaround.
I did downgrade to 2.6

Demetre Valaris

unread,
Jul 29, 2013, 6:17:55 AM7/29/13
to aprx-s...@googlegroups.com
Hi,

Has anyone found a solution to this problem yet? I see the same problem with IGATEing here,

73 de Demetre SV1UY

IW3IJQ

unread,
Jul 31, 2013, 3:38:09 AM7/31/13
to aprx-s...@googlegroups.com
Hi,

no solutions.....
We have to hope in OH2MQK.

Demetre Valaris

unread,
Jul 31, 2013, 4:09:36 AM7/31/13
to aprx-s...@googlegroups.com
Hi,

It's a pity because APRX seems to be the nicest and easiest IGATE to install and run and now it is broken.

I have made numerous changes and tests in the filters but I can't find a solution. Anything (not only messages) coming from APRSIS to an RF station do not make it through even if the receipient has been heard. Also the "filter b/callsign filters do not work either. Only

I hope OH2MQK will find some free time to fix this problem.

73 de Demetre SV1UY


--
You received this message because you are subscribed to a topic in the Google Groups "Aprx software" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/aprx-software/FbMcDXE_fdI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to aprx-softwar...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Regards
Demetre Ch. Valaris
e-mail: dval...@gmail.com
Radio e-mail: sv...@winlink.org
(to use my radio e-mail put //WL2K in the beginning of the subject line)
Reply all
Reply to author
Forward
0 new messages