Idea ID: 2767688

Possibility for agentcache to support ipv4 and ipv6 both listening on 8081 port

Status : New Idea
over 1 year ago

We can manage to change ipv4 to ipv6 for agent-cache and vice versa, but not both ipv4 and ipv6 at the same time listening on 8081.

We would like this possibility to have agent cache listening on both ipv4 and ipv6.
The current workaround is to add a netcat instance listening on 8081:
Example:

ncat -4 -l --keep-open 0.0.0.0 8081 --sh-exec "ncat -6 ::1 8081"

[root@coreSA ~]# netstat -tulpn|grep 8081
tcp        0      0 0.0.0.0:8081            0.0.0.0:*                       LISTEN      30977/ncat            
tcp        0      0 :::8081                     :::*                                LISTEN      17988/python2.7

Or  swap them,so that netcat will create an ipv6 instance "ncat -6 -l --keep-open :: 8081 --sh-exec "ncat -4 127.0.0.1 8081"
and agentcache will be configured on ipv4.

HOW-TO-REPRODUCE:

Enabling or disabling ipv6 works just for ipv4 or ipv6 but not for both at the same time.

The Webserver for the agentcache on port 8081 doesn't support IPv6.
Here's an example to prove it:

************************************************
[root@coreSA ~]# wget http://localhost:8081
--2020-02-26 15:54:15-- http://localhost:8081/
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:8081... failed: Connection refused.
Connecting to localhost|127.0.0.1|:8081... connected.
HTTP request sent, awaiting response... 200 OK
Length: 28222 (28K) [text/html]
Saving to: “index.html.1”

100%[===========================================================================================================================================================================>] 28,222 --.-K/s in 0s

2020-02-26 15:54:15 (323 MB/s) - “index.html.1” saved [28222/28222]

[root@coreSA ~]#