DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
Old 18th May 2011
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

I generally don't recommend using hostname.if(5) for wireless, but that's my recommendation.. mostly due to the fact that switching between networks and configurations is a high probability with wireless, manual configuration makes more sense.

What you don't explicitly tell us is what happens after running ifconfig/dhclient, pasting the full output in [code][/code] tags.. both before and after you set the nwid and wep key in ifconfig.. will help diagnose possible configuration errors.

Are you bringing the interface up? does the connection establish? is a lease acquired? are you able to ping your router or other hosts?
Reply With Quote
Old 18th May 2011
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 566
Thanked 14 Times in 13 Posts
Default

Quote:
Originally Posted by chicago View Post
If i drop encryption then I'd provide free internet for some of my neighbors and this would not be pleasant. Even if it would work that way I can't do it.
In suggesting to drop encryption, I had in mind doing it for a short time just to try to get a connection, rather than on an ongoing basis. Sorry I probably should have been more clear about that. However, only you can judge if even that would be an unacceptable security risk, fair enough.

I do have two other suggestions to add, assuming you will use encryption.

(1) Carefully check that your WEP key is the same as used in the the AP. I.e., are they both strings or both hex, or do you have some accidental mixture?

(2) Rather than DHCP, you can try running
# tcpdump -ni bwi0
No IP address is needed for this. If the connection and encryption are right, and if there is wireless network traffic, you should see packets being reported.

Last edited by IdOp; 18th May 2011 at 01:21 PM.
Reply With Quote
Old 18th May 2011
backrow backrow is offline
Real Name: Anthony J. Bentley
Shell Scout
 
Join Date: Jul 2009
Location: Albuquerque, NM
Posts: 116
Thanked 10 Times in 4 Posts
Default

This is how I typically connect to a WPA wireless network, assuming wireless interface foo0:

/etc/hostname.foo0:
Code:
dhcp NONE NONE NONE
# ifconfig foo0 nwid networkgoeshere wpa wpakey keygoeshere
# sh /etc/netstart foo0


This is in -current; I remember they changed the key semantics fairly recently (you used to have to run /usr/sbin/wpa-psk to generate the key, then provide those results to ifconfig).
__________________
Many thanks to the forum regulars who put time and effort into helping others solve their problems.

Last edited by backrow; 18th May 2011 at 05:18 AM. Reason: Correction, thanks Daffy
Reply With Quote
Old 18th May 2011
Daffy Daffy is offline
Fdisk Soldier
 
Join Date: Jun 2010
Posts: 73
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by backrow View Post
# ifconfig foo0 nwid networkgoeshere wpa wpapsk keygoeshere
I think this is wrong. "Wpapsk" was being used up until 4.9. Someone correct me if I'm wrong, but ifconfig(8), states that you must use "wpakey" instead.

So you should use
Code:
ifconfig <interface> nwid <id> wpakey <key>
Reply With Quote
Old 18th May 2011
backrow backrow is offline
Real Name: Anthony J. Bentley
Shell Scout
 
Join Date: Jul 2009
Location: Albuquerque, NM
Posts: 116
Thanked 10 Times in 4 Posts
Default

Quote:
Originally Posted by Daffy View Post
I think this is wrong. "Wpapsk" was being used up until 4.9. Someone correct me if I'm wrong, but ifconfig(8), states that you must use "wpakey" instead.

So you should use
Code:
ifconfig <interface> nwid <id> wpakey <key>
You’re right. From /usr/src/sbin/ifconfig/ifconfig.c:
Code:
        { "wpakey",     NEXTARG,        0,              setifwpakey },
        { "-wpakey",    -1,             0,              setifwpakey },
/*XXX delete these two after the 4.9 release */
/*XXX*/ { "wpapsk",     NEXTARG,        0,              setifwpakey },
/*XXX*/ { "-wpapsk",    -1,             0,              setifwpakey },
The options do the same thing but wpapsk will be removed soon.
__________________
Many thanks to the forum regulars who put time and effort into helping others solve their problems.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
script add user with encrypted password wesley OpenBSD General 3 14th December 2010 03:22 PM
Encrypted == secure? passthejoe OpenBSD Security 13 9th November 2010 05:45 PM
Tool for cracking encrypted session data J65nko News 0 9th June 2010 06:31 PM
Openbsd 4.5 network connection timeout andrewm OpenBSD General 4 11th September 2009 02:32 AM
Encrypted disk compatibility issue TheLogicInverter FreeBSD Security 3 30th January 2009 02:59 PM


All times are GMT. The time now is 12:17 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick