I don't understand.
You are asking for a ping
ping 192.168.102.116 to a private address in the range
192.168.x.y which is an address in one of the RFC1918 block addresses. All the addresses in a RFC1918 block should be discarded by any internet public router (such addresses are not routable).
The answer you get back comes from a public internet address
From 188.8.131.52 which belongs to:
$ whois 184.108.40.206
NetRange: 220.127.116.11 - 18.104.22.168
Organization: Wayne County Community College (WCCC-3)
That should not happen.
Futhermore, you are getting a public route
Redirect Host(New nexthop: 22.214.171.124) as the best route for an internal address. That answer is asking to add a new route to the local routing table.
That should be forbidden
Understand that there is no routing entry in the (local computer) route table for the local address range
192.168.x.y. As there is no routing entry, the packet gets sent to the default gateway
default 10.10.2.1. That router sends the packet to the next router. If the next router in in the internet cloud then this router is a "border router" and should not route packets in private ranges from RFC1918 to the wide internet.
In any case, there are at least this problems in your setup:
- There is no route for the address range in your route table.
- The router at
10.10.2.1 (or any other border router) does not have an specific route for
192.168.x.y. It should.
- Packets from
192.168.x.y are being routed to the internet (ping request).
- Packets to
192.168.x.y are being routed back from the internet (ping answer).
- You are scanning a VM at
192.168.102.116. I believe that being a VM the packets should not even be sent to the local network (and then to the internet). This packets should be controlled (contained) by the VM virtual network interface.
Could you clarify?
Quoting RFC 792 (Internet Protocol).
The gateway sends a redirect message to a host in the following
situation. A gateway, G1, receives an internet datagram from a
host on a network to which the gateway is attached. The gateway,
G1, checks its routing table and obtains the address of the next
gateway, G2, on the route to the datagram's internet destination
network, X. If G2 and the host identified by the internet source
address of the datagram are on the same network, a redirect
message is sent to the host. The redirect message advises the
host to send its traffic for network X directly to gateway G2 as
this is a shorter path to the destination. The gateway forwards
the original datagram's data to its internet destination.
In this case, G1 is 10.10.2.1 (eth1:0 above), X is 192.168.102.116 and G2 seems to be 126.96.36.199, and the source is in range (you did not say) 10.10.2.0/16 (i.e. G2 and the host identified by the internet source address of the datagram are clearly NOT on the same network)