About CptnCrnch

CptnCrnch

REST API is simply using HTTP for communication. Other than having to authenticate before using the proxy, there should be nothing special about it. Depending on proxy configuration, PUT and „special“ HTTP requests could be blocked though.

CptnCrnch

Sounds like even more fun, then. You got me, I‘m in 😉

CptnCrnch

Hi Antonio! Hope you're happy without the CLI now 😉 At least I found myself in a similar situation but really started to embrace the Meraki "easyness".

CptnCrnch

As far as I know, RF Profiles can only be assigned to APs, so I guess this doesn't work.

CptnCrnch

Great job gentlemen! Keep 'em coming! 🙂

CptnCrnch

I had the chance to participate at Cisco Live Barcelona. CTF is so much fun and highly recommended! 😎

CptnCrnch

What's the color of the Power LED? Static orange? Otherwise it looks like it doesn't have cloud connectivity: https://documentation.meraki.com/MX/Installation_Guides/MX450_Installation_Guide#Ports_and_Status_Indicators Also, what's the status of the machine on your Dashboard?

CptnCrnch

CCNA? Whoa, it's been a loooong time since then 😉

CptnCrnch

His idea...possibly (and hopefully) not his best one though.

CptnCrnch

You'll find the switches IP address on its information page in the Dashboard. In case of a Layer 3 switch, it will be the highest Vlan interface. Many customers simply add the whole management network to their RADIUS server so they don't have to fiddle around with static DHCP leases etc.

CptnCrnch

@CptnCrnch is your username a nod to the 2600hz whistle? Good catch @BrandonS!

CptnCrnch

I really hope to be able to see Mt. Fuji someday too! 🙂 Welcome to the forums!

CptnCrnch

As for the switch regarding 802.1x: https://documentation.meraki.com/MS/Access_Control/MS_Switch_Access_Policies_(802.1X) Unless you've also got Meraki Access Points, it definitely won't show SSID configuration, so I don't really know what you're refferring to with that.

CptnCrnch

I'm not Brandon (sorry 😉 ), but: yes

CptnCrnch

As so often with Meraki, it‘s documented quite nicely within the „fine manual“ 🙂 https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Upstream_Firewall_Rules_for_Cloud_Connectivity

CptnCrnch

Bonjour Jean-Philippe, bienvenue en club! 😎

CptnCrnch

Well, what kind of integration are your seeking with non-Meraki devices?

CptnCrnch

It's a 1 year license for a vMX (MX in Azure or AWS). What's the exact problem?

CptnCrnch

Another option would be having that endpoint being managed by MDM and force it to only connect to a specific SSID that way.

CptnCrnch

No. You could only prevent that endpoint from connecting to the SSIDs it should not connect to, e.g. by using Authentication (802.1x / MAB)

CptnCrnch

Good finding, thanks for the update!

CptnCrnch

Geo blocking itself is one of the most useless features any firewall nowadays can have...

CptnCrnch

Upgrade went smoothly last night, looking good so far. Had a strange problem with one of my clients that had some network issues over the day. Currently even that one is running flawlessly. 😎

CptnCrnch

Not natively, as far as I know. You'll need to sync your GSuite directory to something like https://jumpcloud.com/product/cloud-radius and leverage RADIUS for user authentication.

CptnCrnch

Well, the screenshot shows something like MX84 / MX100, which doesn't provide any PoE ports. Also you don't get to configure the port speed. MX is not an MS after all. 😉

CptnCrnch

Community Record

Badges