About ww

ww

https://documentation.meraki.com/MR/Encryption_and_Authentication/IPSK_Authentication_without_RADIUS Or https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Splash_Page#Creating_a_Group_Policy_to_Bypass_a_Splash_Page

ww

the stp is using a native vlan. So as long you make sure you never have a loop (by the network admin/user error), and dont want/use redundancy based on stp blocking on your network, it should work.

ww

Remove the rules from the dashboard using you phone on lte. Or connect your laptop to the router or another network. But you already made it to the internet posting here... In case the switch is offline, (Which should not happen because there is a explicit allow at the acl to the meraki ip addresses) you could factory reset it after you remove the rule from the dashboard https://documentation.meraki.com/General_Administration/Support/Resetting_Cisco_Meraki_Devices_to_Factory_Defaults#MS_Access_Switches

ww

I think that is "by client" and that is not supported on switches https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies#By_Client

ww

Some api calls do not add but replace the current rule. Like the fw rules you need to put all rules at once. I suppose this api call has the same behavior

ww

Basically the options you have are these,but its more like telling who is allowed: https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Switch_Ports#Port_configuration MAC allow list: Only devices with MAC addresses specified in this list will have access to this port. Up to 20 MAC addresses can be defined. Sticky MAC allow list: The switch will dynamically learn the MAC addresses of devices connected to the port and place the address in the MAC Whitelist. The administrator can define the size of this list. When this list is full, all subsequent devices will be denied access to this port. It can take up to 5 minutes for the learned MAC to appear in dashboard. User-defined access policy: Administrators may define a policy for authentication via 802.1x or MAB. Learn more about access policies here.

ww

No, a hub connect to all other hubs

ww · Does the other side have a route back to 10.0.1.0/24 ... View more

Does the other side have a route back to 10.0.1.0/24

ww

You are not blind.;) There is/was a gui bug that it does not show bgp learned routes in some networks. Could that be the difference?

ww

You can contact support to push the update.

ww

It should not work because meraki statefull fw is outbund and if a inbound session is iniated its a allowed session in the firewall. If it works then they should remove this part from the documentation. "As such, the MX cannot block VPN traffic initiated by non-Meraki peers"

ww

But that is traffic initiated by you. Not by the other 3rd party

ww

No. Its says "As such, the MX cannot block VPN traffic initiated by non-Meraki peers."

ww

That does not work, you cant block incoming traffic with the site2site vpn firewall. You could try using a the group policy and assign it to the local vlan. Gp uses stateless firewall rules

ww

Yes i noticed yesterday. Previous it was only available at the local status page

ww

On mx you cant limit the vlan. You can only limit per client/session

ww

Yes that would work. From dc2 you also need to set the static routes (or at least the 0.0.0.0 one) to be part of the vpn. This will automatically also advertise these routes to your spokes

ww

You could set a color in the <a https://htmlcolorcodes.com/tutorials/html-link-color/ Or Change the color of "a, a:visited, a:active {color: #fff; text-decoration: none;}" in the main.css https://documentation.meraki.com/MR/MR_Splash_Page/Custom_Splash_Page_Themes#Editing_the_Custom_Theme's_HTML_Files

ww

If you bought it new, ask the company that sold it. If you already owned it you could try support and ask which org its in

ww

Try upgrading to 16.16.7. If it then still happens, contact support.

ww

Did the wan port get a link or not?

ww

So can you plug the isp in the switch. And use a sfp+ port of the switch to connect to the sfp+ wan of the mx to see if you get a link and update the mx.

ww

What if you plug the utp in one if the normal ports of that switch? Or does the switch have a Sfp+ port so you can test with a sfp+dac cable between the mx and switch? Or can you connect the mx temporary directly to the isp to see if you can get it to update

ww

Where can we find this info regarding this kind of issues?

ww

Splashaccess can do a lot of things. You could take a look at this https://apps.meraki.io/en-US/apps/380853/splash-access https://community.meraki.com/t5/Marketplace-Announcements/Announcing-our-1st-Cisco-Meraki-Ecosystem-Partner-of-the-Month/ba-p/175727

ww

Community Record

Badges