Skip to main content

Hi! I got connected via DSL about a week ago and ever since the conection has been unstable. Sometimes it works for hours without interruption, and sometimes disconnects every 15 minutes. I suspect it is worse during peak hours.

In the logs every incident starts with xDSL: XTM link down followed by xDSL: link up, Connection Type: PTM, Speed: RX:111214 / TX:30542 (Kbps) two minutes later (+-10 seconds). Please see a full excerpt of one incident below.

I tried several DSL cables and resetting the modem to factory settings, but it didn't help.

Mar 23 21:40:03 daemon.debug udhcpc: Sending discover...
Mar 23 21:40:05 daemon.debug udhcpc: Sending discover...
Mar 23 21:40:06 daemon.debug udhcpc: Sending discover...
Mar 23 21:40:10 user.info esmd: xDSL: XTM link down.
Mar 23 21:40:10 daemon.info udhcpc: Received SIGTERM
Mar 23 21:40:10 daemon.info udhcpc: Unicasting a release of 10.152.183.102 to 10.152.0.3
Mar 23 21:40:10 daemon.debug udhcpc: Sending release...
Mar 23 21:40:10 daemon.info udhcpc: Entering released state
Mar 23 21:40:12 user.notice zcmdModuleCfg: System: Wan interface VD_MGNT connection lost
Mar 23 21:40:12 daemon.info udhcpc: Received SIGTERM
Mar 23 21:40:12 daemon.info udhcpc: Unicasting a release of 82.172.121.138 to 81.59.0.1
Mar 23 21:40:13 daemon.debug udhcpc: Sending release...
Mar 23 21:40:13 daemon.info udhcpc: Entering released state
Mar 23 21:40:14 user.notice zcmdModuleCfg: System: Wan interface VD_Internet connection lost
Mar 23 21:40:15 daemon.debug udhcpc: Sending discover...
Mar 23 21:40:15 daemon.info udhcpc: Received SIGTERM
Mar 23 21:40:15 daemon.info udhcpc: Entering released state
Mar 23 21:42:08 user.info esmd: xDSL: link up, Connection Type: PTM, Speed: RX:111214 / TX:30542 (Kbps)
Mar 23 21:42:09 daemon.info udhcpc: udhcp client (v0.9.8) started
Mar 23 21:42:09 daemon.notice udhcpc: Attached to schema shared memory
Mar 23 21:42:09 daemon.notice udhcpc: Attached to object name shared memory
Mar 23 21:42:09 daemon.notice udhcpc: Attached to parameter name shared memory
Mar 23 21:42:09 daemon.notice udhcpc:
Mar 23 21:42:10 daemon.info udhcpc: udhcp client (v0.9.8) started
Mar 23 21:42:10 daemon.notice udhcpc: Attached to schema shared memory
Mar 23 21:42:10 daemon.notice udhcpc: Attached to object name shared memory
Mar 23 21:42:10 daemon.notice udhcpc: Attached to parameter name shared memory
Mar 23 21:42:10 daemon.notice udhcpc:
Mar 23 21:42:11 daemon.info udhcpc: udhcp client (v0.9.8) started
Mar 23 21:42:11 daemon.notice udhcpc: Attached to schema shared memory
Mar 23 21:42:11 daemon.notice udhcpc: Attached to object name shared memory
Mar 23 21:42:11 daemon.notice udhcpc: Attached to parameter name shared memory
Mar 23 21:42:11 daemon.notice udhcpc:
Mar 23 21:42:11 daemon.warning udhcpc: 2024-03-23 21:42:11 udhcpc<14721>, zcfg_msg.c:244, _msg_recv(), WARNING: EID = 10, select() wait forever, EID = 1, type = 1 with reply, oid = 71184
Mar 23 21:42:11 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:11 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:11 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:13 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:13 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:13 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:13 daemon.debug udhcpc: Sending select for 10.152.183.102...
Mar 23 21:42:13 daemon.debug udhcpc: Sending select for 82.172.121.138...
Mar 23 21:42:13 daemon.info udhcpc: Lease of 10.152.183.102 obtained, lease time 3600
Mar 23 21:42:13 daemon.info udhcpc: dhcpMsgSend: msgTypeT-2147483432]
Mar 23 21:42:14 daemon.info udhcpc: Lease of 82.172.121.138 obtained, lease time 1800
Mar 23 21:42:14 daemon.info udhcpc: dhcpMsgSend: msgTypeT-2147483432]
Mar 23 21:42:15 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:17 user.notice zcmdModuleCfg: System: Wan interface VD_MGNT connection ready
Mar 23 21:42:19 daemon.info udhcpc: No lease, forking to background.
Mar 23 21:42:20 user.notice zcmdModuleCfg: System: Wan interface VD_Internet connection ready
Mar 23 21:42:24 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:26 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:28 daemon.debug udhcpc: Sending discover...
Mar 23 21:42:37 daemon.debug udhcpc: Sending discover...

 

 

Hello @NeKpoT 

Is the modem directly connected to the main KPN ISRA where the KPN cable is also connected or is it connected to another connection point in your house? 


Hi @Waqqas,

I coudn’t find the ISRA, so it’s connected to an outlet in the living room. There are TV and radio connections right next to it though, so maybe it’s not just any connection point.


@NeKpoT 

Can you share pictures of the wall outlet and your fusebox? Maybe there's an ISRA in your fusebox?


@Waqqas 

I don’t see any phone connections in the fusebox. Here are the photos 

 

 

 

 


@NeKpoT 

I cannot see an ISRA but the outlet on the last photo is not the original ISRA. It's any of these :

Do you have a crawling area? Maybe you'll see the blue KPN cable there.


@Waqqas 

Unscrewing the outlet reveals 2 blue cables going somewhere into the wall. If there is a crawl space, I don't have an easy way to access it. I’m trying to get an answer from my landlord, but they aren't helpful so far. Can we try some other approaches in the meantime?

Disconnect frequency changes through the day, peaking in the evening and dropping to almost none at night. This suggests it depends on network load, not just some wires loosing contact.

Also, I'm surprised that every time the connection comes back almost exactly 2 minutes later, both when the internet goes down and when I unplug it myself. It seems artifitial, maybe you know a modem setting that controls it (I have Zyxel T-54)? Would be much more bearable if it were shorter.


@NeKpoT

Because you have 2 cables behind the outlet there is a bridge tap in your network. You are supposed to only have the incoming KPN cable connected.

I think it is better that a moderator can send a technician to locate the original KPN cable, connect the modem there and remove the other cable.


Reageer