Issues with DHCP on 374.43 by Merlin and 374.43 Merlin Fork

[sojer2005]

Hello,
I am testing different versions of the firmware for my Asus N66U router.
Version 374.43 (FW by Merlin) and version 374.43 Merlin Fork by john are great when it comes to signal strength and range.
Unfortunately, I have noticed some errors in the log, which arise when you try to renewal IP address.


I have also tested the latest version 376.48 by Merlin and the original Asus FW (latest) - these error messages do not occur. The logs are clean.





Here is my log from 374.43:

Dec 14 01:41:02 miniupnpd[688]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Dec 14 01:41:02 miniupnpd[688]: Failed to get IP for interface eth0
Dec 14 01:41:02 miniupnpd[688]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 14 01:41:02 dnsmasq[667]: read /etc/hosts - 5 addresses
Dec 14 01:41:02 dnsmasq[667]: using nameserver 62.179.1.61#53
Dec 14 01:41:02 dnsmasq[667]: using nameserver 62.179.1.63#53
Dec 14 00:41:04 WAN Connection: ISP's DHCP did not function properly.
Dec 14 00:41:04 stop_nat_rules: apply the redirect_rules!
Dec 14 01:41:04 dnsmasq[667]: exiting on receipt of SIGTERM
Dec 14 00:41:05 dnsmasq[905]: started, version 2.69 cachesize 1500
Dec 14 00:41:05 dnsmasq[905]: asynchronous logging enabled, queue limit is 5 messages
Dec 14 00:41:05 dnsmasq-dhcp[905]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Dec 14 00:41:05 dnsmasq-dhcp[905]: DHCP, sockets bound exclusively to interface br0
Dec 14 00:41:05 dnsmasq[905]: read /etc/hosts - 5 addresses
Dec 14 00:41:05 dnsmasq[905]: using nameserver 62.179.1.61#53
Dec 14 00:41:05 dnsmasq[905]: using nameserver 62.179.1.63#53
Dec 14 00:41:05 dnsmasq[905]: read /etc/hosts - 5 addresses
Dec 14 00:41:05 dnsmasq[905]: using nameserver 62.179.1.61#53
Dec 14 00:41:05 dnsmasq[905]: using nameserver 62.179.1.63#53
Dec 14 00:41:05 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Dec 14 00:41:05 dnsmasq[905]: exiting on receipt of SIGTERM
Dec 14 00:41:05 dnsmasq[924]: started, version 2.69 cachesize 1500
Dec 14 00:41:05 dnsmasq[924]: asynchronous logging enabled, queue limit is 5 messages
Dec 14 00:41:05 dnsmasq-dhcp[924]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Dec 14 00:41:05 dnsmasq-dhcp[924]: DHCP, sockets bound exclusively to interface br0
Dec 14 00:41:05 dnsmasq[924]: read /etc/hosts - 5 addresses
Dec 14 00:41:05 dnsmasq[924]: using nameserver 62.179.1.61#53
Dec 14 00:41:05 dnsmasq[924]: using nameserver 62.179.1.63#53
Dec 14 00:41:05 rc_service: udhcpc 906:notify_rc stop_upnp
Dec 14 01:41:05 miniupnpd[688]: shutting down MiniUPnPd
Dec 14 00:41:05 rc_service: udhcpc 906:notify_rc start_upnp
Dec 14 01:41:05 miniupnpd[940]: HTTP listening on port 44709
Dec 14 01:41:05 miniupnpd[940]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 14 01:41:06 dhcp client: bound 66.66.66.666 via 66.66.66.6 during 172800 seconds.
Dec 14 00:41:10 WAN Connection: WAN was restored.





Thanks

 

[RMerlin]

These log entries are just the usual messages you get when the WAN interface goes down. You didn't post the section that shows where the WAN interface actually does go down, just before that.

 

[sojer2005]

These log entries are just the usual messages you get when the WAN interface goes down. You didn't post the section that shows where the WAN interface actually does go down, just before that.

Hi,
there is nothing before. No messages about WAN interface going down.

My DHCP lease expires in 49 minutes (Internet status window), I will post the new log after that.

 

[sojer2005]

My DHCP lease expires in 49 minutes (Internet status window), I will post the new log after that.

The DHCP lease expired a little bit earlier.
The log after that:

Dec 14 10:01:40 dnsmasq-dhcp[542]: DHCPACK(br0) 192.168.1.42 xxx Mac-mini
Dec 14 10:20:14 miniupnpd[558]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Dec 14 10:20:14 miniupnpd[558]: Failed to get IP for interface eth0
Dec 14 10:20:14 miniupnpd[558]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 14 10:20:14 dnsmasq[542]: read /etc/hosts - 5 addresses
Dec 14 10:20:14 dnsmasq[542]: using nameserver 62.179.1.61#53
Dec 14 10:20:14 dnsmasq[542]: using nameserver 62.179.1.63#53
Dec 14 10:20:18 dnsmasq[542]: read /etc/hosts - 5 addresses
Dec 14 10:20:18 dnsmasq[542]: using nameserver 62.179.1.61#53
Dec 14 10:20:18 dnsmasq[542]: using nameserver 62.179.1.63#53
Dec 14 10:20:18 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Dec 14 10:20:18 dnsmasq[542]: exiting on receipt of SIGTERM
Dec 14 10:20:18 dnsmasq[713]: started, version 2.69 cachesize 1500
Dec 14 10:20:18 dnsmasq[713]: asynchronous logging enabled, queue limit is 5 messages
Dec 14 10:20:18 dnsmasq-dhcp[713]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Dec 14 10:20:18 dnsmasq-dhcp[713]: DHCP, sockets bound exclusively to interface br0
Dec 14 10:20:18 dnsmasq[713]: read /etc/hosts - 5 addresses
Dec 14 10:20:18 dnsmasq[713]: using nameserver 62.179.1.61#53
Dec 14 10:20:18 dnsmasq[713]: using nameserver 62.179.1.63#53
Dec 14 10:20:18 rc_service: udhcpc 695:notify_rc stop_upnp
Dec 14 10:20:18 miniupnpd[558]: shutting down MiniUPnPd
Dec 14 10:20:18 rc_service: udhcpc 695:notify_rc start_upnp
Dec 14 10:20:18 dhcp client: bound 66.66.66.666 via 66.66.66.6 during 172800 seconds.
Dec 14 10:20:18 miniupnpd[730]: HTTP listening on port 60168
Dec 14 10:20:18 miniupnpd[730]: Listening for NAT-PMP/PCP traffic on port 5351

-----------------------------------------------------
Now I have rebooted the router and my DHCP lease is 1 hour. It says it will expire in about 51 minutes. I have noticed actually DHCP lease expires earlier (about half that time). After that DHCP lease is much longer (2 days).

When I am using firmware 376.48 the logs are empty during DHCP expires and renewals.

 

[RMerlin]

I don't see anything wrong in these log entries. The Wan IP expires, and 5 seconds later a new lease gets allocated, so everything looks perfectly normal to me.

Dec 14 10:20:18 dhcp client: bound 66.66.66.666 via 66.66.66.6 during 172800 seconds.