This entry is part 6 of 6 in the series 4 SSIDs 1 Secondary Academy

This final network is quite possibly the ones that most Schools will shy away from on grounds of ‘security’ – where I work however that just isn’t an option as we have paying users of the school facilities right the way through the evening and weekends. Indeed the weekend after we put this public network in place we have ~110 users on the network all of which were taking part in a chess competition that was being held at the Academy.

James stop rambling and get on with the guide…

So for the Public WiFi network the objective is to provide guests with a shared key (which is changed regularly) to access the network and to be able to use the internet without putting in any web proxy settings.


As per with the BYOD network you must have the Smoothwall configured with a virtual adapter which sits in the Public VLAN (details here – before carrying on with this guide. The screen shots below cover the configuration required…

Windows DHCP Server

Next up you must configure your Windows DHCP server to provide the clients with their IP addresses…


The configuration on the HP MSM for this network is as easy as setting up the Mac Wi-Fi VLAN as I will just be using a pre shared key that is changed regularly. However there are plenty of other options available like a captive web portal or single use keys (Meraki have a pretty funky option where you are forced (or just directed to) to ‘like’ a Facebook page before you are authenticated onto the network).

Zone Bridging

Finally as part of the configurations for the BYOD and Public networks because we are using the Smoothwall (and not our internal router) as the default gateway we need a method to allow what are 3 separate networks (BYOD/Public/Internal) to communicate with each other. On Smoothwall firewalls this is called Zone Bridging. N.B. – To configure zone bridging you need to have the Zone feature installed as a module (System > Maintenance > Modules).

That’s all folks!

Here ends this series of posts; hopefully they have given you an interesting insight into one (of many) ways to configure a WiFi network inside a School (or indeed any workplace). Please note that for specific help on the Smoothwall side your best bet will be to get a hold of Smoothwall direct and for support on HP wireless networks you will probably need to get a VAR involved.

This entry is part 5 of 6 in the series 4 SSIDs 1 Secondary Academy

The BYOD network is quite possibly the hardest to setup (and thanks to the Smoothwall support guys for spotting an obvious mistake I made on my DHCP config the first time round!) of all 4 of the SSIDs by also the most rewarding when you see 300+ students and staff connected on their Phones, Laptops and Tablet PCs. In a typical school BYOD network setup you will have two hoops to jump through, authenticating onto the SSID and then authenticating against the schools web filter. However using the neat WPA Enterprise authentication mode on Smoothwall firewalls its possible to both authenticate onto the SSID and the web proxy at the same time making life much easier for your users.

So time to get the configuration going…

Smoothwall Firewall

First up you must have configured a VLAN for the exclusive use of the BYOD network (as per the guide here – taking special note of setting the IP Helper Address to a virtual network adapter on your Smoothwall firewall which sits in the BYOD VLAN. Take a look at the screen shots below for more info…

NB – in this configuration the Smoothwall firewall will allow connectivity to the internet at the users policy level, if you want to allow BYOD guests to access your internal resources you will need to configure the Smoothwalls DNS and Zone Bridging features. I will touch on this in the next article.


The configuration on the HP MSM is similar to setting up the Domain WiFi network in that a RADIUS server is configured and the VSC is configured to use that RADIUS server.

User guides

To help you get started with your own user guides feel free to download and modify the ones that I have used at my establishment below.

  OSA-BYOD - Android (498.4 KiB, 1,807 hits)

  OSA-BYOD - iOS (3.3 MiB, 1,840 hits)

  OSA-BYOD - Windows 7 (796.7 KiB, 1,550 hits)

  OSA-BYOD - Windows 8 (2.1 MiB, 1,565 hits)

  OSA-BYOD - Windows Phone (206.9 KiB, 1,326 hits)

  OSA-BYOD - Windows Vista (1.5 MiB, 1,452 hits)

You will note that Windows XP is omitted as it is no longer a Microsoft supported operating system (although XP does work with this configuration).