AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() Maybe we, (W)ISP's that actually want to help Skype traffic to highest QoS leves should ask Skype developers to embed a sort of ´disguise/recognize´ button on each skype. So, does it work on all Skype versions? And how easy can they change the package to avoid us finding it?Ĥ. Is this first package always the same for all Skype versions. How long would it take for Skype to modify their initial ´handshaking´ so your solution won't work any longer?ģ. If we now found an relative easy way of identifying its traffic we can off course prioritize it to grant it a better quality but at the same time it can be used to block it as well. Skype made its protocol hard to catch not to have it easy blocked by ISP's. Or should we do it in the prerouting chain on the local port of the border router (=more powerfull)?Ģ. ![]() We need to filter Skype then before we apply the natting on it? What is your suggestion? In a mixed network with even some old rb112's around should we do this at the client CPE and then give that traffic a TOS marker over the rest of the network? What if several Skype users are behind one NAT firewall? Is Skype not using more info on the subscriber (like src port-IP combination) so several Skype comms can run at the same time from one IP?īut I presume that that is not so important to us. We can use this NAck packet to identify the peers, and mark the connections to that peer (at max 50kbps).ġ. ![]() NAck packet: how does Skype know the public IPĢ Its peer won’t be able to decrypt the message (bad CRC)ģ =) The peer sends a NAck with the public IPĤ Skype updates what it knows about its public IP accordingly ![]()
0 Comments
Read More
Leave a Reply. |