Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About netper
Community Record
11
Posts
2
Kudos
1
Solution
Badges
@alemabrahao Im not sure how is this going to help, if the user is authenticated he will still be able to use the MR port. Correct?
... View more
@ww would SecurePort also help in my case? I dont want someone to take the cable of the MR and plug it in to his laptop for connectivity. If I understood correctly, SecurePort will be useful if someone connects a rouge MR/Meraki device?
... View more
Hey all, I have an all-around Meraki environment including MXs MS switches and MRs. I wanted to know if there's a way for me to block anyone who tries to remove a cable from my access point and use it on his laptop. Currently the AP's port on the switch is set to 'trunk' and 'open' access policy. When I tried to change the AP to specific MAC addresses it didnt allow any client which is not the AP to use the wifi broadcasted by the AP. Is Meraki offering any protection to this case?
... View more
Just updating that as predicted this was the issue. One of the switches in the middle which were managed by outside source didnt have the VLAN. Thanks all
... View more
When connecting to the MX itself and setting the port as 'access' I did get the correct address. When connected to the MS switch, I got APIPA. We do have some temporary switches in the middle, but should all be set to trunk. As I now know that the problem lies somewhere in between the MX the switch I will start from there.
... View more
I captured packets on the AP that a test client was connected to. I think it doesn't go past the Discover part of the request.
... View more
Hmm I did try that in one of the MS switches and no luck still not getting proper IP address.
... View more
Native VLAN kept at default '1'. No firewall rules at all (only allow any any) it's a new SSID. DHCP guard is disabled on that SSID, also others.
... View more
Yes The uplink from the MS switch to the MS is configured as TRUNK and all vlans as well.
... View more
Hey, Yes, the ports for the APs are in TRUNK mode and allowing all VLANS. I do have other VLANs that were configured before and are working on wired and wireless connection (different SSID)
... View more
Hey guys, I'm trying to understand where my issue is when creating a VLAN and assigning it to a wireless network. My setup currently is MX68 connected to > MS250 and connected to MR44 APs. Currently, devices connecting to the new SSID with the VLAN assigned are getting APIPA and from the AP event logs I'm getting the following error ''Client made a request to the DHCP server, but it did not respond." I did the following when creating the new VLAN and assigning to SSID: - Under Security & SD-WAN > Addressing & VLANs - I've created a new VLAN, assigned the MX IP and range of the subnet. (For now, all the ports on the MX are on TRUNK mode allowing all VLANS) - Under Security & SD-WAN > DHCP - I've made sure the new VLAN shows up and the DHCP server is running. - Moving to Wireless > SSIDs - Created a new SSID and under Client IP and VLAN did the following. On the AP itself I see DHCP and ARP failures. Would really appreciate your help as I must be missing something.
... View more
Labels:
- Labels:
-
Installation
-
Other
-
SSID
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 8378 |
© 2024 Cisco Systems, Inc.
