1. Operating Systems FreeBSD and Monowall Joel Jaeggli For AIT Wireless and Security Workshop

2. Why FreeBSD? ● Traditional UNIX platform ● Heavily oriented towards network services rather than say desktop environment. ● The kernel and FreeBSD development is a central part of system management making it easy to maintain consistency between FreeBSD systems ● Ports tree and 3 rd party software integrated in the FreeBSD style of management.

3. Why Monowall? ● FreeBSD integrated into a cute little appliance platform. ● Complete FreeBSD Firewall in ~8MB ● All configuration in a single file (similar in style to some router platforms) but in xml

4. What Monowall Provides ● web interface (supports SSL) ● serial console interface for recovery – set LAN IP address – reset password – restore factory defaults – reboot system ● wireless support (access point with PRISM- II/2.5 cards, BSS/IBSS with other cards including Cisco) – stateful packet filtering – block/pass rules ● logging ● NAT/PAT (including 1:1) ● DHCP client, PPPoE and PPTP support on the WAN interface ● IPsec VPN tunnels (IKE; with support for hardware crypto cards and mobile clients) ● PPTP VPN (with RADIUS server support) ● static routes ● DHCP server ● caching DNS forwarder ● DynDNS client ● SNMP agent ● traffic shaper ● firmware upgrade through the web browser ● configuration backup/restore ● host/network aliases

5. Built on the following Software components ● FreeBSD components (kernel, user programs) ● ipfilter ● PHP (CGI version) ● thttpd ● MPD ● ISC DHCP server ● ez-ipupdate (for DynDNS updates) ● Dnsmasq (for the caching DNS forwarder) ● racoon (for IPsec IKE)

6. What we're going to do with it... ● Static routes ● IP firewall ● NAT

7. Monowall

12. Bibliography ● FreeBSD Handbook - http://www.freebsd.org/doc/en/books/handbook/ http://www.freebsd.org/doc/en/books/handbook/ ● Monowall - http://m0n0.ch/wall/http://m0n0.ch/wall/