I think you have every right to be a bit pissed. We as a group, with some member donating large amounts of free time, create a public service for The Greater Good and a half dozen people are abusing it. Since we can't trace the wires back to the offender, there must be a technical solution. Shutting down the node for long term is not really a solution.
However, SCFN like all ISP's has to deal with this issue, so we don't really have to implement a new system, just find out what they are doing and then do it. The problem becomes, how much of the public nodes has to be reworked to fix this problem. I wish I could be at the meeting tonight. This kind of stuff is right up my alley. Steve Shapery wrote: > I guess I wasn't clear in my initial tirade about why I tore down the node. > > In general, I've seen 4-6 people on the node at any given time, > sending email, surfing the web, browsing YouTube, whatever. > > but then within 5 days, I saw none of the regular nodes, and I saw > six new ones online, all doing P2P at the same time. > > different apps, different versions, different servers. > > But they were the only apps I saw live for days at a time. > > I guess the crux of my issue is that they so blatantly abused the > service, and that also I couldn't get the P2P completely blocked, > either through MW or through my Cisco with NBAR. > > but when one runs across people puilling 14 mbit of P2P over ones' > wire, one tends to get irked. > > > -S > > > At 09:33 PM 3/21/2007, you wrote: >> FWIW, we do some bandwidth shaping already. M0n0wall has some built in >> rules to elevate traffic like email and ssh and push down known P2P >> (based chiefly on port numbers), leaving http in the middle. See the >> m0n0wall docs for more details. >> >> Re logging of data, I've heard it every way. You shouldn't keep logs >> because then you can't get into trouble for not providing them, or get >> sued by someone subsequently because you did provide them and shouldn't >> have. You should keep logs so you can be a responsible citizen and help >> the authorities track things down, and also show that it wasn't you. Or >> you should keep logs, but anonymize them sufficiently to show that it >> wasn't you, but you can't tell who it really was. >> >> We briefly toyed with the idea of keeping logs and making them all >> public all the time, but then it was pointed out that they could be used >> by stalkers. Currently we don't keep logs because the donated syslog >> server we were using has died. Before then we used to keep dhcp lease >> logs only. We do have limited logs on the m0n0wall gateways, but they >> expire quickly. Meraki keeps logs, and I don't know exactly what their >> policy is (though now I'll ask!). >> >> Its a fascinating topic (though not to all, as a couple of recent >> unsubscribes suggest!). I'll be happy to continue in person at tomorrow >> night's monthly meeting if anyone who attends is interested. >> http://socalfreenet.org/node/751 >> >> cheers, michael >> -- >> Michael Mee >> 858-531-0735 >> www.socalfreenet.org >> >> _______________________________________________ >> SoCalFreeNet.org General Discussion List >> To unsubscribe, please visit: >> http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org > > > _______________________________________________ > SoCalFreeNet.org General Discussion List > To unsubscribe, please visit: > http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org -- -- Jason Murphy [EMAIL PROTECTED] _______________________________________________ SoCalFreeNet.org General Discussion List To unsubscribe, please visit: http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org
