Why does ss show strange Local/Peer addresses on the SYN-RCV sock with v4mapped addrs?
Issue
- Why does ss show strange Local/Peer addresses on the SYN-RCV sock with v4mapped addrs?
Sample:
web1's ip: 192.168.122.86
[root@web1 /]# grep "^Listen" /etc/httpd/conf/httpd.conf
Listen [::ffff:192.168.122.86]:80
[root@web1 /]# ss -nat | egrep "^State|:80"
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 ::ffff:192.168.122.86:80 :::*
SYN-RECV 0 0 0:0:200:10e5:::80 ::ca25:e230:cb25:e230:58492
SYN-RECV 0 0 ::1.0.0.0:80 ::200:0:300:0:58490
SYN-RECV 0 0 0:0:200:1025:::80 ::bb12:bc99:bc12:bc99:58494
[root@web1 /]# netstat -ant | egrep "Proto|:80"
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 192.168.122.86:80 192.168.122.106:58492 SYN_RECV
tcp 0 0 192.168.122.86:80 192.168.122.106:58490 SYN_RECV
tcp 0 0 192.168.122.86:80 192.168.122.106:58494 SYN_RECV
tcp6 0 0 192.168.122.86:80 :::* LISTEN
[root@web1 /]#
cli1's ip: 192.168.122.106
[root@cli1 /]# telnet 192.168.122.86 80 &
[root@cli1 /]# telnet 192.168.122.86 80 &
[root@cli1 /]# telnet 192.168.122.86 80 &
Environment
- Red Hat Enterprise Linux 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.