Link here in case you were curious:   https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html ... View more

@PhilipDAth wrote: Did you know they in WLC firmware updates Cisco regularly drop support for older AP's?   I bet you have upgraded to a release that no longer supports your older APs - and 1131's are pretty old.  Check the release notes. Good catch Phil, totally skipped my mind.   For reference @MarcP , the latest version 1131 supports is 8.0.x ... View more

Can you provide a screenshot of how you have Option 43 configured? You'll need to setup a DHCP option 'custom' code = 43 and Type = HEX Use this tool to convert your WLC IP to HEX for the OPTION 43 https://shimi.net/services/opt43/ Might be worth trying to set up the port forwarding via the following guide using these ports. Not sure if this will work though. https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX ip forward-protocol udp 12222 ip forward-protocol udp 12223 ip forward-protocol udp 5246 ip forward-protocol udp 5247 ... View more

You would have to tell us basically is what I was getting at since it could be a variety of things 😃 So let us know what you see ^_^ ... View more

@BrechtSchamp wrote: however clients on the NAT SSID may be unable to communicate with these networks." Thanks for the link @BrechtSchamp    That statement on the document seem's a little vague to me though, no?   So maybe I'm misunderstanding something fundamental here.  The AP is NAT'ing, so I'm not seeing how the client behind it getting  (lets just pretend 10.1.1.1) will ever be able to have an issue with a LAN side client or device that might also have 10.1.1.1 (coincidentally).  I always viewed this as like RFC1918 over the Internet. Issues don't happen, because its being NAT'ed via the public IP.    In this case the 'public IP' being the IP of the AP.  The client won't even know what that IP is since he'll only ever know about 10.128.128.128   The only thing I can think of is if the client gets 10.128.128.128 (either unlikely or not possible via Meraki doing something behind the scenes), or two clients get the same IP, but would that matter either since NAT/and isolation?   I hate it when I start to overthink stuff like this lol ... View more

Also, another fun fact @DHAnderson is that NAT mode, while it works great for what it does, does not allow seamless roaming.  =(   Roaming - NAT mode with Meraki DHCP will use the IP address of the AP as the public IP address for wireless clients. When a client roams between APs with Meraki DHCP, TCP connections will drop and have to be re-established. This can cause problems with some applications and devices.   This is why I tend to go out of my way to create a guest VLAN etc., so that I can use bridge-mode. ... View more

@MerakiDave  Hey Dave, do you by chance know if 10.128.128.128 is automatically excluded as a possible IP a client will receive, from the pool of 10.0.0.0/8 when NAT mode is used?   Thanks and sorry to bug you 😃 ... View more

I guess the only scenario that I can think of (and maybe it is what you were thinking of but I missed the point), is if the client happens to receive 10.128.128.128 as his IP. Maaaaaaaaaybe that's possible but I would like to think the Meraki went out of their way to exclude that IP as an ever possible choice for its random DHCP algorithm + MAC hashing etc. ... View more

NAT mode means the client IP in the 10.0.0.0/8 never gets 'seen' on the LAN side. It just see's [AP-IPADDRESS:port]. Unless I have somehow completely misunderstood how NAT mode works with Meraki lol From the client's perspective, its gateway/DHCP/DNS is the AP (10.128.128.128). If the client gets an IP of say 10.1.2.3, only the AP will know about that, nothing on the LAN side should see that. ... View more

Are you saying the SSID is using NAT mode? The LAN 10.63.145.0/24 wouldn't interfere even if a client landed on that subnet if using NAT mode, as it just see's the AP IP which is on the LAN side. ... View more

You have to go to security appliance>addressing & vlans and you can see the port configs there. ... View more

Port 30001 was indeed being blocked, and just allowed it, now cloud proxy video stream works, and exporting video too. Thanks again ! ... View more

@jdsilva wrote: Given that Chromecasts use mDNS to advertise their services to client devices, and you don't want guests to "see" or cast content to every CC in a hotel you're pretty much forced into a one VLAN per room model. You could stand up one SSID per room, but besides being just plain stupid you can't configure that many SSID's in a single network in the Dashboard. You could go with multiple networks, but that's even stupider 😉   With one VLAN per room, and ideally one SSID, you need a way to get clients authenticated and into their room's VLAN. Welcome to RADIUS authentication with dynamic VLAN assignment.  While we're talking about authentication... What are you authenticating? You can't do dynamic VLAN assignment with PSK, so you're doing either MAC based or 802.1x (You need a RADIUS response that contains the VLAN id). Ideally I would think you'd want something like lastname and room number... But how do you get that info to authenticate against? It's all in the PMS for the hotel...    @jdsilva  Out of curiosity, have you had any luck on this front via the following?   I'm assuming their is going to be a limit on this feature no?   ... View more

@MerakiDave    We have 1Gbps symmetrical circuit here for Internet thankfully.   I've always viewed the feed with local LAN connection, as I'm on the same network/vlan (switch stack for that matter).   However I'm starting to lean towards firewall because I also found out that I am unable to get Cloud Proxy to load (so that I can view the camera feed from outside our network). Me thinks this is also causing an issue with the exportation process.   I'll have to hit up security team. 😃   Thanks !! ... View more

Rebooted Still no luck   bah humbug   ... View more

I'll give that a shot Its an MV12W for reference, and it is on 3.29 ... View more

Well what about just actual client connections page then? Regardless of splash-page attempts, they clients there either connected or they didn't. Would that give you the count your looking for? So you could just disable the splash page all together and just use Monitor>Clients. Or is your splash-page having them insert their name and other details? Otherwise I"m not sure about disabling the forced-login thing ... View more

This link explains everything:   https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Analytics   Here is an example of a small branch office I have.   ... View more

oooooh I think I figured it out I guess I need to find a page not using HTTPS Block Page is Not Displayed If your browser/the website is using HTTPS/SSL, the browser will not be forwarded to the block page. Due to the encrypted nature of SSL requests, the MX cannot decrypt and redirect HTTPS traffic. Instead, the MX will force the request to timeout (an example of which can bee seen in Fig. 3, below). ... View more

@Haydn wrote: I get the following, I cant see that you can customise it anywhere or turn if off/on ? It points to Wired.Meraki.com though                   So maybe with @jdsilva's first reply make sure the first part is enabled (from the screenshot) "Local device status pages (my.meraki.com, switch.meraki.com, wired.meraki.com)" This is what I believe I remember seeing in the past.   Hmm...I guess I'll have to tshoot this  =(   Thanks ! ... View more

I do indeed, however that is for when Apple byod devices get blocked from the corp SSID via the group policy settings under access control. That works perfectly. Maybe i'm just not remembering it correctly? i just could have sworn there was a message about content filtering. ... View more