Meraki

PhilipDAth · ‎Oct 29 2018

Is this an AD account? Do they perhaps need to login as domain\user? And to be specific. in your packet capture you sure the RADIUS server send an ACCESS_ACCEPT message?

PhilipDAth · ‎Oct 29 2018

You can apply the "Blocked" group policy, which will prevent them from accessing anything. https://documentation.meraki.com/MX/Group_Policies_and_Blacklisting/Blocking_and_Whitelisting_Clients Removing just a single client from the client monitor is not really possible. You could possibly use the GPDR data privacy feature. https://documentation.meraki.com/zGeneral_Administration/Privacy_and_Security/Meraki_Data_Privacy_and_Protection_Features

PhilipDAth · ‎Oct 27 2018

I like Pizza @MRCUR.

PhilipDAth · ‎Oct 27 2018

Try making a wish for "konami" and then scroll down a little bit.

PhilipDAth · ‎Oct 26 2018

No one should be using WEP anymore. Use WPA2 Enterprise mode instead.

PhilipDAth · ‎Oct 25 2018

Meraki does not prevent you changing ownership @Jack. The old owner has to remove the kit from their dashboard so that the new owner can claim it. What Meraki does stop stolen kit from being re-used. If you can't get the "previous" (claimed) owner to remove the kit from their Dashboard then I would say it is pretty dodgy, and should not be allowed by Meraki.

PhilipDAth · ‎Oct 25 2018

From an environmental view; why not send the old kit to a scrap metal dealer? That's what we do.

PhilipDAth · ‎Oct 24 2018

You can't do this on Meraki switches. What you can do is put a point to point /30 link between the routers, and let the routers handle the policy routing.

PhilipDAth · ‎Oct 24 2018

This happens when the Meraki system tries to send data to your solution, and it experiences a number of errors or it takes a long time to respond. This causes it to give up. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Troubleshooting_the_Scanning_API Endpoint is taking too long to respond If an endpoint is taking an exceptionally long time - 500ms or longer - to respond to a POST, that endpoint's information will be dropped without being sent. It is recommended that applications separate processing of incoming Scanning API data from data routing for this reason.

PhilipDAth · ‎Oct 23 2018

Typically you would use trunk links between your Meraki switches and your 9300. When on the Meraki switch you configure the ports that users plug into as access ports, in whatever VLAN they should be using.

PhilipDAth · ‎Oct 23 2018

Remove the static route, that is definitely not the right thing. Because the 192.168.1.0/24 subnet is directly connected, you should be able to just browse to the ISP router. This is assuming you don't have a full VPN tunnel configured.

PhilipDAth · ‎Oct 23 2018

This is the Microsoft CVE relating to it. https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8333 If you have the specific updates installed then I would say you should be safe to whitelist the threat.

PhilipDAth · ‎Oct 22 2018

I haven't had that one fire - so I think that is bad news. Which snort signature is it (the number)?

PhilipDAth · ‎Oct 22 2018

If you hover your mouse over it in the dashboard what does it say?

PhilipDAth · ‎Oct 22 2018

Fibre modules don't support speed negotiation.

PhilipDAth · ‎Oct 21 2018

Some clients can not handle complex passwords. For a test, try making the password simple.

PhilipDAth · ‎Oct 21 2018

That subnet is fine. Have you configured the link between the switches as trunk ports?

PhilipDAth · ‎Oct 21 2018

You should not need to enable multicast routing. Is the Lighting system connected to the MS350 by chance? If so, you should just need to create a layer 3 interface on that switch, with just the IGMP querier turned on. I don't think the MS120's will support creating a layer 3 interface.

PhilipDAth · ‎Oct 19 2018

It would result in the stack being in a permanent broken state but it would work. I wouldn't do it. You are asking for problems.

PhilipDAth · ‎Oct 19 2018

If you want to stack them use two stacking cables. Otherwise you could just connect then with an Ethernet cable.

PhilipDAth · ‎Oct 18 2018

Ohh look at that! A fancy new Meraki notebook for being member of the month. Thanks everyone for your support.

PhilipDAth · ‎Oct 18 2018

Wahoo! I got my bag of goodies today for winning the community vote for my WiFi design.

PhilipDAth · ‎Oct 18 2018

I'll guess the Meraki AP is expecting to see a 1:1 mapping between a WiFi connection and a client connected. Certainly the whole dashboard is setup that way. In your case, you are presenting multiple clients per connection (WGB+WIN10). I'm guessing this is not a supported configuration. I'm guessing it will never be a supported configuration. You are going to need to use Meraki MESH mode, with Meraki kit. An option for you to consider to replace the WGB is an MR30H. They are more intended for Hotels and accomodation and the like (where you put one in each room), but it should fit your need. https://meraki.cisco.com/products/wireless/mr30h You could also consider a low cost MR20. https://meraki.cisco.com/products/wireless/mr20

PhilipDAth · ‎Oct 17 2018

Anything you run inside of a VDI session, including a web browser, will use the Internet where the server hosting the VDI sessions is located. To use local Internet break out out need to run a web browser on a local machine, not a VDI session.

PhilipDAth · ‎Oct 17 2018

Yes that is fine.

About PhilipDAth

PhilipDAth

Philip D'Ath

Community Record

Badges