Contributed by jose on from the wep-doesn't-cut-it dept.
"Hello all the OpenBSD SysAdmins!I am currently trying to set up 802.11 wireless network with OpenBSD or probably NetBSD.
Have anyone already set up wireless network with OpenBSD or NetBSD?
If anyone of you especially admins who already have fully working 802.11 wireless network, can you share your experience and give some tips?"
"I'm on a BSD based wireless network right now, but it's a pretty basic setup, nothing suitable for a corporate network. Does anyone want to share their configurations for wireless networks with higher security standards?
- Hardware
- Cost
- Software
- Configuration
- Security
- Availavilities
- Differences in 802.11a, 802.11b, 802.11g
- and etc...
http://www.bsdtoday.com/2001/August/News546.html
Thanks... "
(Comments are closed)
By schubert () on
Comments
By Anonymous Coward () on
I know some don't have the option to do, or support for bridging because the specs have never been released.
In the meanwhile I'm having to do NAT & BiNAT with mine cause of this. :(
By Anonymous Coward () on
By Anonymous Coward () on
By lanshark () alexalmazan@netscape.net on mailto:alexalmazan@netscape.net
To remedy this, I have built a multi interface x86 based machine. Two of these interfaces are Cat 5 friendly, and my third interface is WiFi. Open 3.2 identified my Prism2 Card with no problem whatsoever.
By Anonymous Coward () on
http://www.deadly.org/search.php3?query=wireless
From good ol' Google:
http://www.google.com/search?q=wireless+openbsd+howto
From screaming electron:
http://screamingelectron.org/phpBB2/viewtopic.php?t=34
http://screamingelectron.org/phpBB2/viewtopic.php?t=20
By Anonymous Coward () on
If you want to know the differences, then do some homework.
By deekayen () on http://openbsddiary.org/
I'm in college, and neither my campus nor my friend's campus have WEP enabled so people have open access to the network.
So there are lots of different configuations, with buts attached.
If you only give DHCP addresses to people that have their MAC registered with an office somewhere, that keeps a lot of people off the network, but obviously anyone smart enough to set one staticly is going to get on the network.
You could enable WEP only and that would keep even more people out, but if you had someone walk in with AirSnort, that solution is out the window.
The best combination I've seen is to register MACs for staticly assigned DHCP addresses and use WEP, IPSec, and authpf for redundant authentication. That still won't stop someone from DoSing your network with AirJack (http://802.11ninja.net) or Fake AP (http://www.blackalchemy.to/Projects/fakeap/fake-ap.html).
The idea on my campus is to leave the wireless access completely open. It takes all the fun and challenge out of trying to break into the network. We don't have much to hide that's not already behind its own firewall. My friend's campus uses a web based authentication (enter email on a local webserver and leave window open). Only people that know they have to authenticate can get on. It's just a small prevention against wardriving.
Other than that, I've been happy with Cisco equipment. Just don't upgrade the firmware on cards because the obsd 3.1 kernel doesn't have support for new firmware versions. $200 a card to get Cisco client equipment. I can't vouch for any other hardware.
Comments
By Anonymous Coward () on
Comments
By deekayen () on http://openbsddiary.org/
Comments
By Anonymous Coward () on
Comments
By deekayen () on http://openbsddiary.org/
By Anonymous Coward () on
Comments
By Alex () alex@wnc.or.at on mailto:alex@wnc.or.at
By Anonymous Coward () on
Comments
By click46 () click46@operamail.com on www.genmay.net
I have a sinking feeling the editorial staff here at deadly is scarficing quality for quantity. at least thats the impression I've been getting lately.
Comments
By Anonymous Coward () on
If you are not happy about this forum, just piss off or stop posting things nothing to do with OpenBSD.
AMEN
By Anonymous Coward () on
By Patrick Myers () patrick@myers.net on mailto:patrick@myers.net
I started the IPSec thread on screaming electron mentioned earlier and I'll cross post this there later today. Though I haven't gotten to IPSec yet (been distracted), here's what I've put together about just getting stuff set up.
http://www.idiotblocks.com/patrick.myers.net/how-tos/index.php
It is by no means exhaustive and as always, YMMV.
Comments
By Patrick Myers () patrick@myers.net on http://patrick.myers.net
Wireless HowTo is in the, *duh*, how-tos section.
By Philip Munts () phil@munts.net on mailto:phil@munts.net
had uniformly bad experiences with different wireless routers (they all seem need to be power
cycled periodically). I now use cheaper WAP's
(Wireless Access Points) connected to dedicated
NIC's in each OpenBSD firewall box. I feel like I
I get better routing granularity using pf rather
than the dedicated routers anyway.
Comments
By Arrigo Triulzi () on http://www.alchemistowl.org/~arrigo
By Anonymous Coward () on
Comments
By Anonymous Coward () on
whats wrong with using authpf to allow access?
Comments
By Anonymous Coward () on
By Joe () on
Is it possible to use ipsec and wep togeather?
If so how any ideas? I understand ipsec in theory, but am not able to get 2 boxes to talk togeather using it.