17 May 2023 12:45 PM
Is anyone aware of an (undocumented) option to only bind an active gate to a specific network interface (or exclude interfaces)?
I have an interesting case where an active gate located in DC1 (external) reports two interfaces where one contains also an IP that belongs to a locally routed subnet in DC2 (internal). The result it that it can happen that agents in DC2 try to reach an Active gate endpoint reported by DC1 (which is of course not reachable or belongs to completely other services).
I know for that scenario it is adviseable to also set up network zones (which we have) but it still could be that a oneagent in DC2 tries the remote IP in it's serverlist as a fallback.
Solved! Go to Solution.
17 May 2023 12:58 PM
You can bind ActiveGate to specific interface using `bindToNetworkInterface` property in custom.properties file
Example:
[connectivity]
bindToNetworkInterface=192.168.1.1
17 May 2023 01:13 PM
Super, thanks!
Please lets add this to the documentation 🙂