limit home network bandwidth per node

I didn't want to dig up an extremely old thread, and since search brought back few items in such a regard, i opened new thread. Hope thats cool w/ you guys.

The old thread is: http://www.codeguru.com/forum/archiv.../t-291754.html

My idea is that it would be much easier(sorta) and much more reliable to simply hook windows firewall or QoS packet scheduler(via code cave preferably - assuming a mem patch fails), and simply add a 'sleep(variableRate)' where variableRate = 10ms to ... say 100ms. Wouldn't you guys agree?

I mean windows firewall (assuming it's enabled, of course) must intercept all the packets to determine it's protocol(port) - and thus to determine whether to allow dispatching or not. So, assuming it's so resident in memory, why not hook it and sleep it?

Just an idea I thought I run by all of you gurus. Any comments/suggestions?

I'll go ahead and pull out OllyDebug and see what I can do. will post results if I get any progress, but do let me know if you have any comments/suggestions! I'm flying semi-blind here.

hmm. Has this never been done before? Or is my question confusing perhaps?

Idunno, I think it's an idea that should work. Guess I'll go ahead and give it a try. Usually people are quite opinionated on forums(well, i guess in life in general), but seems very quiet.....

Hi Dcyuri,

The link doesn't work so I don't know what your initial request was.
I can only assume that you would like to intercept and manipulate packets, and if that's the case why hook if you can cook (build your own)?

You can use an existing library like Winpcap http://www.winpcap.org/ ), or API's like LSP, NDIS, etc..

Even that I like your idea (and please do post your findings if you decide to go ahead with it), I wouldn't like to miss the flexibility and extendibility I could gain otherwise.


Good luck
Doron

Ahh my mistake. Clipboard failed me!
Correct link updated above now. It's from the code guru archives here.

And thank you for the reply! I really appreciate your insight here. I do agree, hooking would definitely not be forwards nor backwards compatible, and may work only per O/S sub-build for all I know. I agree, using those API's would be a much better option. I'll go ahead and get started on this, should be alot of fun.
Will post the results once finished. :)
And just for testing purposes, I may try the hook a well, just to see if it pulls through at all. I have a feeling it may be a bit shoddy in reliability.

Thanks again,
Brandon