The aprsispseudoserver plugin in YAAC provides a receive-only emulation of a real APRS-IS server, so other clients can listen to what the YAAC instance is listening to. However, it doesn't support forwarding transmissions through YAAC's other interfaces. The mini-webserver in YAAC is another way for other users (withot an APRS client, but just a web browser) to "look over the shoulder" of the YAAC user, but also doesn't allow injecting additional transmissions.
Is there a need to improve the aprsispseudoserver plugin to support authenticated transmit-capable connections? Note that YAAC is not optimized for being a digipeater or I-gate; it is optimized for being a user display, and can do the other functions as side-effects. You might be better to just run something like DireWolf or aprx on your headless Pi, and then connect to _it_ with YAAC (or other clients) from your systems with screens.
Andrew, KA2DDO
author of YAAC
________________________________________
From:
[email protected] <
[email protected]> on behalf of Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Sent: Saturday, October 29, 2022 8:17 AM
To:
[email protected]Subject: [yaac-users] Connect to YAAC IGATE/DIGI's port 14580?
Hi all,
Can we connect to a YAAC's session running as IGATE/DIGI in port 14580 using another APRS CLient in another PC in our LAN and can we see what is YAAC sees in it's radio port?
Furthermore can we also transmit messages and BEACONS using the other APRS Client program?
If this is possible, how is it done?
I am interested in running YACC in an RPi without monitor 24/7 as an IGATE/DIGI and use my Desktop PC to run another session of YAAC or APRSIS32 for doing the above. I know I can use VNC but mapping etc is too slow really.
73 de Demetre M0SUY
