Spud1200
Fully Optimized
- Messages
- 2,556
- Location
- England, UK
I've been thinking about this in depth as In VPN's . I know I have a fasination with them lately and have been asking a lot about them but I've been doing a Shed load of reserch in too them and this is the map I had been given as to their functionality.
Thats pretty straight forward with the likes of IP Address Changes and encryption running on the line what I know is encrypted at my terminal and IP Address changed at my terminal.
But what about DATA Packets. If an ISP is going to sniff a DATA Packet to their best ability, I've read some were that a DATA packet will double in length every transmission.
So 512 becomes 1024 ect:
But how does this work in the real world. If I send a request for a Web Page to my the google servers. Ultimately it has to fetch the load from Google and be bounced around multiple systems so if a DATA Load is fetched from Google threw my VPN Provider then my ISP, back threw my network and in to my system were as the Key Headers are decrypted and the information is displayed I'm thinking originally when the request is made it self on a encrypted network their has got to be constant communication with the ISP so I was thinking this this.
My Computer. (I.P Address Changed - DATA Encrypted)
Information gets pushed out to ISP
ISP (Information gets pushed back to My Computer to confirm Packet)
My Computer (Information gets checked somehow then DATA Packet is confirmed and doubled)
VPN Provider (Changed I.P Address and Exit of DATA is channelled to say Germany)
My Computer (Information gets checked somehow then DATA Packet is confirmed and doubled
WWW (Google receives Packet and sends back confirmation and packet doubles.)
And again this in reverse.
I know their is a constant checking for the DATA Packet integrity but with this doubling every stage is this " ^^ " what I'm thinking correct.
This will operate on the lower layers of the OSI Model I'm thinking.
- My Computer.
- My Network.
- My ISP.
- VPN Provider.
- WWW.
- VPN Provider
- My ISP
- My Network
- My Computer.
Thats pretty straight forward with the likes of IP Address Changes and encryption running on the line what I know is encrypted at my terminal and IP Address changed at my terminal.
But what about DATA Packets. If an ISP is going to sniff a DATA Packet to their best ability, I've read some were that a DATA packet will double in length every transmission.
So 512 becomes 1024 ect:
But how does this work in the real world. If I send a request for a Web Page to my the google servers. Ultimately it has to fetch the load from Google and be bounced around multiple systems so if a DATA Load is fetched from Google threw my VPN Provider then my ISP, back threw my network and in to my system were as the Key Headers are decrypted and the information is displayed I'm thinking originally when the request is made it self on a encrypted network their has got to be constant communication with the ISP so I was thinking this this.
My Computer. (I.P Address Changed - DATA Encrypted)
Information gets pushed out to ISP
ISP (Information gets pushed back to My Computer to confirm Packet)
My Computer (Information gets checked somehow then DATA Packet is confirmed and doubled)
VPN Provider (Changed I.P Address and Exit of DATA is channelled to say Germany)
My Computer (Information gets checked somehow then DATA Packet is confirmed and doubled
WWW (Google receives Packet and sends back confirmation and packet doubles.)
And again this in reverse.
I know their is a constant checking for the DATA Packet integrity but with this doubling every stage is this " ^^ " what I'm thinking correct.
This will operate on the lower layers of the OSI Model I'm thinking.