Quote:
Originally Posted by BetBlowWhistler
Do you think the situation being investigated by the Police courtesy of Alex might explain it?
---------- Post added at 08:05 ---------- Previous post was at 07:52 ----------
It's worth pointing out to the non technical that the IP packets that everyone refers to has two sections.
1. IP Header
2. Payload
The IP header contains information to allow the packet to traverse the internet. Source IP, Destination IP, protocol type etc.
You should note that the information in this header cannot be used for traffic shaping of http traffic and the like as it would only mention the protocol 'tcp'.
You have to process this packet to 'strip off the outer layer' thus revealing the payload to consist of the following (let's continue with the http example)..
1. TCP Header
2. Payload
The TCP header contains other information for the processing computer so it knows what to do with it and how the packet fits in with other packets. Key fields in this header are the source and destination ports.
Most people will know by now that http runs on tcp/80, and this is all the information you really need to shape this traffic. You could distinguish between ftp, http and bit-torrent traffic at this level assuming everyone is using the standard ports for such protocols.
What DPI does is to look into the payload section which contains information for the application that is listening on the mentioned port, in this case port 80. For the sake of simplicity this is where your personal information is kept and you could also analyse the payload to see if you really are looking at http traffic or if you have disguised a bit-torrent stream on port 80.
My point is, it is nothing like a postcard apart from the fact that the packet isn't encrypted. (With encrypted traffic you would typically only see the IP header information so it can get where it's going).
It is very much like an envelope within an envelope within an envelope.
Anyone wishing to understand further is encouraged to google 'osi 7 layer model' - you should be able to find some general overviews. Even the wiki pages might be understandable  |
I have no idea if this is relevant or not as it is too technical for me - but as a BT customer I now find that the ThinkBroadband speed test on default settings does not give me an accurate reading - generally very very low- I have to rerun it using the port 80 alternative to get a proper result.
And the BT official speedtester has a weird Firefox related fault (for some people, including me, who get a java socket error in the results and the test hangs) that can be overcome by using either IE7 (with same Java) or using our Firefox, putting in the IP address, instead of the url.
These are the sort of problems that BT "investigate" but never seem to be able to solve nowadays.
Might this be in any way connected ? (quite happy to be totally wrong here - please educate me)
---------- Post added at 08:19 ---------- Previous post was at 08:18 ----------
Quote:
Originally Posted by icsys
|
Not sure there is a lot of point as BT being a commercial company and not a public body, won't be required to disclose commercial legal advice. AFAIK