[Release] Asuswrt-Merlin 384.13 is now availableIf you get a chance to verify that....
I double checked my backport....looks in sync with Merlin.
I don't want to reflash myself.
[Release] Asuswrt-Merlin 384.13 is now availableIf you get a chance to verify that....
I double checked my backport....looks in sync with Merlin.
I take back me not seeing it.....I also see it during startup and shutdown.....The only time I see this in my logs is when the WAN interface is offline. So that's at router startup or shutdown, or when I unplug the WAN cable.
And mdns.While we're on the subject of daemons listening on 0.0.0.0, I would love to have a way to disable lpd and u2ec permanently.
Strangely, it is the same as the LAN MAC address (seems to be a Broadcom quirk) unless you have changed it on the WAN page (MAC Address/MAC Clone).
It's also written on the white label on the back of the router.
Is an unrecoverable feature of ASUS routers?Apr 18 01:07:48 WAN_Connection: ISP's DHCP did not function properly.
Apr 18 01:07:48 DualWAN: skip single wan wan_led_control - WANRED off
On my PC (Laptop). Or on my iPhone.Where are you running the TunnelBear or NordVPN client? On the Ubiquity or on your PC?
Sorry, you'll have ask for help on the Ubiquity forums.On my PC (Laptop). Or on my iPhone.
It generally means your router isn’t getting an IP address from your ISP’s DHCP server.@john9527
John, please tell me the error that constantly appears in the system log:
Is an unrecoverable feature of ASUS routers?
Can't it be fixed?
Thank you in advance!
grep -i dhcp /tmp/syslog.log-1 /tmp/syslog.log | grep -v dnsmasq
Can this be fixed?admin@RT-N66U-B068:/tmp/home/root# grep -i dhcp /tmp/syslog.log-1 /tmp/syslog.lo
g | grep -v dnsmasq
grep: /tmp/syslog.log-1: No such file or directory
/tmp/syslog.log:Jan 1 03:00:23 WAN_Connection: ISP's DHCP did not function properly.
/tmp/syslog.log:Jan 1 03:00:37 rc_service: udhcpc 442:notify_rc start_firewall
/tmp/syslog.log:Jan 1 03:00:37 rc_service: udhcpc 442:notify_rc stop_upnp
/tmp/syslog.log:Jan 1 03:00:37 rc_service: waiting "start_firewall" via udhcpc ...
/tmp/syslog.log:Jan 1 03:00:38 rc_service: waiting "start_firewall" via udhcpc ...
/tmp/syslog.log:Jan 1 03:00:52 rc_service: udhcpc 442:notify_rc start_upnp
/tmp/syslog.log:Jan 1 03:00:52 rc_service: waiting "stop_upnp" via udhcpc ...
/tmp/syslog.log:Jan 1 03:00:53 rc_service: udhcpc 442:notify_rc start_ntpc
/tmp/syslog.log:Jan 1 03:00:53 rc_service: waiting "start_upnp" via udhcpc ...
/tmp/syslog.log:Jan 1 03:00:54 rc_service: udhcpc 442:notify_rc stop_ntpd
/tmp/syslog.log:Jan 1 03:00:54 rc_service: waiting "start_ntpc" via udhcpc ...
/tmp/syslog.log:Apr 18 04:32:13 rc_service: udhcpc 442:notify_rc start_vpnclient1
/tmp/syslog.log:Apr 18 04:32:13 dhcp_client: bound 128.70.210.185 via 128.70.208.1 during 600 seconds.
/tmp/syslog.log:Apr 18 04:32:19 openvpn[560]: [truncated] PUSH: Received control message: 'PUSH_REPLY,route 10.224.0.0 255.254.0.0,dhcp-option DNS 192.168.104.1,block-outside-dns,route-gateway 192.168.104.1,topology subnet,ping 110,ping-restart 360,route 103.246.200.0 255.255.252.0,route 109.239.140.0 255.255.255.0,route 128.199.0.0 255.255.0.0,route 149.154.160.0 255.255.240.0,route 149.154.164.0 255.255.252.0,route 149.154.168.0 255.255.252.0,route 149.154.172.0 255.255.252.0,route 159.203.0.0 255.255.0.0,route 159.
/tmp/syslog.log:Apr 18 04:32:19 openvpn[560]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
admin@RT-N66U-B068:/tmp/home/root#
I only see one occurrence of the DHCP message and that is at router boot up which is normal. That's not "constantly appearing".Here is what the router produces according to the command you submitted:
Can this be fixed?
It only appears once during a reboot (expected). But you do have a short lease of 10 minutes (600 seconds) from your ISP. Maybe it happens more frequently when it’s time to renew the lease?@dave14305
Here is what the router produces according to the command you submitted:
Can this be fixed?
Thank you in advance!
(Default Build - All supported routers)
b3044e944aa41094c2c8c80239f63f48620380d0164cf780dfcffc6b5c2e3863 RT-N16_374.43_43E6j9527.trx
54e9b96e3eb5cf9fa467d849a59209a9bbc69ec11a2e85898afc9d4a1625d392 RT-AC66U_374.43_43E6j9527.trx
caa94ce7b5be75ac05e9e5de40db58f4efc828a45aa536349df280cd23a751ad RT-N66U_374.43_43E6j9527.trx
385e5d05c110e60493ce03bf769899a6495704722d37fdfdb82df8e61fd4996b RT-AC68U_374.43_43E6j9527.trx
b00afe528c3d7bad0099486fedd370750576e7e8afdf4af76d04f5e846559d71 RT-AC56U_374.43_43E6j9527.trx
If you have an Arris modem... that exposes data on 192.168.100.1/getRouterStatus...https://github.com/jackyaz/modmonJust a reminder for everyone to look beyond the obvious...
I was having intermittent DNS failures, which I was blaming on the DNS provider unable to handle the increased traffic. When it happened again, I decided to check my modem log and low and behold it was filled with T3 and T4 timeouts and a really bad upstream power level. Turns out I had a cable splitter that had gone bad! Replaced and now the modem logs are perfectly clean and no more DNS outages.
It pays to check the hardware
And my Cisco modem has a similar feature at http://192.168.100.1/Docsis_system.aspIf you have an Arris modem... that exposes data on 192.168.100.1/getRouterStatus...https://github.com/jackyaz/modmon
If you have an Arris modem... that exposes data on 192.168.100.1/getRouterStatus...https://github.com/jackyaz/modmon
And for completeness....Netgear modemsAnd my Cisco modem has a similar feature at http://192.168.100.1/Docsis_system.asp
(Actually just http://192.168.100.1 is enough -- defaults to the above address)
It's much more fun when you can graph data though!And for completeness....Netgear modems
http://192.168.100.1/DocsisStatus.asp
http://192.168.100.1/EventLog.asp
or just navigate the menus from
http://192.168.100.1
And the cable companies are not fond of revealing those.You'll be prompted for your password for any of the above.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!