Re: Bandwidth throttling question
From: Martin Harvey (Demon account) (martin_at_nospam_pergolesi.demon.co.uk)
Date: 09/15/04
- Next message: Maarten Wiltink: "Re: Sorting of 4 String-Lists"
- Previous message: Stark: "Re: Again on kb_event. It almost works"
- In reply to: Jamie: "Re: Bandwidth throttling question"
- Next in thread: Jamie: "Re: Bandwidth throttling question"
- Reply: Jamie: "Re: Bandwidth throttling question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 15 Sep 2004 17:55:50 GMT
Wrong answer.
Generally: There actually is no real problem at all. The TCP "cwnd"
will do bandwidth sharing for you.
If you want to mess with it properly then there's no effective socket
hook - the correct way to do it is to:
1. Get a linux box.
2. Use it as a router.
3. Recompile the kernel with NistNet in it.
4. Set the bandwidth / drop rules appropriately.
5. If you want, write a client on the PC that plays with the
configuration parameters on the linux box.
I had to do this for some QoS investigations a couple of years back,
and it works great!
See my comments below.
MH.
On Wed, 15 Sep 2004 12:26:20 -0700, Jamie
<jamie_5_not_valid_after_5_Please@charter.net> wrote:
>the only way that i know of this is to place write some
>firewall code which in turn uses the functions in the
>winsock to hook the socket calls.
Please - if you're going to give advice, could you at least point the
guy in the right direction - his following up your suggestion is
likely to waste a great deal of his time.
a) Firewalls operate at the bottom of the stack (just below the IP
layer), not the top.
b) Winsock hooks operate on the API call level, not on the packet
level.
MH.
- Next message: Maarten Wiltink: "Re: Sorting of 4 String-Lists"
- Previous message: Stark: "Re: Again on kb_event. It almost works"
- In reply to: Jamie: "Re: Bandwidth throttling question"
- Next in thread: Jamie: "Re: Bandwidth throttling question"
- Reply: Jamie: "Re: Bandwidth throttling question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]