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
  #1   (View Single Post)  
Old 15th September 2010
divadgnol67 divadgnol67 is offline
Fdisk Soldier
 
Join Date: Jul 2009
Posts: 79
Default Wanted: More Documentation

I have read the man pages for ifconfig and my wireless card wpi in my case and have a decent understanding of their contents. This morning while at Panera Bread getting some coffee I attempted to connect to their network and was able to do but only after resetting my nic to its default setting (i.e., -wpa, -nwid, -nwkey, etc, etc) I re-read ifconfig and wpi and could find no mention of this being a necessity. It is probably common knowledge so I apologize for my ignorance.

Onto my question - is there recommended reading in order to gain a greater understanding of how networks and nic's work within OpenBSD.

divadgnol67
Reply With Quote
  #2   (View Single Post)  
Old 15th September 2010
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by divadgnol67 View Post
...is there recommended reading in order to gain a greater understanding of how networks and nic's work within OpenBSD
  • The first thing to recognize is that wired Ethernet networks are a mature & stable technology. The same isn't true about wireless. If you read through old threads both here & on the official misc@ mailing list, you will find a number of people commenting about various idiosyncrasies about the different wireless cards they use.

    Wireless in the Open Source world (including Linux) is not plug-&-play. Some cards work, others don't, & many times users have to experiment to find out the peculiarities associated with the cards they have. Some work better than others. The problem is that the wireless vendors sell chipsets with the same model numbers, but varying degrees of crippled behavior. Likewise, new cards continue to come out where drivers don't exist yet. All of this is compounded by the fact that many vendors are very nervous about releasing specifications to their products. This hurts the Open Source world in its quest to write robust drivers.
  • As for documentation, network engineers have to digest lots of information. For general knowledge, go to a library & look at books by Douglas Comer. If you want to know what's going on at the code level, read the books by Richard Stevens. There aren't definitive wireless books yet, but you might want to look into the book market surrounding exams such as the CWNA, not that I am advocating that certifications are the best route, but digesting their material may be useful. Lastly, there are always the RFC's.
  • As I have said in other threads, the OpenBSD project is very small in comparison to other more publicly known projects. The developers like it this way. There will be gaps in the community & what documentation is made available by the project. Third-party information not affiliated with the project should be read with great skepticism because much of it is incomplete, out-of-date, or simply wrong. This is why being well-grounded is so very important to avoid getting snared in the OpenBSD world.
Reply With Quote
  #3   (View Single Post)  
Old 15th September 2010
divadgnol67 divadgnol67 is offline
Fdisk Soldier
 
Join Date: Jul 2009
Posts: 79
Default

@ocicat,

Thank you for the recommended reading and the additional insight.

divadgnol67
Reply With Quote
  #4   (View Single Post)  
Old 16th September 2010
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

Network configuration in OpenBSD is not friendly to roaming users which is not to be seen as a critiscm. A secure OS just does not hook-up with the first available router

One option is to have two hostname.wpi0 interfaces, ie one with no wpa or wep and another with what ever encryption your home router users. Rename the one you want to use to hostname.wpi0 while renaming the additional interface as something like home.wpi0. Restart your network with
#sh /etc/netstart wpi0
Reply With Quote
  #5   (View Single Post)  
Old 16th September 2010
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Banned
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Default

It seems counter intuitive to random join networks within range, in fact I believe a user should always configure this themselves.

I would consider it bad etiquette to just walk into someones house, and it should be bad wireless etiquette to join some strangers network and start spewing packets.
Reply With Quote
  #6   (View Single Post)  
Old 16th September 2010
divadgnol67 divadgnol67 is offline
Fdisk Soldier
 
Join Date: Jul 2009
Posts: 79
Default

@shep,

thanks for the tip. i didn't know it was possible to have two hostname.if files.

@BSDfan666,

I agree, I do not want to join any wireless network willie nille. But, I do want to understand how to join a network when needed. Love the term "start spewing packets"

I have decided to write simple shell scripts to connect to the various networks that I frequent.

Thanks again everyone,

divadgnol67
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
NetBSD Documentation kalimuthu NetBSD General 1 20th July 2010 04:12 PM
Requesting a refund of an unused not wanted MS Windows license guitarscn Off-Topic 11 29th January 2010 12:18 AM
Newbie-friendly "printing in OpenBSD" guide wanted Shagbag OpenBSD Packages and Ports 5 7th July 2008 09:26 PM
BSD Magazine/ authors wanted :) kasia Off-Topic 8 6th June 2008 10:51 AM
server documentation mtx Off-Topic 7 8th May 2008 09:39 PM


All times are GMT. The time now is 08:09 PM.


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