User story #20113: It's not possible to make the agent listen on a specific interface - Rudder - Issue Tracker

Actions

Copy link

User story #20113

closed

It's not possible to make the agent listen on a specific interface

Added by Nicolas CHARLES over 2 years ago. Updated over 2 years ago.

Status:

Released

Priority:

N/A

Assignee:

Alexis Mousset

Category:

System techniques

Target version:

6.2.12

Pull Request:

https://github.com/Normation/rudder-t...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

To do

Fix check:

Checked

Regression:

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

Subtasks 2 (0 open — 2 closed)

Actions

Copy link

Updated by Nicolas CHARLES over 2 years ago

Status changed from New to In progress

Actions

Copy link

Updated by Nicolas CHARLES over 2 years ago

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

PR https://github.com/Normation/rudder-techniques/pull/1727

Actions

Copy link

Updated by Vincent MEMBRÉ over 2 years ago

Target version changed from 6.2.11 to 6.2.12

Actions

Copy link

Updated by Nicolas CHARLES over 2 years ago

Status changed from Pending technical review to Pending release

Applied in changeset rudder-techniques|1519888f24fc20f03392688f109adc368f110c1e.

Actions

Copy link

Updated by François ARMAND over 2 years ago

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

Actions

Copy link

Updated by Alexis Mousset over 2 years ago

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

Actions

Copy link