posted by
emperor at 07:01pm on 30/06/2008
We have an open wireless access point, which allows anyone to get to the outside world (only some ports, most especially not SMTP), as a matter of policy (such things are useful, IMO, and so running one is a good thing).
Sadly, it seems someone (presumably one of the near neighbours), which I guess means next-door in the semi (as the other way is away currently) is making extensive use of our wireless during the chargable period - we've used 1.38G chargable this month, compared to an average of about 570M for the previous 3 months. I don't think we want to start paying extra for others to use our wireless internet.
I can see a few options:
i) turn the wireless off during chargable hours (except on days when someone is working at home)
ii) rate-limit the wireless to 512K/s (with some baroque
iii) redirect all web-traffic to a stunt webserver that puts up a page saying "you're running up our bandwidth costs - please email
emperor if you want to carry on doing this"
iv) assume my guess is right and go and talk to the neighbours
I'm not interested in playing games like redirecting them to goatse or inverting their images or any of that sort of thing.
Sadly, it seems someone (presumably one of the near neighbours), which I guess means next-door in the semi (as the other way is away currently) is making extensive use of our wireless during the chargable period - we've used 1.38G chargable this month, compared to an average of about 570M for the previous 3 months. I don't think we want to start paying extra for others to use our wireless internet.
I can see a few options:
i) turn the wireless off during chargable hours (except on days when someone is working at home)
ii) rate-limit the wireless to 512K/s (with some baroque
tc runes?) during charging hoursiii) redirect all web-traffic to a stunt webserver that puts up a page saying "you're running up our bandwidth costs - please email
iv) assume my guess is right and go and talk to the neighbours
I'm not interested in playing games like redirecting them to goatse or inverting their images or any of that sort of thing.
(no subject)
(no subject)
(no subject)
To maintain your policy, you could set up some sort of traffic shaper which severely limits access for people who haven't logged on to it or devices not on the "friendly" MAC list or somesuch. The problem is already solved; the likes of BT OpenZone let you only connect to the pay-us page. You'd want something slightly different like a punitive rate- or bandwidth-limit for unknown devices coupled with a welcome page saying "hi, this is our wireless, we're making it available as a public service, it's rate-limited, if you want to make nontrivial use of it contact [...]"
(no subject)
(no subject)
If you don't think the neighbours are likely to take kindly to it I'd do a combination of i and iii.
(no subject)
If that all sounds like too much effort, then the other approach is just to secure the thing. That's what I do.
(no subject)
(no subject)
(no subject)
OK, the risk is small, but the consequences are dire.
(no subject)
(no subject)
It's probably even more valid with 42 days rules.
(no subject)
English law still overwhelmingly works the other way around.
(S)
(no subject)
(no subject)
(no subject)
(no subject)
I think you need to be clearer here about what you're trying to achieve. Because if you start switching it off, you're no longer providing that open access. And I'm not sure that just talking to your neighbours is going to stop them. Seems to me there's only two reasons why a neighbour would use your signal (deliberately) - either so you pay for *all* their surfing or so that they can do all the surfing on your account that they don't want tracking back easily to their own, whether for reasons of legality, cost or whatever.
I'd go for (ii) if you're determined to leave it unsecured.
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
[1] On this particular AP.
(no subject)
you could set the numbers so that visitors are fine, but anyone using it for more than a polite period would find it getting slower and sssllloooooowwer
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
Open wireless is a good thing for a variety of reasons, practical and political ones among them, and you should arrange things so that you like the balance between the cost to you and the general benefit.
(S)
(no subject)
When I'm at Ma's, I can sometimes get a very weak signal that's barely sufficient to get email, but I feel bad about using someone's unsecured network.
(no subject)
(no subject)
(no subject)
I think Bridget may have had some difficulty with her EEE.
Our main 'problem' is that my brother uses massive amounts of bandwidth, and needs occasional reminding to stay in the non-chargeable period. On the other hand, the ISP allowed us to set up a 'PAYG' option so if we go over our limit, they just charge us a bit more at not extortionate rates. And what he costs us occasionally in ISP, he more than makes up for in childminding and gardening.
(no subject)
(no subject)
Kill them all.
(no subject)
I'm broadly in favour of leaving wireless access open, at least until the law trips even further towards "guilty until proven innocent". (Our own wireless network is secured, because that's
(no subject)
I'd either lock it down, or rate limit any traffic from unknown hosts to something really painful for anything more than a quick terminal session, 28k8 is probably about right.
(no subject)
A friend of mine got a lot of gnutella-ish packets slowing his unsecured wireless, and changed the essid of the network to no-gnutella-please, which apparently solved the problem. I think it rather depends how much they know what they're doing, whether something simple like "oy, we've noticed, please don't" works, or not.