Quote:
Originally Posted by Naydef
- modifying inbound packet - currently you can block packet from the client and use Socket extension to send packet with modified data
|
I don't doubt blocking the packet will work, but I don't think Socket ext is able to send a modified packet from the right source IP and port.
When sending a replacement packet from the client to the server, SrcDS will expect the source IP address to be consistent with that client's - some internet IP, whereas the actual source IP will be SrcDS' localhost. Given that SrcDS distinguishes clients by IP:port data in the packet, I expect the packet would be disregarded. Similarly, to send a modified outbound packet to a client, the socket ext will bind to some port other than SrcDS' port; as such, NAT or not, the client will ignore the packet since it came from the wrong port on albeit the right IP.
I'm not sure what implementation you had in mind when you said that Socket ext could be used to send the modified packet - please clarify.