Hey,
First off, thanks for reading. I had an existing network of Cisco Aironet APs running on switchports configured for the native vlan of our guest network. The trunk settings allowed all related VLANs, and has worked for ages.
Friday I put into deployment a Meraki MR52 AR mesh, and got the staff wireless working fine through radius, which isn't on the native VLAN. I assumed things would need to be tagged as usual, but alas my network has pitched a fit in bridge mode, and I had to leave things with bridge for the staff VLAN, and the Meraki NAT for guest. Which works, but isn't ideal as we can't control and shape traffic through the web filters.
Today I tried removing the native VLAN on the switchports and letting the APs pick up IP through DHCP, but that didn't work. What I'm trying to do is get the DHCP pool working for the tagged staff network (working) and the tagged guest wireless (not working), but Meraki is much different than the old network. I feel like I'm over complicating this, but all things FAQ seem to point to making sure the switchports are trunks, and native vlan is configured somewhere.
We only have two VLAN at this site, staff and guest, and Meraki support suggested spinning up a third VLAN and third DHCP just for the guest network, but there must be a better way.
TLDR; native vlans on AR switchports causing havoc, not sure where to go next to get both SSID obtaining DHCP.
No comments:
Post a Comment