Project

General

Profile

Actions

User story #20113

closed

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

Added by Nicolas CHARLES 7 months ago. Updated 5 months ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Suggestion strength:
User visibility:
Effort required:

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 open2 closed)

User story #20114: add a default value for bind to interface in rudder parameterReleasedAlexis MOUSSETActions
User story #20427: missing default value in initial promisesReleasedAlexis MOUSSETActions
Actions #1

Updated by Nicolas CHARLES 7 months ago

  • Status changed from New to In progress
Actions #2

Updated by Nicolas CHARLES 7 months 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
Actions #3

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 6.2.11 to 6.2.12
Actions #4

Updated by Nicolas CHARLES 6 months ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by François ARMAND 5 months ago

  • Description updated (diff)

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 #6

Updated by Alexis MOUSSET 5 months 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 #8

Updated by François ARMAND 5 months ago

  • Description updated (diff)
Actions #9

Updated by Vincent MEMBRÉ 5 months ago

  • 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.

Actions

Also available in: Atom PDF