> Nope, that's how its managed to evade most filtering > until recently. You have to examine the characteristics > of the packets internally to get an idea where it came from.
Skype is using AES (go belgium), so you can't get much from the packet data I think, unless you're able to analyse the connection setup packets, and change your rules accordingly. Or unless it is indeed a seperate port, or a wrapped, say HTTP header around their data? Any more technical nitty gritty insight? Thanks, mike
