Talk:TCP sequence prediction attack

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by Networking task force (assessed as Low-importance).

Internet

	Internet portal This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InternetWikipedia:WikiProject InternetTemplate:WikiProject InternetInternet
???	This article has not yet received a rating on the project's importance scale.

What about faking socket number

If I understand correctly to fake a TCP packet the attacker needs both the IP address and socket number to be the same as the faked host, and then deals with sequence numbers. The same IP address is easy with NAT, but NAT does not allow the same socket number for different hosts. Otherwise it cannot tell the packet is to which host. How does this fake both IP and socket number? Or does it have to be done by those controlling the routers Sohardtohavename (talk) 20:51, 10 March 2024 (UTC)[reply]