Hi All,
We’re putting together a proof of concept for a customer who is looking for a WiFi deployment at a number of different locations, these WiFi connections need to provide internet access which is filtered.
We have the filtering platform in place in our DC, so no worries there, i just need a way of handing off the traffic from the WiFi APs on the remote sites to a device/port in my Co-Lo so i can filter it. We currently do this for one of our businesses using openvpn running on pfsense, but this hardware is expensive (too expensive for this project).
I’ve begun to look at MT hardware a little more deeply and i’m considering, i’d like to deploy an L2 network out to the AP’s to make it easy to deploy to sites where i have no control over the internal network (and conflicting local IP subnets is a risk). I’d host DHCP inside my network and use it to Hand Out IPs to Wireless Clients connecting on the remote sites.
1 x Higher Spec “Core” Device in my Co-Lo potentially scalable to 500+ Mbps throughput
1 x RB951Ui-2HnD at each site
1 x cAP 2n at each site where additional coverage is required.
Ideally i’d look to be running CAPsMAN on the Core device to control the APs and deploy SSIDs etc and have options for Captive Portal Etc too.
My initial thought was to use EoIP or L2TP as a tunneling protocol from the remote site back to the core and out to the internet via the Co-Lo Link, we don’t require any encryption on the tunnels, which need to support between 10 and 75Mbps down and 0.8-18Mbps UP (Depending on the type of link on site). We would per running either IP Routing or PPPoE on the customer site, depending on the presentation of the internet connection.
Any thoughts on this would be appreciated. I should add, the initial deployment will be 4 sites, but we would look to scale this up for other customers.
Cheers
Steve