User story #20113
closed
It's not possible to make the agent listen on a specific interface
Added by Nicolas CHARLES about 3 years ago.
Updated almost 3 years ago.
Category:
System techniques
Description
solution: use bindtointerface, with a parameter in the "Rudder" node property
Default value is "::", unless if not ipv6 when it's ""
The correction allows to configure on what IP cf-serverd will listen by setting the following json value in node properties (for example if you want to force listening on 192.168.3.3
):
{
"server": {
"cf_serverd_bind_address": "192.168.3.3"
}
}
You must restart rudder cf-serverd after that change on impacted nodes with:
systemctl restart rudder-cf-serverd
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1727
- Target version changed from 6.2.11 to 6.2.12
- Status changed from Pending technical review to Pending release
- Description updated (diff)
- Fix check changed from To do to Error - Blocking
The cf-serverd service is not restarted when that configuration change. Restarting it by hand with systemctl restart rudder-cf-serverd
make it works as expected:
[root@agent1 vagrant]# netstat -taupen | grep 5309
tcp6 0 0 :::5309 :::* LISTEN 0 72506 21811/cf-serverd
[root@agent1 vagrant]# systemctl restart rudder-cf-serverd
[root@agent1 vagrant]# netstat -taupen | grep 5309
tcp 0 0 192.168.3.3:5309 0.0.0.0:* LISTEN 0 75304 22789/cf-serverd
- Subject changed from It's not possible to make the agent listen on a specific port to It's not possible to make the agent listen on a specific interface
- Fix check changed from Error - Blocking to Checked
- Description updated (diff)
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.12 and 7.0.0~rc2 which were released today.
Also available in: Atom
PDF