Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forwarding all packets #19

Open
marrold opened this issue Jan 4, 2023 · 3 comments
Open

Forwarding all packets #19

marrold opened this issue Jan 4, 2023 · 3 comments

Comments

@marrold
Copy link

marrold commented Jan 4, 2023

Hi,

I was looking for an APRS-IS proxy so I can use Track Direct to have a local map of heard stations without the deduping behaviour and still forward packets to the public APRS-IS servers.

Looking at the config / code you currently need to supply patterns to match on before forwarding, but if I'm reading it right the matched pattern is also used as the callsign to login to APRS-IS with? Just wanted to check that's the case and if so I'm curious why you submit them as the user that sent the beacon rather than under your own callsign ?

Cheers

@lazywalker
Copy link
Owner

Hi,

The patterns is optional, the software use these patterns to replace all matching texts(not only the callsign, just for example), you can simply forward all packages to a APRS-IS with file logs enabled by:

aprsproxy -f -v

73

@marrold
Copy link
Author

marrold commented Jan 9, 2023

Hi, this configuration without a filter won't relay packets to the second APRS-IS server though right?

Thanks

@lazywalker
Copy link
Owner

It will forward all packages to the default APRS-IS which is china.aprs2.net:14580 at this moment, you can use this parameter to specify the target

-r, --remote

aprsproxy -r rotate.aprs2.net:14580 -f -v

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants