|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
One that confuses users switching over from FreeBSD and Linux is that OpenBSD's implementation of WPA is in the kernel, there is no wpa_supplicant userland component.
As jggimi mentioned, in order to utilize the kernels software WPA support, drivers must first support it. The 4.4 release was the first that offered WPA-PSK/WPA2-PSK but it didn't support every wireless chipset in the tree, 4.5 has come a long way since then.. so presumably more drivers will support it come May. |
|
|||
What's funny is that I've only ever used FreeBSD as a RAID server for some file storage. I've always used OpenBSD for my routing and firewalls.
I've typically found that the general idea of setting something up is pretty much the same across *nix's, with the main differences being a) where the file is stored (/etc, /etc/hostapd, etc) and b) some slight changes in command name (sfdisk or fdisk) and parameters. Obviously I was very wrong in this case! I've done WEP configuration only once before, and it was years ago, and I can't honestly remember whether it was on FreeBSD or OpenBSD. Since I was more than likely just toying around for geekpoints, and considering my confusion now, I'm guessing it was on FreeBSD. It really never occured to me that OpenBSD would include the encryption in the kernel - it makes sense to do so, and I'm really glad that they did. Hopefully when I get a chance to toy around again tonight with the -current v4.5 I d/led and installed yesterday I'll be able to get this thing working with no problems. At the very least, WEP encryption for the moment would be nice, just to let me know that I'm on the right track! |
|
|||
Quote:
|
|
|||
Here's the dmesg | grep ath0:
Code:
ath0 at pci3 dev 6 function 0 "Atheros AR5212" rev 0x01: apic 4 int 21 (irq 5) ath0: AR2414 7.9 phy 4.5 rf2413 5.6, FCC2A*, address 00:14:6c:89:52:3b |
|
|||
Thanks jggimi. I'll try just WEP encryption to see if that works tonight. Security wise, I can always force mac-address authentication for the time being until it does become available.
|
|
||||
I'd already mentioned it in post #13.
Quote:
If you're interested in authentication, consider authpf(8). In combination with a VPN or with SSH tunneling, you can have authentication, authorization, and encryption, all without WPA or WEP. |
|
|||
You also mentioned in #15 that the -current snapshot ath(4) driver supported wpa, which I am using
Quote:
|
|
||||
It's hard to tell what's going on with ath from the man page or announcements. And looking through the CVS logs in src/sys/dev/ic/ar52* doesn't help. One has to try it. And so far, it doesn't appear to work.
As for authpf, I recently posted a sample configuration: http://www.daemonforums.org/showthre...3099#post22947 |
|
|||
Quote:
Quote:
|
|
|||
It Lives!
So after no luck at all with the pre-release snapshot of 4.5 this week, I decided to go ahead and give it a shot tonight with the official release version.
Fired it up, immediately attempted an ifconfig on ath0, and system froze. Attempted numerous configurations, but anytime I specified a nwid with hostap enabled the system would lock up, no errors. I could enable hostap, but that doesn't exactly do me any good without having a NWID to connect to, and some form of security on it! So did a little digging, and notice a little nugget right out of the ath(4) man page that I have somehow overlooked: Code:
The following hostname.if(5) example creates a host-based access point on boot: inet 192.168.1.1 255.255.255.0 NONE media autoselect \ mediaopt hostap nwid my_net chan 11 Apparently hostap mode on wireless networks is not controllable via ifconfig. It needs to be handled by inet directly. And this means that you must create a hostname.if file with the parameters, and do Code:
# sh /etc/netstart Code:
inet 192.168.1.1 255.255.255.0 NONE media autoselect mediaopt hostap / nwid my_network wpa wpaakms psk wpaprotos wpa1 wpapsk $(wpa-psk / my_network mywpapskey) Thanks again to everyone for the assist! |
|
|||
Quote:
http://openbsd.org/faq/faq6.html#Setup |
|
|||
Quote:
|
|
|||
But what I find interesting is that issuing the command directly to ifconfig results in a system freeze. The only way I can get it to work without a freeze is through the hostname.ath0.
|
|
|||
Quote:
http://openbsd.org/report.html This site is independent of the project proper. Developers affiliated with the development of OpenBSD are not (generally) aware of discussions here, so any abnormal behaviour discussed here needs to be formally submitted in terms of problem reports if such problems are/can be resolved. As mentioned previously, there are a certain number of recent Atheros chipsets which are similar to what was referenced in the creation of ath(4) but not entirely the same. I have seen one properly identified in dmesg(8) output which then crashes the kernel in -current upon scanning for available access points. Not that this identifies what you are encountering, but for the developers to resolve such problems, they need as much useful information as possible. |
|
|||
I'll take a look and do that. I may have the same chipset - when entering a NWID directly into ifconfig (ie, ifconfig ath0 dhcp nwid something), my system would freeze.
I've noticed that right now, the system only wants to operate in 802.11b, not sure why. Going to investigate that further too. At least I have a wap again! |
Tags |
hostapd, openbsd |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Possible SMP Issue? | MetalHead | OpenBSD General | 1 | 25th November 2008 03:52 AM |
Dual ath cards with WPA2 in hostapd? | Malinda | FreeBSD Security | 4 | 8th June 2008 08:34 PM |
Nagios issue | scottro | General software and network | 5 | 31st May 2008 10:18 AM |
RAM issue | nikkon | FreeBSD General | 5 | 7th May 2008 04:26 AM |