topic Re: Help with DHCP lease error in Wireless

Help with DHCP lease error

RayR — Tue, 30 Apr 2024 02:22:09 GMT

Trying to turn up a new network - and getting this error message: xtra: no_offers_received, vap: 0, vlan: 1. Can't figure out why. Appreciate guidance.

Re: Help with DHCP lease error

Ryan_Miles — Tue, 30 Apr 2024 03:04:47 GMT

Need more info on the entire config/topology. That event log just means the DHCP DORA process didn't happen. Doesn't necessarily mean there were really no DHCP leases available.

Re: Help with DHCP lease error

RayR — Tue, 30 Apr 2024 03:57:58 GMT

Physical config: Client - to MR36 - to MX67 - to Comcast

Logical config: SSID on MR maps to VLAN 1. Address assignment on MR set to "external" - as I want to use DHCP on MX - not MR. Fails...

If I change to Meraki "AP assigned" - things work - but that's not what I had wanted - as I want to use multiple vlans in the network - which I belive means I need to use DHCP from MX - not from MRs - correct?

Re: Help with DHCP lease error

Ryan_Miles — Tue, 30 Apr 2024 04:09:41 GMT

Two of the first issues I see.

Your SSID firewall policy blocks all traffic to private subnets. https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/MR_Firewall_Rules

You use LAN 2 on your MX. That is only configured to allow VLAN 2 (trunk native 2, allow 2).

Re: Help with DHCP lease error

RayR — Tue, 30 Apr 2024 13:15:30 GMT

I corrected SSID FW issue and MX port issue and returned to “external DHCP” on wireless config (as I want MR clients to get DHCP leases from the MX - which I believe appropriate for running multiple vlans?).

Now I get an address / connection to MR – but no internet connection.

Advice?

Re: Help with DHCP lease error

Ryan_Miles — Tue, 30 Apr 2024 14:07:13 GMT

Don't tag your native VLAN on the SSID.

If you want clients of the SSID to be on VLAN 1 then either tag the switchport (MX LAN port in your case) to something other than 1. Or, on the SSID disabled tagging and clients will then be put onto the native VLAN of the LAN port.

Re: Help with DHCP lease error

RayR — Tue, 30 Apr 2024 14:48:03 GMT

Thanks. I'll give that a try when I get back to my desk later today.

Since I want to run multiple ssids each in a separate VLAN, I assume the first of your two suggestions is the way to go?

By the way, just out of curiosity, I'm wondering why the default for the lan port couldn't be the same?

Any going to try later today. Thanks

Re: Help with DHCP lease error

RayR — Tue, 30 Apr 2024 15:11:00 GMT

Changed mx lan port to. "Drop untagged traffic" and now that works fine - THANKS

A follow up if you don't mind?

I assume if I map a port on the mr36 to an SSID, traffic that comes in on that port will be tagged in the VLAN associated to the SSID- correct?

Re: Help with DHCP lease error

Ryan_Miles — Tue, 30 Apr 2024 20:15:26 GMT

A wired port on the MR36H should behave just like wireless clients on the mapped SSID.

Re: Help with DHCP lease error

RayR — Tue, 30 Apr 2024 22:00:54 GMT

Thanks