After @madpsy created the very useful map and analysis service (https://lora-aprs.live/) the SYSLOG feature of the LoRa APRS iGate is "hijacked" in #177 .
I'm a new user and I quickly changed to my own SYSLOG server as I didn't like to send my SYSLOG unencrypted over the public internet. I soon noticed that the online map wasn't working anymore. It wasn't obvious to me that this was dependent on the SYSLOG config.
I suggest adding a few words on this in the GUI and/or add a second SYSLOG server for the few of us who have our own servers.
After @madpsy created the very useful map and analysis service ([https://lora-aprs.live/](https://lora-aprs.live/)) the SYSLOG feature of the LoRa APRS iGate is "hijacked" in [#177](https://github.com/richonguzman/LoRa_APRS_iGate/issues/177) .
I'm a new user and I quickly changed to my own SYSLOG server as I didn't like to send my SYSLOG unencrypted over the public internet. I soon noticed that the online map wasn't working anymore. It wasn't obvious to me that this was dependent on the SYSLOG config.
I suggest adding a few words on this in the GUI and/or add a second SYSLOG server for the few of us who have our own servers.
<!-- github-sync-id:3314475473 -->
Hi Peter,
this is not hijacked, just a recommendation for users without any syslog server ... just that.
Everyone is free to have its own solution , which surely will be custom made for each needs.
The online map of the lora-aprs.live page is needed by your own iGate sending syslog to this page. If disabled it won't be shown there.
please check this link: https://lora-aprs.live/help.html which explains a little how it works.
<!-- github-comment-id:3180735546 -->
You could also forward the same logs from your own syslog server to lora-aprs.live if you wanted.
As for being unencrypted - the logs are available for all to see once you send them so there's no benefit from encryption in transit.
You could also forward the same logs from your own syslog server to lora-aprs.live if you wanted.
As for being unencrypted - the logs are available for all to see once you send them so there's no benefit from encryption in transit.
<!-- github-comment-id:3183864867 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After @madpsy created the very useful map and analysis service (https://lora-aprs.live/) the SYSLOG feature of the LoRa APRS iGate is "hijacked" in #177 .
I'm a new user and I quickly changed to my own SYSLOG server as I didn't like to send my SYSLOG unencrypted over the public internet. I soon noticed that the online map wasn't working anymore. It wasn't obvious to me that this was dependent on the SYSLOG config.
I suggest adding a few words on this in the GUI and/or add a second SYSLOG server for the few of us who have our own servers.
Hi Peter,
this is not hijacked, just a recommendation for users without any syslog server ... just that.
Everyone is free to have its own solution , which surely will be custom made for each needs.
The online map of the lora-aprs.live page is needed by your own iGate sending syslog to this page. If disabled it won't be shown there.
please check this link: https://lora-aprs.live/help.html which explains a little how it works.
You could also forward the same logs from your own syslog server to lora-aprs.live if you wanted.
As for being unencrypted - the logs are available for all to see once you send them so there's no benefit from encryption in transit.