I am having some issues getting YAAC to igate to RF. Digipeating and RF->IS seems to be working fine, however, if I send a poisition message from a handy callsign-7 in to the gateway (gwcallsign-10) the handy's call does not get listed as a local station (not sure if is meant to). The handy's position gets digipeated out, and it arrives in the aprs-is system just fine.
If someone sends that handy's callsign a message, I see it in the RAW data in YACC, coming in via TCPIP, but nothing gets put over the air.
Digipeat alias is wide1-1,wide2-2, trace..... in both digipeat tab and under the relevant serialTNC port. Check boxes for gating RF->IS and IS->RF both ticked. Running version from 30th Jan 2017.
I do not see anything in the 'Stations TX I-Gated by this station' list either.
It is possibly a path issue, but not sure.
Cheers !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Interesting. Could you post a display from the View Message History for that one HT? You get this by right-clicking on the HT station (on the map or in the Stations/Objects List) and selecting View Message History. Lets see if that HT is considered local or considered distant because it isn't being heard by YAAC until after some other nearby digipeater repeats it.
The HT would not show up in the Stations TX I-Gated display; that only shows Internet stations being proxied to local RF by YAAC (i.e., an Internet-relayed station sending a text message to a station local to YAAC). So if, for example, a station on the other side of the country (either RF or directly Internet-connected) sent a text message to your HT, that Internet station would show up in the table (because it sent traffic that YAAC needed to forward to RF to get it to the HT), but the HT wouldn't (because the HT's didn't come to YAAC over the Internet).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have to add, other than this igate->rf issue, where YAAC is seemingly not recognising the HT as a local station, everything else is working perfectly Andrew. The TNC here is a KAM, firmware 6.1, in KISS mode.
Just to confirm, the HT is on low power, and not picked up by any other digipeater/gateway around here, and is only picked up by MB7UNE-10 running YAAC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
seems like setting IS-RF number of hops to 2 turned the HT into a local station, in that it would show up when filter->stations with local contact->local stations was selected. Still no IS to RF though, to that handy (FT1XD) or a tm-710ge. Very odd.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Bear in mind that IS->RF gating doesn't send everything your Tx I-gate receives from the Internet. To prevent clogging the local RF channel (which doesn't have very much bandwidth when using the standard 1200-baud modem), the only traffic that is forwarded IS->RF is:
Internet text message traffic specifically addressed to an RF-local station (not to some multicast address), and
the next position beacon from the sending Internet station that addressed traffic to an RF-local station, so the RF-local station knows where the originating station is located.
So, if no Internet traffic is explicitly addressed to an RF-local station, nothing will be Tx I-gated (keeping the RF channel available for local RF stations).
Now, the fact that you needed to set the hop count to 2 to get the HT treated as local is odd, since the message history you posted does indeed show that your I-gate was the first digipeater for the HT. I will investigate if there is a counter offset bug in determining the hop count, such that 1-hop (direct) RF can't ever have any local stations.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-01-15
Andrew,
Was this issue addressed? I have a similar problem trying to i-Gate to WLNK-1. My HT (low power, via = my YAAC station) sends a message, is gated to APRS-IS and I see the response from WLNK-1 both on the raw packet window and in the RX log but it is never transmitted via RF. TX log has the message out to WLNK-1 but not out to the HT. The HT is listed as a local station.
I have reviewed the setup instructions and I'm running the 10-Jan-2020 version. Any thoughts not already in this thread?
Many thanks,
Glen, NK1N
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-01-18
Andrew,
As a follow up, I tried it with SMSGTE. I can show YAAC received the message on RF and gated to APRS-IS. The ACK is received from the Internet but is never transmitted to RF even though it is logged in the Stations Tx I-Gated list. What might stop it at that point?
Many thanks,
Glen, NK1N
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmm.... Is the I-gate station actually able to transmit anything to RF successfully? Beacons, etc. It might just be a transmission inability. Is it showing up in the AX25xmit log files as sent to the RF port?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-01-28
Sorry for the sluggish response.
Yes, the station works as an RF->RF digipeater (WIDE1-1) along with sending my beacons, my messages and acks. The AX25xmit-<date>.csv files do not list the packets that should have been i-gated from the net. Those packets do show up in the AX25rcvd<date>.csv files as received from the net. </date></date>
If I am the only one noticing this, I must have missed something simple.
Many thanks,
Glen, NK1N
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just noticed this thread started 3 years (!) ago. What build of YAAC are you currently running? I've made several changes to the digipeat and I-gate logic over the last three years. Please upgrade to the latest build (as of this date, 147), and tell me if you still have the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-01-29
OK, I was on 146 before I asked my questions. 147 coming up.
Many thanks,
Glen, NK1N
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-01-29
On 147 now and unfortunately, no change. I'm using an HT to send an SMS message to SMSGTE.
-AX25rcvd-2020-01-28 shows the packet received on RF
-AX25xmit-2020-01-28 shows the packet digipeaded on RF
-AX25xmit-2020-01-28 shows the pacted i-gated to APRS-IS
-AX25rcvd-2020-01-28 shows the ack from SMSGTE directly from APRS-IS
-the next RF entry in AX25xmit-2020-01-28 is a digipeated beacon (four minutes later)
-SMSGTE is in the Stations Tx I-Gated by This Station list
:-(
Thanks for noodling on this
Glen, NK1N
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi,
I am having some issues getting YAAC to igate to RF. Digipeating and RF->IS seems to be working fine, however, if I send a poisition message from a handy callsign-7 in to the gateway (gwcallsign-10) the handy's call does not get listed as a local station (not sure if is meant to). The handy's position gets digipeated out, and it arrives in the aprs-is system just fine.
If someone sends that handy's callsign a message, I see it in the RAW data in YACC, coming in via TCPIP, but nothing gets put over the air.
Digipeat alias is wide1-1,wide2-2, trace..... in both digipeat tab and under the relevant serialTNC port. Check boxes for gating RF->IS and IS->RF both ticked. Running version from 30th Jan 2017.
I do not see anything in the 'Stations TX I-Gated by this station' list either.
It is possibly a path issue, but not sure.
Cheers !
Interesting. Could you post a display from the View Message History for that one HT? You get this by right-clicking on the HT station (on the map or in the Stations/Objects List) and selecting View Message History. Lets see if that HT is considered local or considered distant because it isn't being heard by YAAC until after some other nearby digipeater repeats it.
The HT would not show up in the Stations TX I-Gated display; that only shows Internet stations being proxied to local RF by YAAC (i.e., an Internet-relayed station sending a text message to a station local to YAAC). So if, for example, a station on the other side of the country (either RF or directly Internet-connected) sent a text message to your HT, that Internet station would show up in the table (because it sent traffic that YAAC needed to forward to RF to get it to the HT), but the HT wouldn't (because the HT's didn't come to YAAC over the Internet).
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
hi andrew, thanks for the info. Please find attached a screen grab. The gateway callsign here is mb7une-10.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Have to add, other than this igate->rf issue, where YAAC is seemingly not recognising the HT as a local station, everything else is working perfectly Andrew. The TNC here is a KAM, firmware 6.1, in KISS mode.
Just to confirm, the HT is on low power, and not picked up by any other digipeater/gateway around here, and is only picked up by MB7UNE-10 running YAAC.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
seems like setting IS-RF number of hops to 2 turned the HT into a local station, in that it would show up when filter->stations with local contact->local stations was selected. Still no IS to RF though, to that handy (FT1XD) or a tm-710ge. Very odd.
Bear in mind that IS->RF gating doesn't send everything your Tx I-gate receives from the Internet. To prevent clogging the local RF channel (which doesn't have very much bandwidth when using the standard 1200-baud modem), the only traffic that is forwarded IS->RF is:
So, if no Internet traffic is explicitly addressed to an RF-local station, nothing will be Tx I-gated (keeping the RF channel available for local RF stations).
Now, the fact that you needed to set the hop count to 2 to get the HT treated as local is odd, since the message history you posted does indeed show that your I-gate was the first digipeater for the HT. I will investigate if there is a counter offset bug in determining the hop count, such that 1-hop (direct) RF can't ever have any local stations.
Andrew,
Was this issue addressed? I have a similar problem trying to i-Gate to WLNK-1. My HT (low power, via = my YAAC station) sends a message, is gated to APRS-IS and I see the response from WLNK-1 both on the raw packet window and in the RX log but it is never transmitted via RF. TX log has the message out to WLNK-1 but not out to the HT. The HT is listed as a local station.
I have reviewed the setup instructions and I'm running the 10-Jan-2020 version. Any thoughts not already in this thread?
Many thanks,
Glen, NK1N
Andrew,
As a follow up, I tried it with SMSGTE. I can show YAAC received the message on RF and gated to APRS-IS. The ACK is received from the Internet but is never transmitted to RF even though it is logged in the Stations Tx I-Gated list. What might stop it at that point?
Many thanks,
Glen, NK1N
Hmmm.... Is the I-gate station actually able to transmit anything to RF successfully? Beacons, etc. It might just be a transmission inability. Is it showing up in the AX25xmit log files as sent to the RF port?
Sorry for the sluggish response.
Yes, the station works as an RF->RF digipeater (WIDE1-1) along with sending my beacons, my messages and acks. The AX25xmit-<date>.csv files do not list the packets that should have been i-gated from the net. Those packets do show up in the AX25rcvd<date>.csv files as received from the net. </date></date>
If I am the only one noticing this, I must have missed something simple.
Many thanks,
Glen, NK1N
I just noticed this thread started 3 years (!) ago. What build of YAAC are you currently running? I've made several changes to the digipeat and I-gate logic over the last three years. Please upgrade to the latest build (as of this date, 147), and tell me if you still have the problem.
OK, I was on 146 before I asked my questions. 147 coming up.
Many thanks,
Glen, NK1N
On 147 now and unfortunately, no change. I'm using an HT to send an SMS message to SMSGTE.
-AX25rcvd-2020-01-28 shows the packet received on RF
-AX25xmit-2020-01-28 shows the packet digipeaded on RF
-AX25xmit-2020-01-28 shows the pacted i-gated to APRS-IS
-AX25rcvd-2020-01-28 shows the ack from SMSGTE directly from APRS-IS
-the next RF entry in AX25xmit-2020-01-28 is a digipeated beacon (four minutes later)
-SMSGTE is in the Stations Tx I-Gated by This Station list
:-(
Thanks for noodling on this
Glen, NK1N
I am now registered - Glen, NK1N