BSD Guides

Automatic binary updates for OpenBSD

admin — Tue, 02 Apr 2013 02:07:16 +0000

One of the things i always thought holding OpenBSD back from attracting a larger user base is its lack of a simple way to upgrade the system – i am talking binary updates or moving to a new release. Learn about bluesnapper on his blog, a tool that helps with binary updates on OpenBSD, written by Ted Unangst.

I have no idea how i did not know about this tool or effort; i see so many people asking binary upgrades that i think there is a pretty big demand and truly hope this gets developed further. Reading the linked article above leaves me a little uncertain as to what the future is for that project. Anyways – now I’m off to learn more about bluesnapper so that in the next article i can outline using it step by step and what kind of issues where there on the way.

The post Automatic binary updates for OpenBSD appeared first on BSD Guides.

Awesome mini wireless keyboard and mouse

admin — Mon, 14 Jan 2013 16:51:25 +0000

I came across this great little device while doing some Christmas shopping in the local computer mall and fell in love immediately. Basically a tiny (the smallest I’ve seen so far anyways), yet fully featured wireless keyboard and mouse that is a must for any sysadmin bag and also works great with your home media center. Read more for the pros and cons.

So as you can see from the above what we have here is a pretty small keyboard and mouse, completely wireless. As you will see soon, there is a small USB receiver that is integrated into the back of the device. Pull it out, plug it into your server, and as long as it would support a regular USB keyboard, it is going to support this thing.

I imagine as any sysadmin that needs to visit client sites and server rooms, we all pack a more or less fully featured bag that contains essential items depending on your profession: Laptop, Screwdriver tools, network cables, serial adapters, pen drives, CD and DVD’s, and maybe a keyboard and mouse.

One would think no matter where you go, there always is a keyboard and mouse laying around, but actually every time you need one, there is none to be found. Until i found this one, i always brought my regular Logitech wireless set with me – but it never fit in the already overfilled bag nicely enough; and each time i forgot to bring it, it was one of those times i should have brought it.

So whats good about it?

Number one again, the size. The dimensions are roughly 152mm X 59mm X 12.5mm. It is light and fits into any pocket. Also, it does not miss any keys – it is a full QWERTY keyboard and a left & right click mouse with touch pad.

The device is reasonably sturdy, and you don’t feel like breaking it easily when using it. They keys have a decent touch to them and give good feedback. The key presses compare to using a Blackberry keypad if you can relate. It also has a back light – meaning you can turn on key illumination with the click of a button. Neat.

There are some handy shortcuts included, such as pressing FN+Enter sends a CTRL+ALT+DELETE. The mouse part of this device has left and right buttons, the arrow keys work as one would expect, and the touch pad has tap to click.

The range is basically up to 10 meters – and the manufacturers site says that “…it will have no impact on your health”. Amazing! If that is not enough, it also has a button activated laser pointer. Good idea i guess for those Power point presentations.

Whats not so good?

Well basically not much. Mainly typing on it for extended periods of time is sort of a pain. I typed this post on it to prove a point and to see if it would break – and it took forever. But then again, its not made for office work; Also, instead of a laser pointer, maybe i would have preferred a flashlight LED – it would have been more useful to me.

The one thing that i really dislike about it – others may disagree here – is that it is rechargeable via USB. I know that may be better for the environment and all, but i would have absolutely loved it if i could power the device by a single AA or AAA battery. The reason is that i am using this thing mainly to be part of my sysadmins tool bag, and i may not use it daily. I guess what will happen is that i only pull it out twice a month, and every once in a while ill be like “Dang. I should have charged it”. It would have been much better in that scenario to have a spare pack of batteries in the bag. Well again, its not terrible, and what i will do is get one of those 10USD mobile phone emergency charging thingies that i can use to charge the keyboard on the fly if need be. Advertised stand-by time is roughly 1 month by the way.

Cost:

I paid 280RMB (45USD) for it. Not sure if its available cheaper anywhere or not, didn’t care. The Brandname is ORICO and the Link to the website i found is http://www.orico.com.cn/product/59_692.html; you can see that the model on display has a trackball and mine only has a touch pad. But actually maybe i like touch pad better anyways.

Summary:

If you use a regular PC to be your home entertainment center, then this is a must have and will replace your current wireless keyboard and mouse. Its the same size as a regular remote. Same if you need to go to client sites or data centers to fix stuff and find a keyboard and mouse to be an essential part of your toolbox.

The post Awesome mini wireless keyboard and mouse appeared first on BSD Guides.

Upgrading FreeBSD 9.0 to 9.1 using freebsd-update

admin — Mon, 31 Dec 2012 06:54:36 +0000

Here a quick outline of upgrading FreeBSD from 9.0 to 9.1 on a Soekris 4801 i had installed just two days ago to be a small encrypted fileserver.

First a word of caution: Backup all your data; something we always want to do before doing system maintenance like this, especially when on a machine without physical access.

Second – this Document gives all the details and is the official resource. In addition to these Release Notes, they may provide valuable clues as to what we may need to watch out for when upgrading our systems.

To update our system, we will be using freebsd-update, a great piece of software that fetches and installs binary updates to FreeBSD.

To get started, ensure that your current system is up to date; a change was recently made to freebsd-update(8) (Errata Notice FreeBSD-EN-12:01.freebsd-update) which is needed in order to upgrade to FreeBSD 9.1-RELEASE.

# freebsd-update fetch
# freebsd-update install

If any updates where installed above – reboot your system before continuing.

Now the freebsd-update(8) utility can fetch bits belonging to 9.1-RELEASE. During this process freebsd-update(8) will ask for help in merging configuration files. If you are upgrading from FreeBSD 7.X or 8.X – consult the official installation document.

# freebsd-update upgrade -r 9.1-RELEASE
# freebsd-update install

The system must now be rebooted with the newly installed kernel before the non-kernel components are updated.

# shutdown -r now

After rebooting, freebsd-update(8) needs to be run again to install the new userland components:

# freebsd-update install

At this point, users of systems being upgraded from FreeBSD 8.2-RELEASE or earlier will be prompted by freebsd-update(8) to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries.

After updating installed third-party applications (and again, only if freebsd-update(8) printed a message indicating that this was necessary), run freebsd-update(8) again so that it can delete the old (no longer used) system libraries:

# freebsd-update install

Finally, reboot into 9.1-RELEASE

# shutdown -r now

Summary

On my Soekris 4801 which i can access only via console or network, the update went quite smoothly and i can report no issues as of now. Perfect!

The post Upgrading FreeBSD 9.0 to 9.1 using freebsd-update appeared first on BSD Guides.

FreeBSD 9.1 released

admin — Mon, 31 Dec 2012 03:58:41 +0000

A huge thanks to the FreeBSD team for releasing FreeBSD 9.1 – bringing us a lot of improvements such as a ton of new drivers (new INTEL GPU driver), a new C+11 stack, a stable version of the tmpfs filesystem, improvements to zfs, performance improvements on certain CPU, and much much more. Feels like a delayed Christmas gift.

Read the Release Notes for more details

As a side note: The FreeBSD Foundation has reached their funding Goal for 2013 – which i think is great news. The proverbial finger to all the nonbelievers: Not only did they reach the Goal, they exceeded it by at least 20% last time i checked. So much for relevance…thank you very much.

The post FreeBSD 9.1 released appeared first on BSD Guides.

Lettuce shoots dog

admin — Tue, 11 Dec 2012 08:31:09 +0000

I couldn’t help but notice while walking Metro in the South China Mall – and i think we all should have a bit of RL fun once in a while, hope you enjoy the share.

The post Lettuce shoots dog appeared first on BSD Guides.

Building a captive portal with OpenBSD

admin — Mon, 10 Dec 2012 07:39:57 +0000

There aren’t (m)any lightweight captive portal solutions out there for us, except a few clumsy heavy or badly maintained projects together with heir professional counterparts in routers better than home-grade. Captive portals are cool and useful, read on how to build one, including video demo.

If you have read http://www.bsdguides.org/2012/a-wireless-access-point-hotspot-using-openbsd/ then you already know how to build a wireless access point. If not – also fine, because i will go trough the whole process once again, except this time we will configure our system to configure on boot, instead of via a script. Of course Wifi is not required to run a captive portal, you can use this method to have it run on a regular firewall router as well.

Have a look at the movie to see it working in action before doing your own thing:

Youtube movie coming asap…

Requirements

You need a fresh install of OpenBSD 5.2 on a machine with two Network Cards. I used an older Asus EEEPC with wired + wireless NIC (alc0 & athn0).

You will also need to head over to GitHub and download the OpenBSD Captive Portal files – they contain the application and sample configuration files. They also contain a install.sh script, which helps you move everything into place – be sure to carefully understand what it does before running it though, as it will overwrite a bunch of configuration files such as /etc/pf.conf and /etc/dhcpd.conf to name a few.

The rest of this guide assumes you have extracted the Github files into a folder called /root/obsdcp

Outline

A quick overview of what a captive portal usually does and what this project wants to achieve: A user connects to a wireless access point, say in a Hotel. The access point will give an IP Address, but will not yet allow any traffic such as web or mail. When the user opens his browser, he is presented with a hotel login form of some sort. The user logs in using a password he is provided (by the front desk), and the access point informs the user that he now has internet access for a certain amount of time. The captive portal adds the Users IP address to a whitelist table that is allowed network access, and checks at regular intervals for addresses that need to be expired.

Lets get to it.

Setting up Apache

We need to configure and run our web server so we can intercept and serve web requests from non-authenticated clients. Open up your /var/www/conf/httpd.conf and make sure it has the following configuration directives:

Listen *:80
ServerName localhost
# Set a sensible contact info
ServerAdmin you@your.address.com
# Uncomment rewrite_module and expires_module
LoadModule rewrite_module ...
LoadModule expires_module ...
# Find  and set AllowOverride All
# to allow .htaccess
AllowOverride All

Because our httpd runs chrooted and our captive portal depends on Perl and CGI.pm, we need create a few folders and copy a bunch of files into our webserver directory.

mkdir /var/www/usr
mkdir /var/www/usr/bin
mkdir /var/www/usr/lib
mkdir /var/www/usr/libdata
mkdir /var/www/usr/libexec

cd /var/www/usr/bin
cp /usr/bin/perl .

cd /var/www/usr/lib
cp /usr/lib/libperl.so.* .
cp /usr/lib/libm.so.* .
cp /usr/lib/libutil.so.* .
cp /usr/lib/libc.so.* .

cd /var/www/usr/libexec
cp /usr/libexec/ld.so .

# Here i am copying a lot of possibly 
# unneeded modules for perls CGI.pm
# But it got the job done and i can use
# all of Perls base modules inside a
# chrooted httpd

cd /var/www/usr/libdata
cp -r /usr/libdata/perl5 .

Add the following line to /etc/rc.conf.local so httpd starts on boot

httpd_flags = ""

Setting up the portal application

Move needed files into place – remember the downloaded GitHub Files are at /root/obsdcp

cd /root/obsdcp
cp var/www/htdocs/* /var/www/htdocs/
cp var/www/conf/Obsdcp_config.pm /var/www/conf/
cp usr/local/bin/obsdcp /usr/local/bin/
cp etc/rc.d/obsdcp /etc/rc.d/obsdcp
touch /var/www/conf/obsdcp_queue.txt
touch /var/www/conf/obsdcp_allow.txt

obsdcp does the heavy lifting: It checks for new IPs to add to the whitelist, and existing IPs to expire after their time has run out. Add the following line to the end of /etc/rc.conf.local so obsdcp starts on boot

pkg_scripts="obsdcp"

Now we need to adjust a few file permissions:

cd /var/www/conf/
chown www:daemon *.txt
chmod 755 *.txt

# Set permissions
cd /var/www/htdocs/
chown www:daemon .htaccess
chown www:daemon *
chmod 755 .htaccess
chmod 755 *

Network configuration

Lets setup our wired and wireless interfaces. Find out your interface names by running ifconfig. Mine are as follows:

wired: alc0
wireless: athn0

Create /etc/hostname.alc0 so your wired interface is configured automatically at each boot. We need to give it a fixed IP and add your LAN’s default Router so it can access the Internet.

inet 10.0.1.254 255.255.255.0 10.0.1.255

Adding the default Router to /etc/mygate

10.0.1.2

Now lets setup our wireless interface to be a wireless hotspot; create /etc/hostname.athn0. It will setup your open wireless hotspot using the SSID FreeWifi on channel 11. Note the below is all on one line.

inet 10.0.3.1 255.255.255.0 10.0.3.255 \
media autoselect mediaopt hostap \
nwid FreeWifi chan 11 up

Configuring your Firewall

Firstly, set the sysctl to allow passing of packets between interfaces by adjusting /etc/sysctl.conf:

net.inet.ip.forwarding=1

Now copy the provided pf.conf to /etc/pf.conf

cd /root/obsdcp
cp /etc/pf.conf /etc/pf.conf.bak
cp etc/pf.conf /etc/pf.conf

I suggest you open up /etc/pf.conf and have a look at how it works; quote possible that you need to adjust the network interface names at the top to match your hardware.

Our pf.conf uses a table called whitelist to keep track of who is allowed internet access.

touch /var/db/whitelist

Add the following line to /etc/rc.conf.local so PF starts on boot

pf="YES"

Setup DHCPD

You will need to run dhcpd to provide network configuration to clients connecting to your access point. Copy the provided file, but adjust as you need. It’s not good to blindly copy stuff, always have a look inside and try to understand what it does.

cd ocbsdcp
cp /etc/dhcpd.conf /etc/dhcpd.conf.bak
cp etc/dhcpd.conf /etc/

Add the following line to /etc/rc.conf.local so dhcpd starts on boot

dhcpd_flags="athn0"

Configure BIND

Yes, we want DNS as well; its not strictly needed but we can do a lot of nice things with it such as url filtering or ad blocking.

cd ocbsdcp
cp -r /var/named /var/named-bak
cp var/named/etc/named.conf /var/named/etc/
cp var/named/etc/rndc.conf /var/named/etc/
cp var/named/etc/rndc.key /var/named/etc/
cp etc/resolv.conf /etc/resolv.conf

Add the following line to /etc/rc.conf.local so named starts on boot

named_flags=""

Check and reboot

Now its time to make sure everything works as expected. Reboot your access point and check that:

You can ping your Router
You can ping bsdguides.org
Apache is running
dhcpd is running for your wireless NIC
named is running
PF is enabled
obsdcp is running

Check that relevant services are running by using ps -ax and netstat -an, also check your /var/log/messages and /var/log/daemon logfiles for any potential error messages. For any issues, troubleshoot, reboot, repeat.

Conclusion

Given that you followed the above guidelines and neither of us made any mistakes, you now have an access point with a captive portal. Connect to the “FreeWifi” access point by using your mobile or laptop, and try to browse the Internet. Are you asked to provide credentials before being allowed access? Great! Simple configuration and account management can be done inside /var/www/htdocs/Obsdcp_config.pm – you probably want to change those default username and passwords.

I chose to keep the index.cgi as simple as possible so everything is in base; though i am considering a more feature rich frontend as well. For the moment, this does the job just fine, and runs happily inside a coffee shop i frequently visit.

Let me know what can be improved, post your issues or suggestions in the comments.

The post Building a captive portal with OpenBSD appeared first on BSD Guides.

FreeBSD fundraising – donate now!

admin — Wed, 05 Dec 2012 16:03:12 +0000

Why not spend some of this years Christmas profits on your most favorite OS? FreeBSD calls for donations, every dollar counts! While free to use FreeBSD is certainly not free to develop: Investments need to be made into hardware and developers may need to be paid! Head over to http://www.freebsdfoundation.org/donate/ and make your donation to show your support and help out the project. Your donations enable people that care about FreeBSD to keep improving it and keep working on it.

If you want to know where your money is going, here is a non-exhaustive list from what happened last year:

Funding development projects to improve FreeBSD, including: Capsicum Application Sandboxing, Growing UFS Filesystems Online, the NAND Flash File System, IPv6 Performance Analysis and Improvements, Distributed Security Audit Logging, and porting FreeBSD to the Efika ARM platform.
Educating the public and promoting FreeBSD. We produced a high-quality FreeBSD 9 brochure and visited companies to help facilitate collaboration efforts with the Project.
Sponsoring BSD conferences and summits in Europe, Japan, Canada, and the US.
Protecting FreeBSD IP and providing legal support to the Project.
Purchasing hardware to build and improve FreeBSD project infrastructure.

If you donated, you are awesome!

The post FreeBSD fundraising – donate now! appeared first on BSD Guides.

awstats workaround for custom delimiter tab methodurl bug

admin — Wed, 05 Dec 2012 11:22:23 +0000

For some sites i am using the venerable awstats to keep track of web site statistics; and came across a problem today:

If your apache LogFormat is using a \t (tab) to separate fields you may notice how awstats does not parse %methodurl correctly – instead it looks like your two top pages are called HTTP/1.0 and HTTP/1.1. Read more for a workaround.

So after an hour of looking i found that this behaviour is a documented bug (should have checked that first!). Since i was unable to produce an immediate fix, i came up with this workaround, so you can leave your httpd.conf’s LogFormat the way it is and still use awstats to produce functioning reports:

Create a new document called /usr/local/bin/awstats_workaround.pl with the following contents:

#!/usr/bin/perl
 
use strict;
use warnings;
 
die("Need Logfile as input!!!\n") unless (@ARGV);
 
while(<>){
	s/\t/ /g;
	print;
}

Now in your relevant awstats.conf file, make sure you have the following 2 entries:

LogFile="/usr/local/bin/awstats_workaround.pl /var/log/httpd-access.log |"
LogSeparator=" "

Now create your awstats report as usual. Awstats gets its input from /usr/local/bin/awstats_workaround.pl, which replaces all those \t characters with a regular old space. Hope this quick workaround helps you until this custom delimiter bug is fixed in the awstats code – people are aware of it but so far versions up until 7.1 are not fixed yet

The post awstats workaround for custom delimiter tab methodurl bug appeared first on BSD Guides.

A wireless trap using OpenBSD – reloaded

admin — Tue, 04 Dec 2012 05:00:27 +0000

Build a OpenBSD wireless access point that redirects any client request for any website to a website of your own design. With a little imagination you could adapt this technique for more nefarious purposes – but that is not something we endorse here. Something more applicable to our kind may be to use this technique to do basic DNS based filtering, ad-blocking or something along those lines.

Requirements

I assume you have a OpenBSD Box setup as a wireless access point – if not, go and read this previous post: http://www.bsdguides.org/2012/a-wireless-access-point-hotspot-using-openbsd/

Getting started

Done? Good. Now you have a functioning OpenBSD wireless access point and are ready to modify it to be a “wireless trap”. How it works is that we setup a web server and DNS service on our OpenBSD box, and then configure the DNS system so that for any hostname for any website the client wants to resolve, our DNS server answers with the IP address of the access point itself (10.0.3.1 in our example) – therefore loading up the website running on localhost.

Configure your DHCP Server

Make your /etc/dhcpd.conf look like the below:

option  domain-name "my.domain";
option  domain-name-servers 10.0.3.1;

subnet 10.0.3.0 netmask 255.255.255.0 {
        option routers 10.0.3.1;
        range 10.0.3.100 10.0.3.150;
}

The only difference from this dhcpd.conf to the one in our Hotspot post is the option domain-name-servers 10.0.3.1; which basically tells clients connecting to our access point that it is responsible for DNS.

Configure DNS using BIND

There are different ways to setup DNS – but when possible i like to use what the base system already provides – and therefore chose BIND. BIND’s configuration is held in /var/named/etc/.

Configure your /var/named/etc/named.conf like this:

acl clients {
        localnets;
        ::1;
};

key "rndc-key" {
        algorithm hmac-md5;
        secret "FbxGpQ7kUF55caHrmmeZwfbfqKaLF367DYsQnJuTcQA=";
};

controls {
       inet 127.0.0.1 port 953
       allow { 127.0.0.1; } keys { "rndc-key"; };
};

options {
        version "";     // remove this to allow version queries
        listen-on    { any; };
        listen-on-v6 { any; };
        empty-zones-enable yes;
        allow-recursion { clients; };
};

logging {
        category lame-servers { null; };
        channel query_info {
                file "query.log" versions 3 size 10m;
                severity info;
                print-category yes;
                print-time yes;
        };
        category queries { query_info; };
        category resolver { query_info; };
};

# This is to setup the wifi trap
zone "." {
        type master;
        file "master/root.master";
};

zone "." {
        type hint;
        file "etc/root.hint";
};

zone "localhost" {
        type master;
        file "standard/localhost";
        allow-transfer { localhost; };
};

zone "127.in-addr.arpa" {
        type master;
        file "standard/loopback";
        allow-transfer { localhost; };
};

zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" {
        type master;
        file "standard/loopback6.arpa";
        allow-transfer { localhost; };
};

Configure your /var/named/etc/rndc.conf file like this:

key "rndc-key" {
        algorithm hmac-md5;
        secret "FbxGpQ7kUF55caHrmmeZwfbfqKaLF367DYsQnJuTcQA=";
};
options {
        default-key "rndc-key";
        default-server 127.0.0.1;
        default-port 953;
};

Now we need a master zone file that basically makes our DNS Server claim itself to be responsible for whatever DNS query that comes in. Add a file called /var/named/master/root.master and make it look like this:

$ORIGIN .
$TTL 6h

@       IN      SOA     . root.localhost. (
                        1       ; serial
                        1h      ; refresh
                        30m     ; retry
                        7d      ; expiration
                        1h )    ; minimum

                NS      127.0.0.1
*       IN      A       10.0.3.1

Setting up Apache

Now this is very easy – open up your /var/www/conf/httpd.conf and adjust the relevant configuration directives as written below:

ServerName localhost
Listen *:80

Adjusting our /etc/pf.conf

We need to adjust our firewall configuration so that basically it drops all traffic except ports 80 and 53, for http and dns respectively.

wired = "alc0"
wireless = "athn0"

icmp_types = "{echoreq, unreach}"

set block-policy return
set loginterface $wireless
set skip on lo0

# to some packet scrubbing
match in all scrub (no-df max-mss 1440)

# Handles NAT for the wireless clients
match out on egress inet from !(egress:network) \
to any nat-to (egress:0)

# Block everything by default
block log all

# Let all traffic out
pass out quick

# Let just some traffic in (dns & http)
pass in quick inet proto { tcp udp } from any to ($wireless) port { 53 80 }
pass in quick inet proto icmp all icmp-type $icmp_types keep state

Adjusting our start-up script

As you know from reading the Hotspot tutorial i like to boot up my OpenBSD in a clean state with no settings set and then run a small script that sets everything up the way i need. Once things are perfect it is simple enough to start all the needed daemons at boot time, but especially while hacking around this is my preferred way. Copy my below setup script and adjust interface names etc. as needed. Once done – save it as setup_hotspot or whatever, and make it chmod +x.

#!/bin/sh

# Setup wired Network card
ifconfig alc0 inet 10.0.1.254 netmask 255.255.255.0 up

# Set our wireless open hotspot
ifconfig athn0 inet 10.0.3.1 255.255.255.0 media autoselect mediaopt hostap nwid 1FreeWifi chan 1 up

# default route
route add default 10.0.1.2

# start DHCP on our wireless interface
dhcpd athn0

# start our DNS Service
# and make sure it gets used to resolve DNS queries
named
echo nameserver 127.0.0.1 > /etc/resolv.conf
echo lookup file bind > /etc/resolv.conf.tail

# start our webserver which we configured
# to listen on *:80
apachectl start

# start our modified packet filter
pfctl -ef /etc/pf.conf

Testing

After you run above script, you should see a new wireless hotspot called 1FreeWifi. Connect to it – then try and browse to any website. You will notice how no matter which site you want to pull up, all you get is the default /var/www/conf/htdocs/index.html page. Have a look at our Youtube movie to see this in Action.

Conclusion

While this can be a lot of fun, specifically in a public place where everybody is like “Cool, free Wifi”, and then like “WTF?”, the use of this is kind of questionable. It does however show you some important concepts i think on neat stuff you can do with an OpenBSD based wireless access point. Go get creative with your index.html page, do something funny, or something useful.

If you have neat ideas or suggestions – please comment.

The post A wireless trap using OpenBSD – reloaded appeared first on BSD Guides.

A simple console wireless network manager for OpenBSD

admin — Mon, 03 Dec 2012 05:00:28 +0000

Maybe some will enjoy this simple console based wireless network manager i use on my OpenBSD Box to connect to the different wireless networks i come across during the week. 4NU558BUVMKY

Watch to see how it works on Youtube – for best results set to 720pHD and view full screen:

Get it from GitHub and follow the installation instructions – should take less than a minute as its just two files.

After installation, set your wireless interface and some networks inside the /etc/wireless.cfg config file.

# This will list all your configured
# wireless networks
wireless

# This will connect to wireless 
# network named "yournetwork" given that
# it can be found in the config, and of course
# that it is in rage
wireless yournetwork

Its really very simple – but i use it daily as i move around with my laptop. Saves me a bunch of time.

The post A simple console wireless network manager for OpenBSD appeared first on BSD Guides.