Users have expressed the need to assign an IP other than the default IP (192.168.67.1) for Static profile / non-proxy mode.
Reasons given were the need to access preconfigured webapps on the same subnet or to ensure compliance with their network configuration and security policies.
This will make the system more inline with user expectations and normal experience. Since we don't in any way restrict the users from changing the "Static" profile's IP address, yet when done, it breaks the system in the current implementation.
Once implemented, a change in IP will not hamper the workings of the system.
Users have expressed the need to assign an IP other than the default IP (192.168.67.1) for Static profile / non-proxy mode.
Reasons given were the need to access preconfigured webapps on the same subnet or to ensure compliance with their network configuration and security policies.
This will make the system more inline with user expectations and normal experience. Since we don't in any way restrict the users from changing the "Static" profile's IP address, yet when done, it breaks the system in the current implementation.
Once implemented, a change in IP will not hamper the workings of the system.