Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Become a member of the Cisco Meraki Community today
Get answers from our community of experts in record time.
Join nowAbout Marlon
Marlon
Here to help
Member since Jun 13, 2019
May 16 2024
Community Record
20
Posts
2
Kudos
0
Solutions
Badges
May 12 2024
4:20 PM
Hi @GIdenJoe , this is not the case that you are on the inside of the network, Site A and Site B are not built with Site-to-Site VPN or AutoVPN, Client is having issues on Site B trying to connect VPN to Site A. Any other thoughts thanks.
... View more
May 12 2024
5:47 AM
Hi Community, Did anyone meet this issue below? or anyone can help with this issue. I have two Meraki Sites: Site A and Site B. Both Sites I have setup Client VPN with IPSec. The Client VPN is working well when you are at Home or at any other places except on another Meraki Site. For example, Clients on Site B try to connect Client VPN of Site A, the connection wont' be built up successful. Same issue clients on Site A try to connect Client VPN of Site B, the connect won't be built up, normally it comes with this error below. This issue only happens on a site that is on Meraki Network, both clients VPN is working at home. On Site A I enabled Site-to-Site VPNs, but on Site B Site-to-Site VPN is not enable, not sure if the Site-to-Site VPN could cause any issues. Any ideas? Thanks. Regards, Marlon
... View more
Labels:
- Labels:
-
Client VPN
-
Firewall
Jan 20 2024
3:29 PM
When you say "create a Layer 3 Interface in the MX", I assume you mean create a Static Route to route the Vlan subnet to a Layer 3 Interface?
... View more
Jan 20 2024
3:27 PM
Hi @ww @alemabrahao , I think I find a right article (MX and MS Basic Recommended Layer 3 Topology) to describe my scenario. In this topology the Vlan is created on layer3 Switch only and not go through MX. I think this is what I want. Thanks anyway. https://documentation.meraki.com/Architectures_and_Best_Practices/Recommended_Topologies/MX_and_MS_Basic_Recommended_Layer_3_Topology
... View more
Jan 20 2024
3:35 AM
Thanks, how to create a layer 3 interface in MX? Please also see what I just added on my first question and see if you can help? Thanks.
... View more
Jan 20 2024
3:31 AM
Hi @DarrenOC , Thanks. Let me describe what I want to achieve on MS225. I want to create a new Vlan e.g.24 by creating an Interface on MS225, and setup a DHCP Relay to MX Firewall. On MX, I setup a Static Route to go to Vlan 24 Subnet via the IP of MS225, and I Enable DHCP on this Static Route with the Gateway of the Interface created on MS225. Vlan 24 is not created on MX, I want this MS225 to create Vlan 24 and apply DHCP Relay to MX. Is this logic correct? Any issues? Regards, Marlon IT Department
... View more
Jan 20 2024
3:09 AM
Hi Team, This may be a dumb question but I haven't got any confirmations yet. Can Vlan be created on Meraki Layer 3 Switch? I have a MS225-48P Switch, it's saying this Switch is a Layer 3 Switch that can do DHCP-Relay. See below for example I create an Interface for Vlan e.g.24 but his Vlan 24 is not created on MX Firewall. If I apply this interface setting on this Vlan, will this Vlan be created and existing on the Network or not? Thanks. Regards, Marlon
... View more
Labels:
- Labels:
-
Interfaces
-
Layer 3
I just did a bit more studying and I am clear now. I think the process is this: Clients send untagged DHCP request to the Port, as the Port is setup a Native Vlan 10, Switch will know that the untagged request is from Native Vlan 10 because they are all untagged. When Switch forward that DHCP to another Trunk Port with a different Native Vlan e.g. 20, Switch will tag the request to the Original Native Vlan 10 and forward that request to Vlan 10's Gateway, from Gateway it will use DHCP relay to find the DHCP server. I was a bit confused on the process when a DHCP requests sent from on one Port with a Native Vlan and passed to another Port with a different Vlan, the Switch actually will tag the request with the origianl Native Vlan. It's all make sense now. Thanks.
... View more
Thanks @alemabrahao , I should read the article first (was going to read after I posted). The Article actually tell you why on the first page, It's saying "untagged traffic to the upstream switch port and then DHCP discover in the configured native VLAN". To be honest, I am still a bit confused, why DHCP Discover in the Configured Native VLAN? If you can explain that would be great, if not I will do more research myself. Thanks so much.
... View more
Thanks Joe, I actually setup Bridge Mode on the SSID, but how the Tag happens when I setup Native Vlan 10 on the Switch Port. My understanding Native Vlan won't be tagged, how does the Switch know this port connects to Vlan 10. It's easy to understand when I setup the Switch Port to be Access (e.g. access Vlan 10 only) to connect to AP, as Switch know on this port it connects to Vlan 10, when AP and clients request DHCP, the request will be sent to Vlan 10's Gateway, but when I setup the Port to be Trunk with Native Vlan 10, how does the Switch know clients from this port belongs to Vlan 10?
... View more
Hi, I am testing Meraki Access Point connections with Meraki Switch Port. The basic Connection is: I setup e.g. Vlan 1, Vlan 10, Vlan 11 on Core Switch, the DHCP server for each Vlan is setup on Meraki Firewall, but I setup DHCP relay on the Core-Switch to lead the DHCP request to the firewall. All the connections between Switch are setup as Trunk with Native Vlan1, but on the Port between Switch and AP, I setup Native Vlan to be 1, or 10, or 11. I realize on the Port that connect to AP, if I setup the Port to be Trunk and Native Vlan to 10 for example, the AP and all its WiFi clients will get Vlan 10's IP addresses. If I setup the Native Vlan to be 11 or other Vlan, the AP and clients will get that Native Vlan's IP. I didn't setup tagging on AP or Port, just this basic setting shown in the screenshot. Why APs get Native Vlan's IP address by DHCP? What's the Logic for this? How does the Switch know that AP and its client are belonging to that Vlan (Native Vlan)? Are there any risks of doing this way? I will be very grateful if anyone can help. Thanks. Regards, Marlon
... View more
Labels:
- Labels:
-
SSID
Sep 7 2023
7:24 PM
Hi @alemabrahao , Thanks for your work. I figured it out where to setup DHCP Relay on the HP Switch. This Switch is very weird, on the Web port it didn't give you option to setup DHCP Relay, but today I login via Telnet session and do show ip helper-address, I can see existing IP helper address for existing Vlan, and new Vlan I setup didn't have ip Helper-address. After I setup a new ip Helper-address for new Vlan, all working now, it makes all sense now. Thanks again for your help, this help a lot on identifying the issue.
... View more
Sep 6 2023
5:37 PM
Hi @alemabrahao , thanks for the Video, the HP 3800-24G-2SFP doesn't have the DHCP Relay menu, I am starting looking for other solutions. There is a Meraki Switch MS225 on the network and I searched this MS225 can do the DHCP Relay so I am planning to setup DHCP Relay on this MS225, but this MS225 is connecting to HP L3 Core Switch first, MS225 is not connecting to MX directly. My question: If I setup a new Vlan on MS225 and setup a DHCP Relay to point to MX Gateway, although MS225 is not directly connected to MX, will the DHCP Relay work?
... View more
Sep 6 2023
3:40 PM
1 Kudo
Hi Dimatt, thanks for you reply. The L3 Switch is not Meraki Swtich, it's HP 3800-24G-2SFP and I couldn't find a setting to setup DHCP. Also in this Meraki Example, the DHCP server is setup on the MX, not on the Layer 3 Switch. https://documentation.meraki.com/MS/Layer_3_Switching/Layer_3_Switch_Example I am thinking replacing the HP L3 Switch with Meraki L3 Switch for future, but at current stage I need to figure it out how the HP Switch does the DHCP Relay as I couldn't find any setting for DHCP Relay.
... View more
Sep 5 2023
9:04 PM
Hi @alemabrahao , thanks for the reply, I understand the DHCP Relay needs to be configured in L3 Switch, but I have gone through every menu on the HP L3 Switch Web page but couldn't find any place for DHCP Relay, unless there is management Portal I am not ware of that can configure Relay on this HP L3 Switch. Also could the default Route configured on L3 Switch be acting as DHCP Relay (IP Helper)?
... View more
Sep 5 2023
4:32 PM
Hi All, I am new to my company's Meraki Network and I want to figure it out how it works. My company Network is using this Topology in the article below https://documentation.meraki.com/Architectures_and_Best_Practices/Recommended_Topologies/MX_and_MS_Basic_Recommended_Layer_3_Topology The Layer 3 Switch is using HP 3800 and all the Vlans created on it. All the Static Routes are created on MX Appliance and each Route is setup with a DHCP Server to provide DHCP services to the clients. You can see between MX and Layer 3 Switch it is using an Access link, on Meraki Port is Access Port only Allow Native Vlan in this case is Vlan 50. 1. What I don't understand how DHCP Server give IP to downstream clients when MX is using Access Mode to connect Layer 3 Switch not using Truck Mode? should the Link to Trunk? 2. For example, a new client A in Vlan 1 want to get a IP from DHCP Servers of Static Route 1, Layer 3 Switch will forward the DHCP request to MX, but how MX decide which DHCP server to assign IP to Vlan 1? 3. I tried to create a new Vlan 3 on Layer 3 MX Switch with all the exact same setting as other Vlans, but somehow the client on the new Vlan 3 couldn't get an IP address from DHCP server, I am wondering where it is wrong. Any suggestions or any useful articles please share with me, Thanks first.
... View more
Sep 4 2023
7:20 PM
@Jesse , did you find out the solution in the end? I am having the exact the same issue and got stuck now.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 3980 |
© 2025 Cisco Systems, Inc.
