You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One small thing that it will be handy, it will be to add "hostname" to the configuration parameters (OGN-receiver.conf) the possibility to change the hostname, instead of the default of the ogn-receiver
The text was updated successfully, but these errors were encountered:
depending on your router keeping ogn-receiver as hostname will allow you to go directly to http://ogn-receiver:8080 same for other ports.
Changing the hostname will kill the standard way to access the receiver.
Seb,
That is true for accessing the RPi locally, however if you have several
stations and you need to monitor them remotely all the hostnames are the
same.
One workaround is to change: the overlay to disable, reboot, change the
hostname, overlay to enable and reboot again ..
On Thu, Jun 16, 2022 at 9:35 PM Sebastien Chaumontet < ***@***.***> wrote:
What is the use case?
depending on your router keeping ogn-receiver as hostname will allow you
to go directly to http://ogn-receiver:8080 same for other ports.
Changing the hostname will kill the standard way to access the receiver.
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6DYZ2IFH65I5VQEYGFNU3VPN6YZANCNFSM5W4EOQQA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
One small thing that it will be handy, it will be to add "hostname" to the configuration parameters (OGN-receiver.conf) the possibility to change the hostname, instead of the default of the ogn-receiver
The text was updated successfully, but these errors were encountered: