On Mon, May 24, 2004 at 10:25:33PM +1200, Phillip Hutchings wrote:[bigger snip]Yeah, I'm looking at it, but there's no decent way to detect freenet packets.
That's a feature :).
Yeah, even on localhost :P IPTABLE's OWNER match target only works in the OUTPUT chain. I can't monitor something coming in, but that's an IPTABLES problem :P
I was looking at patching the source so you could specify the
source port range for outgoing connections. If you specified 10 ports
or so and freenet bound them on startup so they were captured then, and
used iptables to MARK the packets you could do some really decent
limiting.
[snip]
Domestically I am willing to give up to 5k/sec out and 15k/sec in (due
to my connection speeds), internationally I would go lower but monitor
the usage. I'd like to cut off after ~100MB/day. I know this is
sub-optimal for freenet, but with caps that's the reality.
Have you tried averageOutputBandwidth (in the config file)?
I think that's what I have on now, but until my ISPs metering catches up with what I've used I won't be testing. Should be on tomorrow though, I'll report what happens.
One thing that I can think of is limiting the size of incoming files not requested by the node directly - stop splitfiles and things going through. I'm more interested in the information, not movies, but I can't think of a tidy way to implement this in a few minutes. I know it's not really in line with the freenet ideal, and also it could compromise privacy, but it's a thought.
Well, if it was widely supported, it would just result in moviez being split into smaller chunks...
Yeah, I guess so. -- Phillip Hutchings [EMAIL PROTECTED] http://www.sitharus.com/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
