Meraki

AreEyePea

I have created a new VLAN 120. I have created a DHCP server and have tagged the new SSID to vlan 120. From the MX to the APs, every port is trucking "All Vlans" with the native being 1. When I connected to the new SSID, I am not getting a DHCP address, just a 169.254. Do I need to specific VLAN 120 instead of "all vlans" on all the truck ports incuding the MX? That is the only thing I can think of that is not getting this to work.

Thanks for the help!

Mloraditch

Is there a switch involved or are the APs plugged directly into the MX? Does the SSID possibly have the Local LAN firewall rule set to deny?

SSID is set to the below?:

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

AreEyePea

Yeah there are 3 MS225. Each uplink is a trunk port with native vlan 1 and allowed vlans all.

The LAN firewall rule is set to allow. And yes the the SSID is configured just like that.

Do I need to change instead of all vlans, set the allowed vlans to each one ex( 1,20,120) but I feel like All vlans should pick that up

Mloraditch

All vlans is fine, so the uplinks to the APs are trunk native vlan 1, and all allowed, an the uplinks between the switches and up to the MX are the same? Did you check addressing and vlans on the mx and make sure it matches?

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

AreEyePea

Yeah, all ports are trucking native VLAN 1 and allowed all VLANs on MX and the switches.

Mloraditch

If you do a packet capture of the MX lan port and the AP Uplink do you see the DHCP requests for VLAN 120?

If you statically IP something on wireless on vlan 120, does it work?

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

alemabrahao

One question: Is the MX acting as the DHCP server?

If not, have you configured DHCP relay?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

AreEyePea

Yeah the MX is the dhcp server. It is working as the dhcp server for the other vlans.

alemabrahao

Are you sure the uplinks between MXs, switches, and APs are all configured as trunks, tagging all VLANs?

The DHCP service is very basic and simple; there's no secret to it.

If I were you, I would double-check to ensure the trunks are configured correctly.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

MarcP

Only way is to verify all over again...

MX port and DHCP settings, MS´s uplinks and MS-Port to MR.

Verify the access control:

Verify MR´s Port:

Meraki

Community

Vlan Tagging

Vlan Tagging