[
https://issues.apache.org/jira/browse/GUACAMOLE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Böhm updated GUACAMOLE-1252:
------------------------------------
Description:
This [change|https://issues.apache.org/jira/browse/GUACAMOLE-1001] introduced
the functionality to read the ip address from the OS and write it to the NAS IP
address of the RADIUS protocol.
However, this is not a proper solution when Guacamole runs in Docker as in this
case the virtual internal IP address is used.
As discussed in the mailing-list, I propose to make it configurable how the NAS
IP address should be created, either automatically from the OS or manually from
a config parameter (or not at all).
was:
This change introduced the functionality to read the ip address from the OS and
write it to the NAS IP address of the RADIUS protocol.
However, this is not a proper solution when Guacamole runs in Docker as in this
case the virtual internal IP address is used.
As discussed in the mailing-list, I propose to make it configurable how the NAS
IP address should be created, either automatically from the OS or manually from
a config parameter (or not at all).
> NAS-IP-Adress should be configurable
> ------------------------------------
>
> Key: GUACAMOLE-1252
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole-auth-radius
> Affects Versions: 1.3.0
> Reporter: Michael Böhm
> Priority: Critical
>
> This [change|https://issues.apache.org/jira/browse/GUACAMOLE-1001] introduced
> the functionality to read the ip address from the OS and write it to the NAS
> IP address of the RADIUS protocol.
> However, this is not a proper solution when Guacamole runs in Docker as in
> this case the virtual internal IP address is used.
> As discussed in the mailing-list, I propose to make it configurable how the
> NAS IP address should be created, either automatically from the OS or
> manually from a config parameter (or not at all).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
