Caveats In Reselling DSL Bandwidth To Neighbors? 383
chrisleetn writes "I'm contemplating getting Slashdot (Speakeasy) 6Mbps broadband or something similar and offering wireless internet access to my neighborhood. Speakeasy even has a plan to allow this. What should I be aware of as far as legal/business/regulatory implications? I know I need to restrict obvious illegal stuff and probably p2p to be safe, but is the local cable modem company going to come after me for competing with them? Has anyone done this who can offer some insight?"
This Is Rather Simple (Score:5, Informative)
Alright, so you not going to be an illicit reseller, but an authorized body capable of forming a legal binding agreements with your customers.
ISP's do this all the time... they simple resell bandwidth they have purchased from their providers.
Basically, write out what services you will provide and clearly define what you won't allow. It needs to be clearly written and agreed upon by your clients.
After that, you simply need to track ip addresses (assumming DHCP will be in iuse), keep mail logs (if you provide smtp/pop service) and generally ensure that you can track illicit activity back to the source if requested to do so by a court order.
It's simply a matter of accountability and this is something you can easily do given it is a service you can provide.
Anything else is just extra, but it would probably be a good idea to track bandwidth usage.
Re:This Is Rather Simple (Score:1, Informative)
No Way (Score:5, Informative)
Points to consider (Score:5, Informative)
Charging lets you assign value to your service, and assigning value is a key way to keep customers in line while covering your nut.
In terms of the cable modem companies "coming after you," you need only worry about legal competition -- no franchise agreements come to mind that completely lock out all broadband competition. It's worth noting, however, that Verizon has backed legislation in Pennsylvania to prevent municipalities from setting up free broadband services -- a bad step in the direction of market control.
If you *are* going to charge, then you've got some additional costs to consider:
Good luck!
RTFA, Idiot (Score:3, Informative)
The article isn't even about the cable modem company, its about DSL (the submitter was wondering if the Cable Co. would come after him for competing with them, which makes you and the grandparent twice the idiot)
Legal Issues (Score:4, Informative)
Re:Why would the cable modem company come after yo (Score:5, Informative)
Accountability and risk (Score:3, Informative)
I am doing this exact thing, except I'm in Sweden. I do not block things like P2P but I do use keyword based filtering through a proxy if the client requests this (usually if it's family computer where they want to keep the kids from visiting Goatse.cx,
Anyway, I'm no legal expert but I would think it'd help to keep the logs from Squid so you can account for who visited what and when. That way, you can always identify the person responsible if it ever comes to that.
I would not worry about your local ISP coming after you for stealing some of their potential customers as long as _your_ deal with _your_ ISP says that you can share your connection with others.
Oh, one more thing... You might want to looking into putting a contract together for your customers / friends who'll be using your line. You could basically ensure that _they_ are infact resposible for what they're doing on your xDSL.
Re:ianal but.. (Score:5, Informative)
Speakeasy handles the billing and credits your account, you just provide the wireless setup. People need to read about Speakeasy's WiFi Netshare Program [speakeasy.net] before assuming stuff.
Re:Is it really worth the trouble? (Score:4, Informative)
Let's see
But yeah
At a minimum, he will most certainly need some way to implement bandwidth caps. Otherwise I guarantee little Tommy next door will hog the whole proceedings downloading by Britney Spears' latest video, or all seven seasons of Stargate SG-1.
This endeavor will probably end up being more trouble than it is really worth, but if the guy gets a kick out of it
Unlikely to be legal (Score:4, Informative)
At least here in Australia if you provide communication services which cross a property boundary then you have to be a licensed telecommunications carrier.
I believe that in NZ this is not a difficult thing to do (about as hard as applying for a passport) but the Australian Government is not fond of the idea of administring millions of telecommunication carriers, and has made the process much more difficult.
I think if you dig deeper in your juristiction you will find that similar rules apply. Remember all the regulations which apply to carriers: having to provide wiretap facilities, etc. Legally, this could be quite messy
Re:Why would the cable modem company come after yo (Score:5, Informative)
Speakeasy even has a plan to allow this.
Forbidden in Spain (Score:2, Informative)
In fact, some small villages had made a public wireless net, so everybody could use internet (we're talking of tiny villages with no access to broadband etc), and they were denounced by some stupid "teleccomunication comission"
The new gobernment told them that they shouldn't have denounced those villages since they were trying to spread internet's access but well...the point is: we have some law that forbids it
Re:Here's an idea (Score:1, Informative)
http://duxcw.com/faq/network/outside.htm
Daveats (Score:5, Informative)
2. Triple check that the AUP for your DSL allows you to share and resell the service. Then check again.
3. If you are reselling, you will probably have to charge for sales tax, check your local tax authority.
4. There are probably FCC rules about the equipment that you can use and the maximum power that it can irradiate. Of course, if you are using turnkey COTS equipment, the odds are that it is FCC legit.
5. Check your neighbors and see what is the interest in this kind of service. If there is too little interest then you are setting yourself for failure, since your location is fixed and there is only so far you can reach.
6. Write your own AUP and make sure the CYA provisions are in bold, plain english a second grader can understand. Then take the AUP to a lawyer to read and see if he can poke holes thru it.
7. Be prepared for the technical support burden, even if most of your customers are geeks.
I know I need to restrict obvious illegal stuff an (Score:4, Informative)
Re:This Is Rather Simple (Score:3, Informative)
The original poster already said "Speakeasy even has a plan to allow this." He didn't provide a link for it, but apparently they will do the billing for him [speakeasy.net] and surprisingly enough they will even allow him to set his own price [speakeasy.net]. It seems to be a really good move on the part of Speakeasy to do this.
Re:... but the upload sucks (Score:3, Informative)
You might figure "hey, whatever, I have 800 up and X megs down, even if one user eats 400 up there's still plenty of bandwidth to go around." That's totally logical in terms of resource allocation, but DSL doesn't work that way: according to Verizon (who had to explain to me why my I wasn't getting my promised bandwidth) half your upload bandwidth is half your bandwidth period. That's why Bittorrent drags so badly on DSL unless you cap the upload with CarraFix or something of that nature. So far as I understand it, this is standard practice for the DSL industry.
So my advice to you is, if possible, share some other sort of connection, because DSL doesn't lend itself to this very well. If that's not possible, just be very clear with all your neighbors before asking them to chip in that this is primarily a down-only network and that upload-intensive activities like Bittorrent or freelance web development won't fly. You can compromise a bit by setting rules. At my last apartment with a shared DSL line, we all agreed that you had to take it easy on bandwidth durring the day so people could work, but that you could do whatever at night. That worked out OK. If you're feeling frisky no doubt you could configure a server or routing device to do this for you, but I lack that sort of expertise and initiative. Sharing broadband is a cool way to do something nice for your neighbors by letting people (including you) get fast web access on the cheap, but if you intend to furnish a connection for any sort of bandwidth-intensive activities, look away from DSL.
Re:Does sharing cableTV hold true for bandwidth? (Score:4, Informative)
When I tell you to take money from my wallet, it's not stealing; without permission you go to jail.
Re:You need a captive portal! (Score:4, Informative)
I've been doing this for years... (Score:2, Informative)
The DSL connection is shared among 4 apartments, plus my own. Instead of sharing out the bill into monthly payments, I ask the neighbors to pay the entire bill in the round-robin fashion - i.e. they only have to do it once every 5 months.
I operate on an honor system, with a wide-open network. If I notice a new MAC address in the logs (ok, a script does it for me) for more then a week, the next time its user will be presented with a friendly page asking to contribute to the coop and an email address to communicate to me. If no email ensues for a week but the user keeps logging in, the MAC address gets shut off.
This arrangement reasonably handles visitors and temporary users, but restricts freeriding (I've only had to shut off a user once - and then he joined the co-op and now pays his bill on time)
Also, make sure you firewall your private network from the wireless network, and the wireless network from the outside world. People bring in virus-infested laptops onto my wireless net all the time; one NetSky infection was enough for me to go get a second firewall.
Finally, regarding 7am calls to fix the network: all network equipment sits on a UPS and is connected to a little gizmo I picked up on SmartHome.com that lets me turn things on and off from a touch-tone phone. Now if somebody complains of an outage (90% of the time - due to hung DSL modem or primary router - fixed by rebooting), I simply reboot the entire set with my phone and later ping-check it.
I use commodity off-the-shelf routers (Linksys) and access points (D-Link Range Extenders); they are reliable if you don't let them overheat. I usually keep at least 1 spare unit of each kind for a quick replacement (I got 10 D-Links at a fire-sale price, so I'm set for a long long time).
Result: I have a virtually no-headache setup. No moving parts (logs are checked remotely by a linux box), no expensive hardware. I get 4-5 incidents of downtime per year, tops - and most are fixed before I even get a phone call from a user.
I wish the idiots would shut up. (Score:5, Informative)
To answer the question, here are some pointers from somebody who is actually doing Speakeasy NetShare.
You do not need to worry (from a layman's viewpoint, IANAL, so check with your family attorney if you are worried) about filtering access. In fact, if you read the fine print of Speakeasy's documentation, you are not really permitted to do so. I was told specifically by a Speakeasy rep NOT to do this, even though I had the ability to.
Since Speakeasy will provide you with an IP address specifically for that customer, it will be easy (should fit hit the shan) to segregate your traffic from theirs. Speakeasy will be billing them seperately, so they will have their address and contact information should the RIAA/MPAA/LE come around. From a legal perspective (again, IANAL), you are no different than your local phone company.. you are only providing a conduit, passively, between the ISP (Speakeasy) and that ISP's customers (your neighbor using NetShare).
Over here, I have three specific ways of getting access. You can be plugged in to my personal LAN (which, BTW, is hardline). You can be accessing a free and open node (which runs NoCat), which is highly filtered and proxied. Or, you can be on the WPAd side of the house, which is the resale network.
Don't hesitate to participate in NetShare. It's an awesome way of reducing your monthly bill AND helping your less tech-savvy neighbors to get off AOL. Both are very worthy causes.
Be very careful of blocking anything (Score:4, Informative)
It does seem to be okay to do things like rate-limit people, or traffic shape so as to prevent one person from DoSing another, and probably to block forged IP addresses (if your ISP doesn't do that already).
However, I think you're in for a world of pain with the RIAA if you assume responsibility for making sure your neighbors don't violate copyright. Sure, you might be able to block P2P traffic, but who knows what other things they'll go after people for in the future. Maybe your neighbor will put up a web page on how to de-copy-protect CDs, and the RIAA will decide this caused them $500,000,000 of damage. Do you really want to be responsible for that?
Do some google searches for "prodigy case". And definitely don't try to institute any kind of blocking without first consulting a lawyer.
Have them sign a contract (Score:3, Informative)
so you are not liable for their crimes. There is no way for you to compose some magic AI that can detect illegal pornography, so all you can do is make sure everything is in writing with their signatures.
they might be able to harrass you legally (Score:3, Informative)
The only direct complaint your cable company might have is if you are laying wire in a way that interferes with their franchise agreement. For example, if you lay coax cable between you and your neighbors's house, particularly if it crosses a cable-company easement, it could be a problem.
If you are doing it wireless using unregulated spectrum, the only way they could shut you down is to get the city to go after you for violating domestic-business laws. This is particularly true if you advertise your business.
Another tack they might try is to get with the RIAA or MPAA and harrass you for copyright infringement every time your neighbors download a song illegally. After you get swamped with enough subpeonas, you may say "this isn't worth the hassle."
PS: Don't forget to comply with IRS rules on business and self-employment taxes.
Re:RTFA, Idiot (Score:5, Informative)
The caveat here is *you* are the business - which means if someone wants to sue "the provider", they would be suing YOU, and anything you own is fair game in said lawsuit.
There's limits to this (Score:3, Informative)
Basically, a contract that attempts to regulate what is the FCC's exclusive jurisdiction is probably unenforceable.
Here's what a greedy ISP CAN do:
If an wire-based ISP has a sweetheart deal with an apartment building and they want to lock out WAPs, they can jam those frequencies. It's deregulated and AFAIK there's nothing that can stop them as long as they keep the power level down.
Related Slashdot stories:
University Bans Wireless Access Points [slashdot.org] Sept. 09, 2004
UTD Lifts Ban On WiFi Equipment [slashdot.org] Sept. 18, 2004
DO restrict port 25 though (Score:2, Informative)
The last thing you want is for one of your non-tech-savvy downsteam customers to get a virus, get you labeled a spammer, AND choke everyone's bandwidth.
Re:RTFA, Idiot - shush ye.. sssh.. calm down buddy (Score:4, Informative)
Math is your friend (Score:4, Informative)
Re:not OT, but sorta related (Score:4, Informative)
DOCSIS 1.0 and 1.1 define QAM modulation for your downstream, but only QPSK for your upstream. QPSK is much less sensitive to noise than 64/256 QAM is, but as a result, you get less bits/Hz. Not to mention the cable provider can allocate a hundred or more Mhz per node for downstream, but less than 54 MHz upstream. This is due to legacy reasons, most amplifiers only pass upstream up to 54 MHz.
DOCSIS 2.0 will change things, which should be rolled out in the next few year.
Roofus - Ex Comcast Engineer.
Re:Stay away from speakeasy (Score:4, Informative)
it works here (Score:2, Informative)
Re:RTFA, Idiot (Score:2, Informative)
Re:Stay away from speakeasy (Score:4, Informative)
~Philly
Re:RTFA, Idiot (Score:2, Informative)