Once the system is upgraded to iputils-20160308-10.el7, the ping6 is failing if the IPv6 address is not configured or is disabled on the interface.2001:xxxx:xxxx:xx::4 ping statistics -Ģ packets transmitted, 2 received, 0% packet loss, time 1001ms When specifying the interface which is not having IPv6 address, ping6 is still working as it is picking the other interface ( ens9) which is having IPv6 address.The firewall has reachability to both of those host IPs and all devices on the inside have the expected access to the Internet (outside) as well as the other assigned zones. 1 is the address assigned to the inside interface. Inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope linkĥ: ens10: mtu 1500 qdisc pfifo_fast state UP qlen 1000 IPv6 address configured on ens9 interface and not on the ens10Ĥ: ens9: mtu 1500 qdisc pfifo_fast state UP qlen 1000.Code fix has been provided and below are the details.
Portal 2 ping tool not assigned upgrade#
Please upgrade the iputils package to at least iputils-20160308-10.el7 This issue has been resolved with the release of RHEL 7.4 and with the upgraded version of iputils package and with the release of the iputils-20160308-10.el7 package as RHBA-2017:1987 ping6 -I was working in RHEL6 but not with RHEL7.ping6 is picking other interfaces when specified particular interface using "-I" option when the IPv6 IP is not configured on it.Ping - ICMP and TCP ping Features: - Request ICMP packets and display ICMP response times. ping6 is able to ping via an interface, even if the interface is not having IPv6 address assigned/configured Ping network tool - a simple but powerful network utility.
0 kommentar(er)
