I discovered that the EdgeMax router dhcp service is, by default. not running in Authortative mode. Since it wasn't, here is what was happening.
- Client connects and issues a DHCP request with a requested IP address (the last one I was using).
- EdgeMax running in non-authortative mode ignores the request because it had a requested address that didn't match the address scope the EdgeMax is configured for.
- Client requestes a number of times before it finally times out.
- After timeout client issues a generic address request without an address
- EdgeMax responds to request with an address
- Client uses the address and is operational.
I issued this command...
set service dhcp-server shared-network-name DHCP-POOL-NAME authoritative enableSwitching the EdgeMax DHCP service to authortative mode the timeout went away. Here's what happens, and there is no timeout or delay involved.
- Client connects and issues a DHCP request with a requested IP address (the last one I was using).
- EdgeMax running in authortative mode denies the request.
- Client issues a new request for an address from the server
- EdgeMax responds to request with an address
- Client uses the address and is operational.
Reference for Non-Authortative and Authortative differences.
Thank you! Was scratching my head over this one. I love it when someone's taken the time to post a quirky issue and its resolution to their blog!
ReplyDeleteThanks you Jeremy! I discovered this problem myself today and your post 100% confirms this problem. From now on I'll always do my DHCP config from CLI on EdgeRouter. This behavior is true for EdgeRouter Pro, EdgeRouter Lite and the new EdgeRouter X as far as I know.
ReplyDeleteThank you! Was scratching my head over this one. I love it when someone's taken the time to post a quirky issue and its resolution to their blog router address
ReplyDelete