Community Record
19
Posts
1
Kudos
0
Solutions
Badges
Apr 18 2019
7:28 AM
Nope you're good, I was miss reading your diagram. So with your original setup, your AP's are going to pull an address from your ADSL router because you have ports 3-5 set as native vlan 1. You are also trying to pass VLAN 1 to your clients for DHCP. We know this doesn't work because you can't pass tagged traffic of the same vlan as your native, the port will drop the tags. If you change the native vlan on ports 3-5 to say vlan 5, you would be able to pass vlan 1 traffic over that interface and route the way you would like. You would need to make sure that you have a DHCP scope tagged to vlan 5 though as the meraki APs still need to pull an internal IP from somewhere. This is where I was going with the "management" VLAN. TL;DR The AP's need an IP that is not pulled from the VLAN you are tagging your clients as.
... View more
Apr 9 2019
4:19 AM
1 Kudo
Grand I'll make a purchase. Thanks a lot for the input folks.
... View more
Dec 4 2018
7:09 AM
That's a real shame. I get one story from Exchange folk and one from the meraki installer. Thanks for clarifying
... View more
Mar 22 2018
6:59 AM
So: yes, one Network per site... Not just because you then get 15 SSIDs for each site, but also: A Network can only be in one time zone - if you have lots of APs in different countries, you will probably want accurate local time for each. If you ever want to deploy the MX Security / VPN / SD-WAN appliance, you can only have one MX active in any single Network in Dashboard. (MR + MX and maybe MS switches too, all together, then suggests use of Combined Networks, per site, as @Uberseehandel mentioned)
... View more
My Top Kudoed Posts
Subject | Kudos | Views |
---|---|---|
1 | 8726 |