On Sat, 2004-04-17 at 17:56, Andy Furniss wrote:
> jamal wrote:
> > I think i am almost understanding you now. Your main concern is people
> > using bittorrent to upload to you, correct?
> > Is there a way to recognize packets going to/from bittorent?
> Quite possibly (though I think it uses connmark which I can't use as I
> use connbytes to get new tcps out of slowstart).
You are speaking Inuit to me. What is connmark? and what is the relation
to tcp slowstart.
> I also sometimes use wget and I've seen posts on LARTC from people who
> use squid and need to solve the same problem.
I am gonna assume that you have some way to recognize the flows destined
to localhost which you want to punish.
> >>ppp0 one dynamic real IP -> gateway PC -> eth0 -> LAN 192.168.0.0/24
> >> |
> >> -> local process.
> > Ok good. Assuming you have attached your HTB etc on one or more dummy
> > devices.
> > - The third path is packets that come in from ppp0, get demasquareded,
> > then have to either go a) to the LAN/eth0 or b)localhost bittorent
> > process. You want to restrict b)
> Well not just restrict - dynamically share per IP total incoming
> bandwidth with LAN traffic using HTB.
Sure - thats assumed since you attach HTB to the dummy device.
To accomodate your need for b), the idea would be as follows:
packet gets demasquared, mark it with a fwmark based on some recognition
you have for bittorent or squid and lastly policy route it to the dummy
device based on fwmark (since routing happens last).
I will need to modify the dummy to not drop such packets which are