IMHO, if the user *wants* an all inclusive service then offer it so long
as you're going to still make a profit.
On the other hand if you explicitly state that you don't and are never
going to allow torrent traffic on your networks then that's your choice
and customers sign up know that's the case.
As an example, these guys aren't an ISP but I know webbynode (vps
provider) will simply terminate accounts that are detected doing P2P
traffic with no questions asked, as it's clearly marked in their
contract terms.
It's really a case of what you want to allow/support and if you can find
customers who are happy with your decisions.
Personally I don't like *blocking* anything on my network as it causes
issues for users who don't understand why things are blocked.. I don't
however have any problem prioritising traffic and <plug> Butch's QoS
setup works great for us. </end plug>
Regards,
Andrew
Josh Luthman wrote:
It doesn't make sense to simply disallow it - offer a bandwidth plan
that makes you both happy. If you can't resolve it then he has
another ISP. Let them deal with the problem.
If he pays for 1 meg and does it all the time we both know that's the
kind of customer that kills your profit and therefor your business.
You and I are WISPs to make money and serve the area - this can't be
done when someone is paying 25/mo and ruining it for everyone.
On 2/13/10, Jeromie Reeves <[email protected]> wrote:
I block anything MT says is a torrent. Life is much better. Mostly, it
is the people who can not figure out how to make it work who have no
understanding of what it does to networks, thus breaking things more
often. The others, get the game, that if it becomes something that I
notice then they will find them selves with 5mbit http, and 64kbit
every thing else for a few weeks.
On Sat, Feb 13, 2010 at 8:07 PM, RickG <[email protected]> wrote:
I truly appreciate everyones feedback on this. Even though it is in
our AUP & TOS, the customer is now admits using torrents and plans to
continue doing so. I want to be fair in all matters. Am I being over
zealous on not allowing torrents? Who here allows or disallows them?
-RickG
On Sat, Feb 13, 2010 at 10:26 PM, Butch Evans <[email protected]>
wrote:
On Sat, 2010-02-13 at 20:14 -0500, RickG wrote:
Ya, I figured it wont catch them all. I'm just wondering about false
positives.
One reason MT is only "so-so" at catching P2P is that they are VERY
conservative in how they identify it. If they are marking it, then
there is a VERY high percentage probability that it really IS a torrent.
Now, whether it is a "legal" torrent or not is another question.
--
********************************************************************
* Butch Evans * Professional Network Consultation*
* http://www.butchevans.com/ * Network Engineering *
* http://store.wispgear.net/ * Wired or Wireless Networks *
* http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! *
********************************************************************
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20100215/aad7a9da/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
