[DLS-AC68U] How to change forced disconnection schedule? busted Hardware?

[nakany]

Hello


I called my ISP and they told me they have nothing to do with IP reassignment schedules ( i have a dynamic IP and its changes every 24h).
Every day at ~15:46 I get a forced disconnection. How do I change it? They told me its a router setting. Where can I add the time for a forced disconnect? they also told me I can just unplug the power source and re-plug it after a few minutes at my preferable time. I did but nothing changed I also tried to enable Reboot Scheduler and still no luck.

Forced Disconnection Log

Oct 19 15:46:11 DSL: Link up -> down
Oct 19 15:46:15 WAN Connection: Fail to connect with some issues.
Oct 19 15:46:16 nat: apply redirect rules
Oct 19 15:46:20 WAN Connection: Ethernet link down.
Oct 19 15:46:40 pppd[478]: Serial link appears to be disconnected.
Oct 19 15:46:46 pppd[478]: Connection terminated.
Oct 19 15:46:46 pppd[478]: Modem hangup
Oct 19 15:47:21 DSL: Link down -> up
Oct 19 15:47:25 WAN Connection: Ethernet link up.
Oct 19 15:47:25 rc_service: wanduck 227:notify_rc restart_wan_if 0
Oct 19 15:47:26 pppd[478]: Unable to complete PPPoE Discovery
Oct 19 15:47:28 pppd[10890]: pppd 2.4.7 started by admin, uid 0
Oct 19 15:47:28 pppd[10890]: Connected to dc:xxx:xxx:xxx:xxx:xxx via interface vlan3880
Oct 19 15:47:28 pppd[10890]: Connect: ppp0 <--> vlan3880
Oct 19 15:47:29 pppd[10890]: PAP authentication succeeded
Oct 19 15:47:29 pppd[10890]: peer from calling number xxx:xxx:xxx:xxx:xxx:xxx authorized
Oct 19 15:47:29 pppd[10890]: local  IP address xxx.xxx.xxx.xxx
Oct 19 15:47:29 pppd[10890]: remote IP address xxx.xxx.xxx.xxx
Oct 19 15:47:29 pppd[10890]: primary   DNS address xxx.xxx.xxx.xxx
Oct 19 15:47:29 pppd[10890]: secondary DNS address xxx.xxx.xxx.xxx
Oct 19 15:47:30 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
Oct 19 15:47:30 WAN Connection: Fail to connect with some issues.
Oct 19 15:47:30 nat: apply redirect rules
Oct 19 15:47:31 wan: finish adding multi routes
Oct 19 15:47:31 miniupnpd[762]: shutting down MiniUPnPd
Oct 19 15:47:31 miniupnpd[10946]: version 1.9 started
Oct 19 15:47:31 miniupnpd[10946]: HTTP listening on port 37080
Oct 19 15:47:31 miniupnpd[10946]: Listening for NAT-PMP/PCP traffic on port 5351
Oct 19 15:47:35 WAN Connection: WAN was restored.
Oct 19 15:47:36 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
Oct 19 15:47:38 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
Oct 19 15:47:39 zcip client: configured xxx.xxx.xxx.xxx

Just right now while typing my post I realised something odd. the date in my logs makes no sense.

Oct3? May 5? My System Time, Time Zone and daylight.. etc. is set probably. I don't get it. Is my Hardware busted?

Log dates from Oct 16 to Oct 19 15:48:08
Oct 3 22:45:13
Oct 17 16:25:32
Oct 18 05:23:36
Oct 18 23:00:05
Oct 19 03:05:27
Oct 19 05:00:22
May 5 07:05:02
May 5 07:05:41
Oct 19 05:03:07
Oct 19 15:48:08
End

Note
- Full Past 3 Days Log is attached
- ###### are syslog: wlceventd_proc_event)

This is a nightmare I can't endure. This stupid DSL-AC68U always pisses me off here and there its popping up some random pathetic issues, I own this since release. Big mistake.

 

[RMerlin]

PPPoE sessions should not drop the connection unless something actually broke the connection. This could indicate you are having line stability issues, especially if the time is randomly changing every time.

 

[nakany]

I do not understand this behaviour. Why does System Time changes to Nov 01.

Oct 31 19:02:30 miniupnpd[2001]: shutting down MiniUPnPd
Oct 31 19:02:31 miniupnpd[7973]: version 1.9 started
Oct 31 19:02:31 miniupnpd[7973]: HTTP listening on port 33396
Oct 31 19:02:31 miniupnpd[7973]: Listening for NAT-PMP/PCP traffic on port 5351
Oct 31 19:02:31 WAN Connection: WAN was restored.
Oct 31 19:02:30 miniupnpd[2001]: shutting down MiniUPnPd
Oct 31 19:02:31 miniupnpd[7973]: version 1.9 started
Oct 31 19:02:31 miniupnpd[7973]: HTTP listening on port 33396
Oct 31 19:02:31 miniupnpd[7973]: Listening for NAT-PMP/PCP traffic on port 5351
Oct 31 19:02:31 WAN Connection: WAN was restored.
Nov  1 03:51:17 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6994)]retrieve firmware information
Nov  1 03:51:17 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7011)]no need to upgrade firmware
Nov  1 03:51:47 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6994)]retrieve firmware information
Nov  1 03:51:47 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7011)]no need to upgrade firmware
Nov  1 12:46:57 syslog: wlceventd_proc_event(534): eth1: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0)

View attachment 27333

 

[nakany]

It happened again. It seems there is a huge problem with system time that forces to change daily ip resets randomly. I will try gnutons merlin cfw and if it's happen again I will dispose my hardware and buy new hardware from other brands.

Nov 2 19:05:11 pppd[1942]: Connection terminated.
Nov 2 19:05:11 pppd[1942]: Modem hangup
Nov 2 19:05:21 pppd[1942]: Connected to xx:xx:xx:xx:xx:xx via interface vlanxxxx
Nov 2 19:05:21 pppd[1942]: Connect: ppp0 <--> vlan3880
Nov 2 19:05:22 pppd[1942]: PAP authentication succeeded
Nov 2 19:05:22 pppd[1942]: peer from calling number xx:xx:xx:xx:xx:xx authorized
Nov 2 19:05:22 pppd[1942]: local IP address xx.xx.xx.xx
Nov 2 19:05:22 pppd[1942]: remote IP address xx.xx.xx.xx
Nov 2 19:05:22 pppd[1942]: primary DNS address xx.xx.xx.xx
Nov 2 19:05:22 pppd[1942]: secondary DNS address xx.xx.xxxx
Nov 2 19:05:22 nat: apply nat rules (/tmp/nat_rules_ppp0_vlanxxxx)
Nov 2 19:05:23 wan: finish adding multi routes
Nov 2 19:05:23 miniupnpd[13714]: shutting down MiniUPnPd
Nov 2 19:05:23 miniupnpd[19422]: version 1.9 started
Nov 2 19:05:24 miniupnpd[19422]: HTTP listening on port 43406
Nov 2 19:05:24 miniupnpd[19422]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 2 19:05:26 WAN Connection: WAN was restored.

 

[ColinTaylor]

I do not understand this behaviour. Why d System Time not to change to Nov 01.

Why would it change to Nov 1, the link went down on Oct 31.

It happened again. It seems there is a huge problem with system time that forces to change daily ip resets randomly.

This is either an issue with your line stability or (more likely) your ISP resetting the connection.

 

[nakany]

bad typo

DLS-AC68U uses May 5 if it can't reach ntp server.

​

DSL Uptime	3 days 5 hour(s) 1 minute(s) 16 seconds

​

Uptime	13 days 19 hour(s) 22 minute(s) 17 seconds

3 Days ago I replugged the cable after ~30 minutes. My daily reset changed from

Oct 19 15:46:11 (my main issue)

to

Oct 29 04:51:31 (on purpose)

It worked fine but somehow it messed up and changed the reset to

Oct 30 18:59:58

That Nov ignore it it was my fault, I was just too tired I thought it was a non ntp preconfiged problem.

My ISP blames me and they said there are no connection issues its my modem-router. I believe because the dst change the router got messed up on its own. Time Zone, DST Start - End, are probably adjusted. There are some System Time issues i keep encountering and I don't know how to solve it.

Screw this I'm gonna buy new hardware. Its way too tiresome the frustration I have to deal with too keep my dsl-ac68u is absolutely not worth it.

 

[blockhead]

Heyoh

I have a VDSL contract and my ISP does an auto-disconnect every 24h.

- Unfortunately DSL-AC68U don't offer an option to pick a time (WAN Options)

- "Enable Reboot Scheduler" doesn't work either, I have a no clue why. Maybe the DSL cable needs to be stay unplugged a little longer?

- Shutting it completely to pick a reset time works for me only for one or three days after that, for whatever reason it does a random re connection. For some strange reasons ASUS won't keep track of time, to do a 24h auto reset. My ISP told me they didn't changed the schedule, they are not involved.

Thanks to your mention, I found a solution and hopefully this might help you as well.

I will try gnutons merlin cfw

Scheduled-Reboot

Create new page · RMerl/asuswrt-merlin.ng Wiki

Third party firmware for Asus routers (newer codebase) - Create new page · RMerl/asuswrt-merlin.ng Wiki

github.com

Glad someone ported asuswrt-merlin to DLS-AC68U