What's new

"DHCP did not function properly"

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

GunnerGGA

Occasional Visitor
Once in a while I have the "DHCP did not function properly" error. If I don't do anything, it usually fixes itself in around 5 minutes. Below is the log. Anything I can try to keep the internet stays connected? What is the router doing at the time?

I wonder where I can start to debug this issue. WISP internet. There is a mimosa power-over-ethernet power adapter on the outlet, which does not seem to have its own IP (to the best of my knowledge).

I wonder if I should set the DHCP query to aggressive/normal/continuous.

Oct 4 04:44:40 wlceventd: wlceventd_proc_event(499): eth7: Auth xxx, status: Successful (0)
Oct 4 04:44:40 wlceventd: wlceventd_proc_event(509): eth7: ReAssoc xxx, status: Successful (0)
Oct 4 04:44:48 wlceventd: wlceventd_proc_event(481): eth7: Disassoc xxx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 4 04:44:48 wlceventd: wlceventd_proc_event(481): eth7: Disassoc xxx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 4 04:44:58 miniupnpd[2931]: upnp_event_process_notify: connect(192.168.50.121:2869): Connection timed out
Oct 4 04:44:58 miniupnpd[2931]: upnp_event_process_notify: connect(192.168.50.121:2869): Connection timed out
Oct 4 04:44:58 miniupnpd[2931]: upnp_event_process_notify: connect(192.168.50.121:2869): Connection timed out
Oct 4 04:50:00 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Oct 4 04:50:03 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
Oct 4 04:51:20 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Oct 4 04:51:22 WAN Connection: ISP's DHCP did not function properly.
Oct 4 04:51:22 nat: apply redirect rules
Oct 4 04:51:23 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
Oct 4 04:51:26 WAN Connection: Ethernet link up.
Oct 4 04:51:26 rc_service: wanduck 1355:notify_rc restart_wan_if 0
Oct 4 04:52:01 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Oct 4 04:52:03 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
Oct 4 04:52:06 WAN Connection: Ethernet link up.
Oct 4 04:52:06 rc_service: wanduck 1355:notify_rc restart_wan_if 0
Oct 4 04:53:01 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind xxx , status: 0, reason: Unspecified reason (1)
Oct 4 04:53:01 wlceventd: wlceventd_proc_event(499): eth6: Auth xxx, status: Successful (0)
Oct 4 04:53:01 wlceventd: wlceventd_proc_event(527): eth6: Assoc xxx, status: Successful (0)
Oct 4 04:54:58 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Oct 4 04:54:58 wan: finish adding multi routes
Oct 4 04:54:58 miniupnpd[2931]: shutting down MiniUPnPd
Oct 4 04:54:58 miniupnpd[23683]: version 1.9 started
Oct 4 04:54:58 miniupnpd[23683]: HTTP listening on port 56105
Oct 4 04:54:58 miniupnpd[23683]: Listening for NAT-PMP/PCP traffic on port 5351
Oct 4 04:55:01 WAN Connection: WAN was restored.
Oct 4 04:55:03 kernel: The For ALL DEVICES flag of Prof 1 has been set to DISABLE
Oct 4 04:55:03 kernel: The For ALL DEVICES flag of Prof 2 has been set to DISABLE
Oct 4 04:55:03 kernel: The For ALL DEVICES flag of Prof 3 has been set to DISABLE
Oct 4 04:55:03 kernel: Successfully alloc ctrie: state num=21, mem=420
Oct 4 04:55:03 BWDPI: fun bitmap = 50b
Oct 4 04:55:04 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Oct 4 04:55:04 dhcp client: bound xxx/255.255.255.0 via xxx for 28800 seconds.
 
Oct 4 04:50:00 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Oct 4 04:50:03 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
Oct 4 04:51:20 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Oct 4 04:51:23 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
Oct 4 04:52:01 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Oct 4 04:52:03 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
Your issue is nothing to do with DHCP, it's because the physical connection to the router's WAN port was disconnected (3 times). My guess would be that your ISP gateway device was restarted.
 
Your issue is nothing to do with DHCP, it's because the physical connection to the router's WAN port was disconnected (3 times). My guess would be that your ISP gateway device was restarted.

You mean the connection between the router's WAN port and the ISP's device is down?

"Port: 3 (phyId: c)" is the ID for the WAN port?

Obviously I did not physically disconnect the WAN port. If so, I can try using a different cable and see if it makes a difference.
 
You mean the connection between the router's WAN port and the ISP's device is down?

"Port: 3 (phyId: c)" is the ID for the WAN port?

Obviously I did not physically disconnect the WAN port. If so, I can try using a different cable and see if it makes a difference.
Yes, the WAN port. Can you log into whatever the device is that the router's WAN cable is connected to and check its logs?

Maybe "physical" was the wrong term, perhaps "electrical" would have been better. The point being that it's not a software/protocol issue (like DHCP).
 
You mean the connection between the router's WAN port and the ISP's device is down?

"Port: 3 (phyId: c)" is the ID for the WAN port?

Obviously I did not physically disconnect the WAN port. If so, I can try using a different cable and see if it makes a difference.
"DHCP did not function properly" is what my Asus routers say when my modem is attempting to acquire DHCP address from the modem. Otherwise is says "No Connection" when I turn off the main ISP's modem completely and then turn it on. I turn my main router off sometimes to test and activate the "hot standby" Fail Over/Fail back feature for my (backup) secondary ISP's modem.

Try setting your DHCP query to Normal instead of the default of Aggressive and see if that makes a difference. Post back here with your results. You can also try turning off your router and unplug all your Ethernet cords from the router. Then turn off your modem and wait for five minutes and then turn on your router and wait five minutes, then plug your Ethernet devices in one by one. You do this to prevent any devices from somehow registering and acquiring a DHCP address from your ISP modem. It ensures only your router acquires the address first.

I actually had this happen in the past where another device was acquiring the address instead of the router and the ISP tech support recommended this solution and it always has worked for me. This problem would usually happen when after installing a new router but would be solved with the sequential power off/power on solution above. You can call your ISP's tech support and ask them to test the connection to your modem and the check the MAC address of the main router or device upstream that it is connecting to. Of course try using a different Ethernet Cat 6 or better cable as well. Good luck and update us when you figure out if this or another solution mentioned here works.
 
Last edited:

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top