[SOLVED] D-Link DSL-224/R1 looses/restarts WAN connection and reconnects on its own

[Loldude]

Hey fellas!
I have a problem with my D-Link DSL-224/R1 router. Basically the WAN connection is lost for 5~ minutes and then goes back up.
I'm not sure what causes it, but I've snooped this from the logs, connection is down from Aug 13 16:45:47 to Aug 13 16:49:36 :

Aug 13 16:36:58 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:27:dd:c7:7c:4c:ed:**:**:**:**
Aug 13 16:40:49 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:40:49 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:40:49 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:40:50 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:40:51 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:45:47 kernel: [ptm_event_detect]: Trigger PTM Rx reset event
Aug 13 16:45:47 kernel: ptm_event_detect: rx=1, tx=0
Aug 13 16:45:47 kernel: ptm_event_process: ptm reset
Aug 13 16:45:47 kernel: ptm_SwitchPHYIfEnable: PCRP5=0x1614200f
Aug 13 16:45:47 kernel: 0xb8a85040 :  1
Aug 13 16:45:47 kernel: ptm_timer_exit
Aug 13 16:45:47 kernel: PTM: disable IP e03ef6ab
Aug 13 16:45:47 kernel: PTM: enable IP f03ef6ab
Aug 13 16:45:47 kernel: ptm_timer_exit
Aug 13 16:45:47 kernel: idx=0, 1, ptm0_1, 0, 0, bc0f9adccdab
Aug 13 16:45:47 kernel: idx=1, 0, , 0, 0, 000000000000
Aug 13 16:45:48 kernel: ptm_timer_exit
Aug 13 16:45:48 kernel: Disable_SAR
Aug 13 16:45:48 pppd[1561]: Terminating on signal 15
Aug 13 16:45:48 pppd[1561]: lcp_close: unit:0, reason: "User request" (status: 5, state: 9, was_ip_down: 0)
Aug 13 16:45:48 pppd[1561]: Connect time 98.4 minutes.
Aug 13 16:45:48 pppd[1561]: Sent 2375290 bytes, received 499452356 bytes.
Aug 13 16:45:48 pppd[1561]: Down ppp with status (5)5
Aug 13 16:45:49 kernel: ==> peerDetectorStop .. (7 17)
Aug 13 16:45:55 pppd[1561]: Connection terminated.
Aug 13 16:45:55 pppd[1561]: Sent PADT
Aug 13 16:45:55 pppd[1561]: Modem hangup
Aug 13 16:45:55 pppd[1561]: lcp_close: unit:0, reason: "" (status: 5, state: 0, was_ip_down: 1)
Aug 13 16:45:55 pppd[1561]: Exit.(5)
Aug 13 16:45:55 kernel: _rtl865x_detachMasterNetif 429 ppp0
Aug 13 16:45:55 kernel: detach ppp0 success.
Aug 13 16:45:55 kernel: _rtl865x_eventHandle_delL2Fdb(283)
Aug 13 16:45:55 kernel: _rtl865x_detachMasterNetif 429 ppp0
Aug 13 16:45:55 stop_process_t[3299]: not found pid process 'igmpx'
Aug 13 16:45:56 kernel: ==> peerDetectorStop .. (9 61)
Aug 13 16:45:56 stop_process_t[3306]: not found pid process 'igmpx'
Aug 13 16:45:57 dms_reset_uptime[3306]: enter key ptm0_1
Aug 13 16:46:01 kernel: Start Phase 0: Vectored VDSL2 17A Discovery Phase...
Aug 13 16:46:20 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:46:20 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:46:21 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:46:23 kernel: Start Phase 1: VDSL2 Training Phase...
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:46:43 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:46:47 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:46:47 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:46:58 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:27:dd:c7:7c:4c:ed:**:**:**:**
Aug 13 16:47:15 conf_wan[3674]: CONFIG_ACTION_EDIT - start
Aug 13 16:47:15 conf_wan[3674]: key_l2_incoming = ptm0
Aug 13 16:47:15 conf_wan[3674]: test
Aug 13 16:47:15 conf_wan[3674]: max_count = 3
Aug 13 16:47:15 conf_wan[3674]: key_l3_incoming = ptm0_1
Aug 13 16:47:15 conf_wan[3674]: Get incoming L2 ptm0 from config
Aug 13 16:47:15 conf_wan[3674]:  ololo
Aug 13 16:47:15 conf_wan[3674]:  line 739
Aug 13 16:47:15 conf_wan[3674]:  line 771
Aug 13 16:47:15 conf_wan[3674]: Is it lan?
Aug 13 16:47:15 conf_wan[3674]: It's wan iface
Aug 13 16:47:15 conf_wan[3674]: Make edit old
Aug 13 16:47:15 conf_wan[3674]:  line 1088
Aug 13 16:47:15 conf_wan[3674]: 1096: l2_key=ptm0, l3_key=ptm0_1
Aug 13 16:47:15 conf_wan[3674]: 1099: stop old l3 with tunnels
Aug 13 16:47:15 conf_wan[3674]: 1103: L3 or Tunnel with gwif=true deleting detected
Aug 13 16:47:15 stop_process_t[3674]: not found pid process 'igmpx'
Aug 13 16:47:15 conf_wan[3674]: 1110
Aug 13 16:47:15 conf_wan[3674]: Renew search L3 ptm0_1
Aug 13 16:47:15 conf_wan[3674]: Delete link ptm0_1
Aug 13 16:47:15 conf_wan[3674]: Set link name ptm0_1
Aug 13 16:47:15 conf_wan[3674]: lets create ethernet
Aug 13 16:47:15 conf_wan[3674]: l2=ptm0 l3=ptm0_1
Aug 13 16:47:15 conf_wan[3674]: contype = ppp
Aug 13 16:47:15 conf_wan[3674]: old connection ptm0 - ptm0_1
Aug 13 16:47:15 kernel: smux_unregister_device remove smux dev ptm0_1
Aug 13 16:47:15 kernel: idx=0, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=1, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=2, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=3, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=4, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=5, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=6, 0, , 0, 0, 000000000000
Aug 13 16:47:15 kernel: idx=7, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: ptm0_1 (): not using net_device_ops yet
Aug 13 16:47:16 kernel: idx=0, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=1, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=2, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=3, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=4, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=5, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=6, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=7, 0, , 0, 0, 000000000000
Aug 13 16:47:16 kernel: idx=0, 1, ptm0_1, 0, 0, bc0f9adccdab
Aug 13 16:47:16 kernel: idx=0, 1, ptm0_1, 0, 0, bc0f9adccdab
Aug 13 16:47:16 conf_wan[3674]: ethernet created
Aug 13 16:47:16 kernel: ADDRCONF(NETDEV_UP): ptm0_1: link is not ready
Aug 13 16:47:17 conf_wan[3674]: L3 ethernet
Aug 13 16:47:17 conf_wan[3674]: Change mac or mtu on L2 iface ptm0 !!!
Aug 13 16:47:17 stop_process_t[3674]: not found pid process 'igmpx'
Aug 13 16:47:17 conf_wan[3674]: Change mac = or mtu=1500 !!!
Aug 13 16:47:17 conf_wan[3674]: CONFIG_ACTION_EDIT - exit
Aug 13 16:47:41 kernel: TIME_OUT (12 236) (16 17 0)
Aug 13 16:47:42 kernel: ==> peerDetectorStop .. (7 16)
Aug 13 16:47:49 kernel: ==> peerDetectorStop .. (9 62)
Aug 13 16:47:54 kernel: Start Phase 0: Vectored VDSL2 17A Discovery Phase...
Aug 13 16:48:19 kernel: Start Phase 1: VDSL2 Training Phase...
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPSOLICIT(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:48:47 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:22:8f:85:9b:b8:81:**:**:**:**
Aug 13 16:48:49 dnsmasq-dhcp[3380]: DHCPREQUEST(br0) 192.***.***.*** b8:81:**:**:**:**
Aug 13 16:48:49 dnsmasq-dhcp[3380]: DHCPACK(br0) 192.***.***.*** b8:81:**:**:**:** ******
Aug 13 16:49:10 kernel: Start Phase 2: VDSL2 Exchange Phase...
Aug 13 16:49:18 kernel: Enter Showtime: TX 0,5759 / RX 0,65617 (kbps)
Aug 13 16:49:18 kernel: LoopLength(m)=400
Aug 13 16:49:24 kernel: ptm_timer_add
Aug 13 16:49:24 kernel: ADDRCONF(NETDEV_CHANGE): ptm0_1: link becomes ready
Aug 13 16:49:27 kernel: device ptm0_1 already exist.
Aug 13 16:49:27 stop_process_t[637]: not found pid process 'igmpx'
Aug 13 16:49:29 pppd[674]: Plugin /usr/lib/pppd/rp-pppoe.so loaded.
Aug 13 16:49:29 pppd[675]: pppd 2.4.4 started by admin, uid 0
Aug 13 16:49:36 pppd[675]: PPP session is 7809
Aug 13 16:49:36 pppd[675]: Used ACName = "43" in ppp(0)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:215
Aug 13 16:49:36 kernel: ,fid(0),mac(8c:90:d3:42:c5:48)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:218
Aug 13 16:49:36 kernel: _rtl865x_addPpp:215
Aug 13 16:49:36 kernel: ,fid(0),mac(8c:90:d3:42:c5:48)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:218
Aug 13 16:49:36 kernel: _rtl865x_addPpp:233
Aug 13 16:49:36 kernel: ,fid(0),mac(8c:90:d3:42:c5:48)
Aug 13 16:49:36 kernel: _rtl865x_addPpp:236
Aug 13 16:49:36 pppd[675]: Using interface ppp0
Aug 13 16:49:36 pppd[675]: Connect: ppp0 <--> ptm0_1
Aug 13 16:49:37 pppd[675]: PAP authentication succeeded
Aug 13 16:49:37 pppd[675]: peer from calling number 8C:90:D3:42:C5:48 authorized
Aug 13 16:49:37 pppd[675]: local  IP address ***.***.***.***
Aug 13 16:49:37 pppd[675]: remote IP address ***.***.***.***
Aug 13 16:49:37 pppd[675]: primary   DNS address ***.***.***.***
Aug 13 16:49:37 pppd[675]: secondary DNS address ***.***.***.***
Aug 13 16:49:37 stop_process_t[756]: not found pid process 'igmpx'
Aug 13 16:56:58 dnsmasq-dhcp[3380]: DHCPINFORMATION-REQUEST(br0) 00:01:00:01:27:dd:c7:7c:4c:ed:**:**:**:**

Note: not sure if MAC addresses are sensitive, so I changed them with asterisks (please notify me if I have exposed any sensitive information here, as I am quite new to administrating the router).

Does anyone know what exactly is "PTM Rx reset event" or what caused it? The connection is PPPoE based, PTM interface, using authorization, ADSL2+ enabled.
My router is connected properly, cables weren't tampered with (the WAN exit goes to a microfilter that connects to a phone line exit on my wall - ADSL).
During the disconnect, I still had access to my router - suggesting LAN worked properly, and the status on the WAN port showed "cable disconnect" (or just disconnected).

Also, only 1 Ethernet and 2 Wifi devices are connected to the router. Does anyone knows how to solve this?

 

[bill001g]

The mac address don't matter because even though people think they are unique they really are not. The manufactures have large pools but if they had to be unique eventually we could not have any new computers. Duplicates are actually fairly common which most large companies that buy thousands of laptops at a time find out.
The one thing that is slightly sensitive is the local IP address that you did not block out. This likely changes sometimes when the DSL is reset. All a hacker could do is try to run denile of service attacks which does not get him any money so his time is better spent elsewhere.

This looks like the DSL is just going down. It is likely some issue with the ISP but you should check all your in house wiring to be sure nothing looks damaged.

 

[Loldude]

Thanks for the reply! I masked the IP addresses, too, just in case. So this is ISP related problem? not router or router configuration? We can rule out wiring, the router sits right in front of me, as well as the microfilter and the phone line exit on the wall.

 

[bill001g]

There is nothing you can really set in DSL part of the router. Anything you can actually change would make it not work at all or do nothing. The router will negotiate with the ISP equipment for the best connection speed possible. The ISP has some settings but it is on their end.

The router could be defective but you would have to blindly replace that. Your best bet is to call the ISP and they can run a test from their office. If they go everything is fine. Then maybe you blindly replace the router and when that doesn't work you have them come out and actually test the line at your house.

 

[Loldude]

I see. I've talked to my ISP, they say they cannot really check the drop they detected since it will cause other clients to disconnect as well. They said it is an infrastructure problem, I have to contact a different company to check that instead.

 

[Loldude]

By the way, could it be because of IPv6 being enabled in the router? Or does it makes sense I have high ping (1200 - 600ms) after the DSL connection goes down?

 

[bill001g]

IPV6 can cause a different issue. Mostly you get strange errors with some but not all web sites. It does not cause the dsl to drop.

Just turn off the ipv6 support in your pc nic settings, it likely will not fix the problem but there is still almost nothing that requires IPv6 to function.

Most dsl connection fail becuase of errors on the connection. You will at times get longer pings as the router is trying to restablish the connection and is holding data in a buffer. What is sounds like is your ISP leases the phone lines from another isp,like the local phone company that actually owns the copper lines. This tends to be why even if it is slightly more expensive you buy your service directly from the company that owns the wires so they can't play these silly games.

Can you actually call the other company yourself. Very technically you are not their customer your ISP is their customer. You do not pay them money directly.

 

[Loldude]

IPV6 can cause a different issue. Mostly you get strange errors with some but not all web sites. It does not cause the dsl to drop.

Just turn off the ipv6 support in your pc nic settings, it likely will not fix the problem but there is still almost nothing that requires IPv6 to function.

Most dsl connection fail becuase of errors on the connection. You will at times get longer pings as the router is trying to restablish the connection and is holding data in a buffer. What is sounds like is your ISP leases the phone lines from another isp,like the local phone company that actually owns the copper lines. This tends to be why even if it is slightly more expensive you buy your service directly from the company that owns the wires so they can't play these silly games.

Can you actually call the other company yourself. Very technically you are not their customer your ISP is their customer. You do not pay them money directly.

Hi, thanks for answering!

Here, in my country, you have 2 separate company types or fields for network communications. One is your ISP, the other is referred to "infrastructure". My ISP just like most ISP's gives me access to the internet, depending I have working infrastructure or (copper wires, phone exit and all of that). I pay them directly for 70-100 mbps connection.

The other company "infrastructure" actually owns the copper wires and down the path the fiber optics cables. I also pay them directly. They are in charge of the Telephone Switchboard which aggregates the copper wires from a building block down the road and then into the backbone - again this time with fiber optics cables for the backbone.

This is problematic since a customer like myself will often be playing Ping-Pong or table tennis, only this time as the ball, jumping between the two companies to try and get help resolving the issue. From what it seems, in a matter of a few years this will stop and every ISP in my country will merge with an infrastructure company. Right now, that's not the case.

I've talked to the ISP, mainly, they just need to send me my PPPoE authentication details (which they did) and make sure to allocate to me our agreed upon speeds (70-100mbps down,
5-6mbps up). If I had an issue with them, I would assume it would be capped speeds (say 40mbps instead of 100) or maybe no connection at all (wrong details/ account status is inactive).

So they obviously referred me to the infrastructure company. Note, I have a deal with the ISP that covers them and the infrastructure company under the same bill. It's a deal package, but it doesn't help them communicate better with each other when issues like mine arise.

The infrastructure company sent a technician that didn't do much, he connected to the Telephone Switchboard via his smartphone to monitor our line and I logged onto my router and we saw the line statistics matched, the router and the switchboard both had almost the same values for my internet down and up speeds. He said if they had a problem the whole block would have increased number of disconnects and they would issue a checkup on the switchboard themselves (which is not the case, apparently only my line drops daily).

The technician did replace a microfilter adapter to a normal phone line to ethernet cable, but after he left I had another disconnect or even two, later in the same evening.
His suggestion is that I rent a router from the infrastructure company. Even if the disconnects will occur, they will have much more information about the cause of the problem rather than only knowing there's a problem which is the case with my personally owned router.

I'd suspect either company to deliberately disconnect me just to get me rent a router, but then what happens if I rent the router from the other company, which is not responsible for this allegation instead?
So I'm not sure. Currently my best options are:

• Contacting D-Link technical support for my country (my router has active warranty).
• Switching a router to infrastructure's one, and if that don't work then to ISP's one.
• Switching infrastructure company or ISP company.

These are sadly by far the least convenient solutions, but even if 1 of them will resolve this issue, I will be a happy man, surfing the web without interrupts.

 

[dordor]

I have the exact same problem. Same router, same log, and same country I presume by your description.
However, the fact that this is the same router might be unrelated, because I got here by searching the exact log message "Trigger PTM Rx reset event".
Did you get it solved?