I am experimenting with the web.address feature as a means of isolating traffic on a multi-use server and have configured it to use a 2nd IP address assigned to the same NIC as the primary IP address as so:
[object Object]
[object Object]
However, when the traccar service is restarted, the UI is listening on some other IP in the Automatic Private IP Addressing range which coincidentally corresponds to the Remote NDIS Compatible Device psuedo NIC (I think the server's OOB management card):
[object Object]
Logs indicate no issues:
[object Object]
Debug log references the odd IP:
[object Object]
2024-02-17 15:04:36 DEBUG: ServerConnector@3b45242b{HTTP/1.1, (http/1.1)}{:8080} added {sun.nio.ch.ServerSocketChannelImpl[/169.254.41.152:8080],POJO}
And I confirmed the UI is listening on 169.254.41.152:8080. I don't see any other web.* settings that may come into play here.
Not a showstopper for me but if there's a way around it, I would appreciate it. Thanks for a great product.
I am experimenting with the web.address feature as a means of isolating traffic on a multi-use server and have configured it to use a 2nd IP address assigned to the same NIC as the primary IP address as so:
However, when the traccar service is restarted, the UI is listening on some other IP in the Automatic Private IP Addressing range which coincidentally corresponds to the Remote NDIS Compatible Device psuedo NIC (I think the server's OOB management card):
Logs indicate no issues:
Debug log references the odd IP:
And I confirmed the UI is listening on 169.254.41.152:8080. I don't see any other web.* settings that may come into play here.
Not a showstopper for me but if there's a way around it, I would appreciate it. Thanks for a great product.