|
Another bug I have found.? When I receive a message that goes through my gateway the first message shows as received from the originating station (in this case N8VNR) and subsequent messages are shown as received from my gateway (WG3K-15).
YAAC is also sending ACKs to my gateway as well:
2021-12-18 19:55:35 EST: >APJYC1,qAO,::N8VNR????:ackC000a
2021-12-18 19:56:08 EST: >APJYC1,qAO,::WG3K-15??:ackC000a
2021-12-18 19:56:41 EST: >APJYC1,qAO,::WG3K-15??:ackC000a
73,
Eric WG3K
|
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, December 18th, 2021 at 20:18, Eric H. Christensen via groups.io <eric@...> wrote: Another bug I have found.? When I receive a message that goes through my gateway the first message shows as received from the originating station (in this case N8VNR) and subsequent messages are shown as received from my gateway (WG3K-15). Just grabbed the received packets from the log. It looks like YAAC might not be handling third-party packets appropriately? I have no idea why these packets are coming in as third-party packets when the initial packet comes in normally, but I'd think that YAAC should be able to handle them properly. N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ooh, I see it acked now. and your test.{C000b WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ooh, I see it acked now. and your test.{C000b N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC0007 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ackC0007 N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :and now the chat is doing the dupe thing{C000c WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :and now the chat is doing the dupe thing{C000c null>APJYC1,WIDE2-2::N8VNR :The dupe thing?{C0008 N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC0008 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ooh, I see it acked now. and your test.{C000b WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR :The dupe thing?{C0008 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ackC0008 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :and now the chat is doing the dupe thing{C000c WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ooh, I see it acked now. and your test.{C000b null>APJYC1,WIDE2-2::N8VNR :I'm not sure why I'm showing up as qAO which should be a rx-only{C0009 N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC0009 WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR :I'm not sure why I'm showing up as qAO which should be a rx-only{C0009 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ackC0009 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :and now the chat is doing the dupe thing{C000c null>APJYC1,WIDE2-2::N8VNR :i-gate. Just verified my settings... Should be bidirectional.{C000a N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC000a WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR :i-gate. Just verified my settings... Should be bidirectional.{C000a 73, Eric WG3K
|
OK, finally got this figured out. It seems a long time ago in build#146, I thought I was fixing a bug with station identification for Tx I-gating, and I fixed it wrong. You are seeing the results of this, because of the callsign change in the Tx I-gate transmission, which is getting echoed back to you by a local RF digipeater (K3NAL-1 in your sample log below), so it does look like a transmission from a different originating station (i.e., originated by your I-gate WG3K-15). I will be fixing this in the first build of the New Year. Andrew, KA2DDO ________________________________________ From: [email protected] < [email protected]> on behalf of Eric H. Christensen via groups.io <eric@...> Sent: Saturday, December 18, 2021 11:14 PM To: [email protected]Subject: Re: [yaac-users] [bug] Same message received from different sender. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, December 18th, 2021 at 20:18, Eric H. Christensen via groups.io <eric@...> wrote: Another bug I have found. When I receive a message that goes through my gateway the first message shows as received from the originating station (in this case N8VNR) and subsequent messages are shown as received from my gateway (WG3K-15). Just grabbed the received packets from the log. It looks like YAAC might not be handling third-party packets appropriately? I have no idea why these packets are coming in as third-party packets when the initial packet comes in normally, but I'd think that YAAC should be able to handle them properly. N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ooh, I see it acked now. and your test.{C000b WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ooh, I see it acked now. and your test.{C000b N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC0007 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ackC0007 N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :and now the chat is doing the dupe thing{C000c WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :and now the chat is doing the dupe thing{C000c null>APJYC1,WIDE2-2::N8VNR :The dupe thing?{C0008 N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC0008 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ooh, I see it acked now. and your test.{C000b WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR :The dupe thing?{C0008 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ackC0008 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :and now the chat is doing the dupe thing{C000c WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ooh, I see it acked now. and your test.{C000b null>APJYC1,WIDE2-2::N8VNR :I'm not sure why I'm showing up as qAO which should be a rx-only{C0009 N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC0009 WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR :I'm not sure why I'm showing up as qAO which should be a rx-only{C0009 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :ackC0009 WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR>APJYC1,TCPIP,WG3K-15*::WG3K :and now the chat is doing the dupe thing{C000c null>APJYC1,WIDE2-2::N8VNR :i-gate. Just verified my settings... Should be bidirectional.{C000a N8VNR>APJYC1:N8VNR>APJYC1,TCPIP*,qAC,T2ALBERTA::WG3K :ackC000a WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR :i-gate. Just verified my settings... Should be bidirectional.{C000a 73, Eric WG3K
|
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, January 1st, 2022 at 12:46, Andrew P. <andrewemt@...> wrote: OK, finally got this figured out.
It seems a long time ago in build#146, I thought I was fixing a bug with station identification for Tx I-gating, and I fixed it wrong. You are seeing the results of this, because of the callsign change in the Tx I-gate transmission, which is getting echoed back to you by a local RF digipeater (K3NAL-1 in your sample log below), so it does look like a transmission from a different originating station (i.e., originated by your I-gate WG3K-15).
I will be fixing this in the first build of the New Year. Great, glad you were able to find the problem. 73, Eric WG3K
|
Andrew,
Just tested out the fix for this bug but I'm not sure it was fixed completely. I've attached two screenshots to this message. The messages screen shows the incoming message coming in multiple times from different senders, but never from the proper sender (N8VNR-5). The chat screen, however, does appear to show the message appropriately.
Here are the relevant packets:
08/Jan/2022 15:54:27,"APRS-IS: /192.168.1.200[WG3K]","null>APJYC1,WIDE2-2::N8VNR-5 :Good morning{C0003"
08/Jan/2022 15:54:27,"APRS-IS: /192.168.1.200[WG3K]","null>APJYC1,WIDE2-2::N8VNR-5 :Good morning{C0003"
08/Jan/2022 15:54:28,"APRS-IS: /192.168.1.200[WG3K]","N8VNR-5>APDR16:N8VNR-5>APDR16,TCPIP*,qAC,T2SJC::WG3K :ackC0003"
08/Jan/2022 15:54:29,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR-5 :Good morning{C0003"
08/Jan/2022 15:54:39,"APRS-IS: /192.168.1.200[WG3K]","N8VNR-5>APDR16:N8VNR-5>APDR16,TCPIP*,qAC,T2SJC::WG3K :o/{4"
08/Jan/2022 15:54:39,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::N8VNR-5 :ack4"
08/Jan/2022 15:54:40,"APRS-IS: /192.168.1.200[WG3K]","WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WG3K-15*::WG3K :o/{4"
08/Jan/2022 15:54:40,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WG3K-15 :ack4"
08/Jan/2022 15:54:45,"APRS-IS: /192.168.1.200[WG3K]","WX4EMC-5>APRS:WX4EMC-5>APRS,K3NAL-1*,WIDE2-1,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WX4EMC-5*::WG3K :o/{4"
08/Jan/2022 15:54:45,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WX4EMC-5 :ack4"
08/Jan/2022 15:54:47,"APRS-IS: /192.168.1.200[WG3K]","WX4EMC-5>APRS:WX4EMC-5>APRS,K3NAL-1,W3SMD,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WX4EMC-5*::WG3K :o/{4"
08/Jan/2022 15:54:47,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WX4EMC-5 :ack4"
08/Jan/2022 15:55:43,"APRS-IS: /192.168.1.200[WG3K]","WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WG3K-15*::WG3K :o/{4"
08/Jan/2022 15:55:44,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WG3K-15 :ack4"
Thanks for your hard work building and maintaining YAAC. It's quite awesome!
73,
Eric WG3K
|
Did you upgrade both station WG3K and WG3K-15? The latter station looks like where the problem is. ________________________________________ From: [email protected] < [email protected]> on behalf of Eric H. Christensen via groups.io <eric@...> Sent: Saturday, January 8, 2022 11:17 AM To: [email protected]Subject: Re: [yaac-users] [bug] Same message received from different sender. Andrew, Just tested out the fix for this bug but I'm not sure it was fixed completely. I've attached two screenshots to this message. The messages screen shows the incoming message coming in multiple times from different senders, but never from the proper sender (N8VNR-5). The chat screen, however, does appear to show the message appropriately. Here are the relevant packets: 08/Jan/2022 15:54:27,"APRS-IS: /192.168.1.200[WG3K]","null>APJYC1,WIDE2-2::N8VNR-5 :Good morning{C0003" 08/Jan/2022 15:54:27,"APRS-IS: /192.168.1.200[WG3K]","null>APJYC1,WIDE2-2::N8VNR-5 :Good morning{C0003" 08/Jan/2022 15:54:28,"APRS-IS: /192.168.1.200[WG3K]","N8VNR-5>APDR16:N8VNR-5>APDR16,TCPIP*,qAC,T2SJC::WG3K :ackC0003" 08/Jan/2022 15:54:29,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR-5 :Good morning{C0003" 08/Jan/2022 15:54:39,"APRS-IS: /192.168.1.200[WG3K]","N8VNR-5>APDR16:N8VNR-5>APDR16,TCPIP*,qAC,T2SJC::WG3K :o/{4" 08/Jan/2022 15:54:39,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::N8VNR-5 :ack4" 08/Jan/2022 15:54:40,"APRS-IS: /192.168.1.200[WG3K]","WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WG3K-15*::WG3K :o/{4" 08/Jan/2022 15:54:40,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WG3K-15 :ack4" 08/Jan/2022 15:54:45,"APRS-IS: /192.168.1.200[WG3K]","WX4EMC-5>APRS:WX4EMC-5>APRS,K3NAL-1*,WIDE2-1,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WX4EMC-5*::WG3K :o/{4" 08/Jan/2022 15:54:45,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WX4EMC-5 :ack4" 08/Jan/2022 15:54:47,"APRS-IS: /192.168.1.200[WG3K]","WX4EMC-5>APRS:WX4EMC-5>APRS,K3NAL-1,W3SMD,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WX4EMC-5*::WG3K :o/{4" 08/Jan/2022 15:54:47,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WX4EMC-5 :ack4" 08/Jan/2022 15:55:43,"APRS-IS: /192.168.1.200[WG3K]","WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WG3K-15*::WG3K :o/{4" 08/Jan/2022 15:55:44,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WG3K-15 :ack4" Thanks for your hard work building and maintaining YAAC. It's quite awesome! 73, Eric WG3K
|
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, January 8th, 2022 at 12:14, Andrew P. <andrewemt@...> wrote: Did you upgrade both station WG3K and WG3K-15? The latter station looks like where the problem is. WG3K-15 is a Microsat WX3in1 Plus 2.0, not a YAAC instance. 73, Eric WG3K
|
Just because it's not YAAC doesn't mean that it might not have a code bug. Looking at the packet samples you sent earlier:
08/Jan/2022 15:54:27,"APRS-IS: /192.168.1.200[WG3K]","null>APJYC1,WIDE2-2::N8VNR-5 ?:Good morning{C0003"
08/Jan/2022 15:54:27,"APRS-IS: /192.168.1.200[WG3K]","null>APJYC1,WIDE2-2::N8VNR-5 ?:Good morning{C0003"
08/Jan/2022 15:54:28,"APRS-IS: /192.168.1.200[WG3K]","N8VNR-5>APDR16:N8VNR-5>APDR16,TCPIP*,qAC,T2SJC::WG3K ? ? :ackC0003"
08/Jan/2022 15:54:29,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1:WG3K>APJYC1,K3NAL-1*,WIDE2-1,qAO,WG3K,qAR,WG3K-15::N8VNR-5 ?:Good morning{C0003"
08/Jan/2022 15:54:39,"APRS-IS: /192.168.1.200[WG3K]","N8VNR-5>APDR16:N8VNR-5>APDR16,TCPIP*,qAC,T2SJC::WG3K ? ? :o/{4"
08/Jan/2022 15:54:39,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::N8VNR-5 ?:ack4"
08/Jan/2022 15:54:40,"APRS-IS: /192.168.1.200[WG3K]","WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WG3K-15*::WG3K ? ? :o/{4"
08/Jan/2022 15:54:40,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WG3K-15 ?:ack4"
08/Jan/2022 15:54:45,"APRS-IS: /192.168.1.200[WG3K]","WX4EMC-5>APRS:WX4EMC-5>APRS,K3NAL-1*,WIDE2-1,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WX4EMC-5*::WG3K ? ? :o/{4"
08/Jan/2022 15:54:45,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WX4EMC-5 :ack4"
08/Jan/2022 15:54:47,"APRS-IS: /192.168.1.200[WG3K]","WX4EMC-5>APRS:WX4EMC-5>APRS,K3NAL-1,W3SMD,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WX4EMC-5*::WG3K ? ? :o/{4"
08/Jan/2022 15:54:47,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WX4EMC-5 :ack4"
08/Jan/2022 15:55:43,"APRS-IS: /192.168.1.200[WG3K]","WG3K-15>APMI06:WG3K-15>APMI06,K3NAL-1,WIDE2*,qAR,WG3K-15:}N8VNR-5>APDR16,TCPIP,WG3K-15*::WG3K ? ? :o/{4"
08/Jan/2022 15:55:44,"APRS-IS: /192.168.1.200[WG3K]","WG3K>APJYC1::WG3K-15 ?:ack4"
Notice the bolded lines at 15:54:40 and 15:55:43. It looks like your Wx3in1 has the same defect(?) I just fixed in YAAC, where it puts the I-gate's callsign-SSID in the RF packet's sender field, rather than in the digipeat alias list as an already-"digipeated"
station. Of course, that's what the documentation at said, which I why I had made that other change back in build#146.
Unfortunately, we can't check aprs-is.net right now because it seems to be under a DNS spoofing attack right now (or maybe it's just me).
Andrew, KA2DDO
author of YAAC
________________________________________
Sent: Saturday, January 8, 2022 1:05 PM
Subject: Re: [yaac-users] [bug] Same message received from different sender.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, January 8th, 2022 at 12:14, Andrew P. <andrewemt@...> wrote:
> Did you upgrade both station WG3K and WG3K-15? The latter station looks like where the problem is.
WG3K-15 is a Microsat WX3in1 Plus 2.0, not a YAAC instance.
73,
Eric WG3K
|
