>> Moreover - packets must not be dropped! >Sorry for this useless answer, but... How strong is this condition? > I mean, even if you don't drop a packet locally, it can still be > dropped by the target machine, or by one of the routers in between. > You have no influence on that whatsoever, so no matter what you do, > your application must be able to handle dropped packets. No. There are no routers and no any other hosts between server and client machine. There are only ... air and space :) . I talk about sattelite link with 100% qality within fixed bandwidth. In way from server to client only a shaper can drop packets. This programm (client-server) use this characteristic (this and some other) and "accellerate Internet access". But any packet loss entail speed fall and a lot off "land" high-proced traffic. > Does the kernel even know about that? Of course. We use HTB to separate speed between user, and may be logic implemented, that guaranted package delivering to the network adapter. That all we need: do not filter THIS traffic at all - talk about availible "traffic" to userspace programm (using tokens, e.g. or in some other way). _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
