The first question is, why were you advised to do that? That port number is for when you want unfiltered full-planet feeds from the APRS-IS. Do you really need that much traffic flooding into your DireWolf instance? Remember, DireWolf's purpose is to be an RF TNC; it supports I-gate connections primarily so you can _contribute_ to the APRS-IS by forwarding received RF traffic to the Internet, and optionally re-transmit Internet traffic specifically addressed to RF stations you have heard. You really don't need to hear any other Internet traffic in DireWolf. Make a connection like that in an APRS display client like APRSIS32 or YAAC if you want to see planet-level traffic, but DireWolf won't present that data in a usable form.
Andrew, KA2DDO
author of YAAC
________________________________________
From:
[email protected] <
[email protected]> on behalf of Douglas Pervine, N1OBU <douglas.pervine@...>
Sent: Sunday, September 8, 2024 7:48 AM
To:
[email protected]Subject: [direwolf] How to change APRS-IS connection port?
I'm testing a local (non upstream) APRS-IS server and was advised to switch all my client connections to port 10152. How do I configure/change that in Direwolf? I am using 1.8D.
Thanks
Doug
