login
Header Space

 
 

Re: securing OpenBSD wireless network

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: openbsd-misc <misc@...>
Cc: Juan Miscaro <scry_mr@...>
Date: Friday, November 16, 2007 - 8:35 pm

On Nov 16, 2007 2:39 PM, Juan Miscaro <scry_mr@yahoo.ca> wrote:

I combined authpf with OpenVPN, using some big hints from some easily
google-able places.  Even though WEP and WPA aren't supported by
OpenBSD, I still wanted to have authenticated and encrypted traffic.
This might be overkill for some but it works for me.

After setting up the wireless interface to dhcpd a private netblock, I
locked it down with pf:
block in on $wlan_if
pass in on $wlan_if proto udp to port { bootps, bootpc }
pass in on $wlan_if proto udp to ($wlan_if:0) port domain
pass in on $wlan_if proto tcp to ($wlan_if:0) port ssh

Then I setup authpf to allow authenticated users the ability to
connect to the VPN:
pass in on $wlan_if proto udp from <authpf_users> to ($wlan_if:0) port 1194

Next I configured OpenVPN in routed mode.  It hands out IPs from yet
another private netblock I have permanently attached to lo1.

Finally, I treat the tun0 interface like a semi-trusted wired
interface in pf and apply my standard list of allowable client
applications:
client_if = "{ sk0, tun0 }"
pass in on $client_if proto udp to port $udp_client_ports
pass in on $client_if proto tcp to port $tcp_client_ports

This obviously isn't my full pf.conf, and care must be taken because
the rules are highly dependent on order.  My initial setup took nearly
a full day to configure and troubleshoot, since I had to get pf,
authpf, dhcpd, named, and OpenVPN to all cooperate.  I found that
selectively allowing and denying ICMP was of great assistance while
testing pf rules and tcpdump to be essential when I had other services
misconfigured.

Windows and OS X OpenVPN clients are readily available and
configuration is easy if you understood what you were doing when
setting up the OpenVPN server.

Although I feel like I've got a good handle on all the interactions
here, I'm no professional and if there are any gaping holes in this
setup, I am eager to hear about them.  I plan to investigate IPSEC in
the near future, which may be an alternative.

--david
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
securing OpenBSD wireless network, Juan Miscaro, (Fri Nov 16, 3:39 pm)
Re: securing OpenBSD wireless network, David Higgs, (Fri Nov 16, 8:35 pm)
Re: securing OpenBSD wireless network, Lars Hansson, (Sun Nov 18, 10:19 pm)
Re: securing OpenBSD wireless network, Clint Pachl, (Mon Nov 19, 1:51 am)
Re: securing OpenBSD wireless network, Lars Hansson, (Mon Nov 19, 8:40 am)
Re: securing OpenBSD wireless network, Tor Houghton, (Mon Nov 19, 7:18 am)
Re: securing OpenBSD wireless network, David Newman, (Mon Nov 19, 11:59 am)
Re: securing OpenBSD wireless network, Tor Houghton, (Mon Nov 19, 5:23 pm)
Re: securing OpenBSD wireless network , Marco S Hyman, (Mon Nov 19, 5:44 pm)
Re: securing OpenBSD wireless network, Peter N. M. Hansteen, (Mon Nov 19, 5:57 pm)
Re: securing OpenBSD wireless network, Tonnerre LOMBARD, (Mon Nov 19, 12:16 pm)
Re: securing OpenBSD wireless network, David Newman, (Mon Nov 19, 6:20 pm)
Re: securing OpenBSD wireless network, Tonnerre LOMBARD, (Mon Nov 19, 6:36 pm)
Re: securing OpenBSD wireless network, David Newman, (Mon Nov 19, 7:08 pm)
Re: securing OpenBSD wireless network, Jairo Souto, (Thu Nov 22, 4:56 pm)
Re: securing OpenBSD wireless network, Marc Balmer, (Mon Nov 19, 1:32 pm)
speck-geostationary