Quote:
|
Originally Posted by Ignition
Quote:
|
Originally Posted by ian@huth
When a PC makes a request for information the request has to tell the target where to send the response. Packet inspection can determine the address of the originating request. Monitoring data to and from a specific account can therefore determine how many different devices are connected to that account during the period of monitoring.
|
Nope, don't mean to seem rude Ian but saying that demonstrates you've no idea how NAT works.
The device doing the NAT rewrites the headers containing source address, replacing them with its' own address, to do otherwise would be impossible (IE how is a device on the other side of the internet supposed to know how to get to your private network without a public IP address?) and remembers what to send where by holding a state table of what packets are sourced from where and their destination.
Also to check on source address doesn't require packet inspection just the normal headers inspection that is done by all layer 3 routing devices. |
I tried to give a very simplistic explanation and in it used the word packet to include all data sent with the packet. You must admit that the target has to know how to get to the ultimate destination address in order to reply to it. The fact that the ultimate destination address within the stub domain is hidden by the address translation table in the router makes it difficult, but not impossible, to discover. Just how this is done has security implications that should not be discussed.