Ads by TechWords
Subscribe to our e-mail newsletters
For more info on a specific newsletter, click the title. Details will be displayed in a new window.
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
More E-Mail Newsletters 
Joyce Carpenter's picture
Joyce Carpenter

Philosophy of Technology

Open wireless. Oh my.

Rate this
Rated +1
1313 Votes

I have an open wireless at my house. Now I learn what good company I'm in. If it's good enough for Bruce Schneier, it's good enough for me. Our reasoning is a little different, though, and his is easier to use.

Whenever I talk or write about my own security setup, the one thing that surprises people -- and attracts the most criticism -- is the fact that I run an open wireless network at home. There's no password. There's no encryption. Anyone with wireless capability who can see my network can use it to access the internet.

To me, it's basic politeness. Providing internet access to guests is kind of like providing heat and electricity, or a hot cup of tea.

I don't have a DHCP server running, so anyone who wants to use my wireless needs to configure a static address on the correct subnet. I'm happy to do this for guests who don't know how, but drive-bys are strictly on the do-it-yourself system.

I figure both my local network (the wired and the wireless parts) and the various machines are as secure as I need them to be. Traffic is encrypted from the browser or via my vpn, and machines are locked down with firewalls. If I'd use my machine at the local watering hole, I see no reason to suspect that it's less safe at home. As for my neighbors using my bandwidth, I hope they'll return the favor if my router craps out.

See Also:

IT Blogwatch:  Leech my wi-fi? No way! (and messy rack)

 

What People Are Saying

Rate this
Rated +23
1295 Votes

Why not?

Good questions, but I wasn't really trying to accomplish anything in particular. I have a Linux server functioning as a Web Server, firewall and router with NAT enabled. I didn't set it up as a DHCP server, because I started out with two machines on a wired network behind it. I just gave them addresses on the private subnet & walked away.

Then I plugged in a wireless router and added one wireless node. It was easier to give that node an IP than set up DHCP. And on it went. Now I am where I am.

I think I should probably redo the whole setup. But I haven't gotten to it, and I don't really feel any great need to do so.

I should mention that where I live, only chip monks and coyotes are likely to be listening to any traffic. Also, there's very little traffic within the network. Most sensitive traffic is through VPNs and is, therefore, encrypted.

Rate this
Rated +3
1281 Votes

What's the purpose?

Your setup seems a bit pointless. You don't really have an open network, because strangers cannot use it. Since all your traffic is unencrypted, they can still read everything you send across your network in the clear. If you don't want to make your network open to strangers, why leave it in a state where they can read the traffic?

I also agree that having to mess with TCP/IP settings is way more of a pain than using WEP or WPA.

Rate this
Rated -4
1234 Votes

What are you trying to achieve?

I have no problem with running an open wireless network, but I do query what it is that you're trying to achieve by doing so?

If as I presume from your article it's to reduce the administrative burden of connecting devices (both your own and guests) to the network, I think the two choices are:

1, what you're currently doing: No key for access; have to specify network settings, or
2) simple (or blank, is this possible?) key for access; DHCP.

In my book, entering a single word when prompted is leagues easier than spelunking through TCP/IP settings.