Monowall and Captive Portal

1
Monowall and Captive Portal

• Timothy Meade
• Eric Stolten

2
What Is Monowall?

• Embedded firewall software package
• m0n0wall is based on a bare-bones version of
  FreeBSD, along with a web server, PHP and a few
  other utilities.
• The entire system configuration is stored in one
  single XML text file.

3
What Is a Captive Portal?

• The captive portal is a web page that
  users/clients are forced to visit before they are
  granted access to the internet.
• At this page they are asked to enter there user
  name and password.
• This username and password are passed along to
  the RADIUS server

4
The flow of data
5
How to Build a Monowall System

• Basic things you need
• Null modem cable
• Compact Flash media 8 meg
• Embedded PC system
• Soekris (who we used)
• PC engines
• Access point for wireless

6
Creating monowall

• The first thing you need to do is download an
  image of monowall and burn it onto your CF card
  with physdiskwrite.Exe.

7
(No Transcript)
8
First Boot

• For the first boot. Connect the null modem cable
  to the soekris box and power it on.
• Once fully booted connect the lan interface to
  the switch. Load a web browser and input
  http//192.168.1.1 to login to the web GUI of
  monowall.
• The Login/password originally was admin/mono.

9
Wan Configuration
10
(No Transcript)
11
Lan Configuration
12
(No Transcript)
13
Captive Portal configuration
14
(No Transcript)
15
DHCP Setup
16
D-link Router/AP Configuration

• Assigned the IP 192.168.0.2
• Disabled DHCP
• Changed SSID (service set identifier) to 354AP
• Password for admin and user changed to mono354

17
(No Transcript)
18
Physical Connection to the Network.
AP
Wireless user
Lan port
311
311
311
311
Monowall
Switches
WAN port
Lab 3
Lab 1 DHCP
Lab2 NIS
Lab 4 RADIUS
Gateway
19
Why It Took So Long

• Almost every time you mess up the configuration
  you have to reload the configuration file.
• Not using an AP
• Cant bridge lan/opt1 interfaces and run captive
  portal
• Misuse of the AP
• From monowall a connection was made to the WAN
  port of the AP it should have been on the switch
  side.

20
Other Plans?

• Changing the DHCP pool from 192.168.X.X to a
  range within our subnet.