Greetings.
When you set up the Pseudo-APRS-IS plugin, are you sure you updated its configuration to enable "Forward authorized transmissions from client through YAAC's upstream connection"? If that isn't checked, APRS packets from sub-clients of YAAC won't be sent onwards. And you have to use a valid passcode for the callsign specified by your sub-client, or the packets won't be forwarded either; I'm assuming the sub-clients are using your same callsign, but different SSID, so the same passcode used for your upstream Internet connection can be used in the sub-clients.
Also, incorrectly formatted packets won't go on upstream either, so make sure every packet you're injecting is compliant with the APRS Protocol Specification.
If your sub-client's packets show up in YAAC's Raw Packets display in magenta (sort of hot pink) text, that means there's some sort of syntax error in the packets.
Hope this helps.
Andrew, KA2DDO
author of YAAC
________________________________________
From:
[email protected] <
[email protected]> on behalf of vas22 <vassilis@...>
Sent: Sunday, November 26, 2023 2:19 PM
Hi,
I installed the Pseudo APRS-IS Server plug-in and I can successfully connect and receive packets using the Python aprslib client. However when I try to transmit a packet, I can see the packet in the raw messages log of YAAC but no actual transmission is happening. I have both option checkboxes checked and successfully logged in as an authenticated user.
I have a single port setup (Direwolf) and have enabled transmission, I can send beacon and messages from YAAC with no issues, problem is when connecting to the pseudo APRS-IS server.
Any suggestions on how to send messages from a Python script?
Thanks,
Vassilis
