Two results are as follows
Ping 192.168.2.59
PING 192.168.2.59 (192.168.2.59) 56 (84) bytes of data.
Ping - R 192.168.2.59
PING 192.168.2.59 (192.168.2.59) 56 (124) bytes of data.
64 bytes from 192.168.2.59: icmp_seq=1 TTL=63 time=9.66 ms
RR: 192.168.5.83
192.168.2.1
192.168.2.59
192.168.2.59
192.168.5.1
192.168.5.83
64 bytes from 192.168.2.59: icmp_seq=2 TTL=63 time=8.30 ms (same route)
64 bytes from 192.168.2.59: icmp_seq=3 TTL=63 time=8.40 ms (same route)
Routing information is as follows:
The route - n
The Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.5.1 0.0.0.0 UG 0 0 0 eno1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eno1
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0 eno1
CodePudding user response:
Speculation should be the cause of the firewall, because when you ping - R packets through a router is a router with the routing information, at this time of the IP packet length of baotou, it is not ordinary package 20, may the firewall to this kind of bag did not judge processing mechanism, data packets can be smoothly delivered to each other, each other can give response,CodePudding user response: