| 55 | | It should look similar to this. Let's check out the source and destination information from the HTTP data packets. We can see that the source is 10.1.4.2, which corresponds to the Alice node IP address, and the destination is 10.1.1.2, which corresponds to the Server1 node's IP address. This makes it clear that Alice was making an HTTP request to Server1. Now open up throughproxy.pcap in Wireshark. What we see is much different, we see that the destination is |
| | 55 | It should look similar to this. Let's check out the source and destination information from the HTTP data packets. We can see that the source is 10.1.4.2, which corresponds to the Alice node IP address, and the destination is 10.1.1.2, which corresponds to the Server1 node's IP address. This makes it clear that Alice was making an HTTP request to Server1. Now open up throughproxy.pcap in Wireshark. |
| | 56 | |
| | 57 | [[Image(wiresharkthroughproxy.png)]] |
| | 58 | |
| | 59 | What we see is much different, we see that the source is 10.1.3.4, which is the IP address of the proxy node. So, now the destination, Server1, doesn't know that the request came from Alice, but instead thinks that the request came from the proxy node. Now, we try it with the throughtor.pcap file. |
| | 60 | |
| | 61 | [[Image(wiresharkthroughtor.png)]] |
| | 62 | |
| | 63 | Again we see that the source is not Alice, but instead matches the IP address from one of the Tor Relay nodes. It won't always be the same every time because the path that the data takes through the Tor network is random. This, like going through the proxy, provides anonymity for the client, in our case Alice, but this provides more anonymity because the data goes through 3 Tor relays instead of just one proxy. |
