Project

General

Profile

Actions

User story #9693

closed

Enable IPv6 for cf-serverd

Added by Alexander Brunhirl about 6 years ago. Updated about 5 years ago.

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

Description

Hi,

I've enabled a IPv6 network in the allowed hosts, but the "cf-serverd" still seems to listen only on IPv4.

Best regards,
Alex

System: openSuSE Leap 42.1 (same as SLES12 SP1)

# netstat -annp | egrep -w "5309|443|514" 
tcp        0      0 0.0.0.0:5309            0.0.0.0:*               LISTEN      2081/cf-serverd     
tcp        0      0 0.0.0.0:514             0.0.0.0:*               LISTEN      763/rsyslogd        
tcp        0      0 :::443                  :::*                    LISTEN      1480/httpd-prefork  
tcp        0      0 :::514                  :::*                    LISTEN      763/rsyslogd        
udp        0      0 0.0.0.0:514             0.0.0.0:*                           763/rsyslogd        
udp        0      0 :::514                  :::*                                763/rsyslogd        
# 

Related issues 1 (0 open1 closed)

Related to Rudder - User story #9269: Add IPV6 support in rudder-initReleasedAlexis MoussetActions
Actions #1

Updated by Alexis Mousset about 6 years ago

  • Category changed from Server components to System techniques

We will:

Enable IPv6 (using bindinterface => "::") on:

  • Windows
  • BSD
  • Compatible Linux

And stay in IPv4 for now on:

  • Incompatible Linux
  • AIX
  • Solaris

The test for Linux can be based on the existence of "/proc/net/if_inet6".

Actions #2

Updated by Alexis Mousset about 6 years ago

We could backport this on servers only (less risky and remote run is not as easy/useful) for 3.1/3.2.

Actions #3

Updated by Alexis Mousset about 6 years ago

  • Tracker changed from Bug to User story
  • Subject changed from Enable IPv6 on Rudder Master issue to Enable IPv6 for cf-serverd
  • Target version changed from 4.0.1 to 3.1.17
Actions #4

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #5

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #6

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #8

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #9

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #10

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #11

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #12

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 3.1.25 to 4.3.0~beta1
Actions #13

Updated by Alexis Mousset over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions #14

Updated by Alexis Mousset about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1219
Actions #15

Updated by Alexis Mousset about 5 years ago

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

Updated by Benoît PECCATTE about 5 years ago

  • Parent task deleted (#9269)
Actions #17

Updated by Benoît PECCATTE about 5 years ago

Actions #18

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0~beta1 which was released today.

Actions

Also available in: Atom PDF