Is it possible, like with Windows route command, to route TCP traffic destined for other IP addresses back to the PC?
Would it be possible to route selected traffic destined to the gateway back to the PC so that it could be intercepted by a program listening on a socket?
More info: Windows sharing is turned on so the PC can act as a WiFi hotspot. The PC’s other adapter is wired ethernet to a gateway router.
Wireshark shows traffic coming into the wired adapter destined for 130.211.9.161:443. That traffic is from a wireless connected device arriving into the WiFi then being sent by Windows sharing through to the wired NIC. The wireless traffic could be from any wireless device connected, weather station, IP camera, smartTV, etc…, connected to the PC’s WiFi hotspot.
Would it be possible to route the 130.211.9.161 traffic back to the PC so that a program listening on a socket for port 443 could capture the traffic? If so, how might that be expressed in the route command?
TY,
It is technically possible to route TCP traffic destined for other IP addresses back to the PC for interception. However, this cannot be achieved using the Windows route command alone, as it only modifies the system’s routing table to determine the next-hop behavior for IP traffic, without influencing how the traffic is processed once it reaches the system.
arslan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2