New IP address allocation causing connection to drop out frequently

[moose56]

Hi,

This problem started last week. After having a very stable Infinity connection we now get a drop in the connection about every 40 minutes that lasts for about 3 minutes.

It was happening last week and I managed to identify that it was beeing caused by our IP address being changed that frequently. It then stopped and the IP address went back to being changes about once a day, ususally at night.

Since yesterday the issues has started again. since 6am today we have had 14 different IP addresses. The fact this happens at least once an hour makes streaming a film frustrating as the connection drops out totally whilie it is happening.

Has anyone else had this problem? I don't think it is happening at my end.

(Disclaimer, I am useing a Vigor 130 not a HomeHub, although I don't think that is causing the problem...)

David.

[Keith_Beddoe]

Its the other way around, its the drop in connection which caused the IP address to change.

Is there any noise on your phone calls? Dial 17070 and select option 2, there should be no noise between the announcements.

Sound like a thermostat on a heating system causing interference and dropping your connection.

Something that starts operating at 6AM.

[moose56]

Thanks, I will try the number when I get home.

It is actually happening around the clock. I just used 6am as a start point to illustrait the frequency of the issue for today.

[Keith_Beddoe]

Then it could be a noisy line, or a high resistance connection somewhere.

Look at the connection error stats on the router and see if there is a high error count.

[moose56]

So I have tried the line and there is no noise. I have called it a number of times and all fine.

Looking at the logs for my router there is a repeating pattern when the new IP address is assigned and I was looking at them when the issue happened again just now, here is an example of what is being logged when the problem occurs until the connection comes back:

Jan 11 20:28:32 USG zebra[696]: interface eth0 index 2 changed <UP,BROADCAST,PROMISC,MULTICAST>.
Jan 11 20:28:32 USG kernel: eth0: Link down
Jan 11 20:28:33 USG zebra[696]: interface eth0 index 2 changed <UP,BROADCAST,RUNNING,PROMISC,MULTICAST>.
Jan 11 20:28:33 USG kernel: eth0: 1000 Mbps Full duplex, port 0
Jan 11 20:29:05 USG pppd[3394]: Serial link appears to be disconnected.
Jan 11 20:29:05 USG zebra[696]: interface pppoe0 index 59 changed <POINTOPOINT,NOARP,MULTICAST>.
Jan 11 20:29:05 USG zebra[696]: interface pppoe0 mtu changed from 1492 to 1500
Jan 11 20:29:09 USG ntpd[30618]: ntpd exiting on signal 15
Jan 11 20:29:11 USG pppd[3394]: Connection terminated: no multilink.
Jan 11 20:29:11 USG zebra[696]: interface pppoe0 index 59 deleted.
Jan 11 20:29:11 USG pppd[3394]: Modem hangup
Jan 11 20:29:11 USG ntpd[18308]: ntpd 4.2.6p2@1.2194-o Wed Sep 27 04:27:31 UTC 2017 (1)
Jan 11 20:29:11 USG ntpd[18309]: proto: precision = 53.443 usec
Jan 11 20:29:13 USG ntpd_intres[18314]: host name not found: 0.ubnt.pool.ntp.org
Jan 11 20:29:17 USG zebra[696]: interface eth0 index 2 changed <UP,BROADCAST,PROMISC,MULTICAST>.
Jan 11 20:29:17 USG kernel: eth0: Link down
Jan 11 20:29:19 USG zebra[696]: interface eth0 index 2 changed <UP,BROADCAST,RUNNING,PROMISC,MULTICAST>.
Jan 11 20:29:19 USG kernel: eth0: 1000 Mbps Full duplex, port 0
Jan 11 20:30:15 USG ntpd_intres[18314]: host name not found: 0.ubnt.pool.ntp.org
Jan 11 20:30:16 USG pppd[3394]: Timeout waiting for PADO packets
Jan 11 20:31:31 USG pppd[3394]: Timeout waiting for PADO packets
Jan 11 20:31:46 USG pppd[3394]: Connected to a0:f3:e4:34:d6:4a via interface eth0
Jan 11 20:31:46 USG zebra[696]: interface ppp0 index 60 <POINTOPOINT,NOARP,MULTICAST> added.
Jan 11 20:31:46 USG pppd[3394]: Connect: ppp0 <--> eth0
Jan 11 20:31:46 USG zebra[696]: interface ppp0 mtu changed from 1500 to 1492
Jan 11 20:31:46 USG pppd[3394]: CHAP authentication succeeded
Jan 11 20:31:46 USG pppd[3394]: peer from calling number A0:F3:E4:34:D6:4A authorized
Jan 11 20:31:46 USG pppd[3394]: Unsupported protocol 'IPv6 Control Protovol' (0x8057) received
Jan 11 20:31:46 USG pppd[3394]: Unsupported protocol 'IPv6 Control Protovol' (0x8057) received
Jan 11 20:31:46 USG zebra[696]: warning: PtP interface ppp0 with addr 86.176.243.69/32 needs a peer address
Jan 11 20:31:46 USG zebra[696]: interface index 60 was renamed from ppp0 to pppoe0
Jan 11 20:31:46 USG pppd[3394]: local  IP address 86.176.243.69
Jan 11 20:31:46 USG pppd[3394]: remote IP address 172.16.12.132
Jan 11 20:31:46 USG zebra[696]: interface pppoe0 index 60 changed <UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>.
Jan 11 20:31:49 USG pppd[3394]: Unsupported protocol 'IPv6 Control Protovol' (0x8057) received

This is basically the same messages that are logged every time the issues happens.

Any ideas?

[imjolly]

Have you tried connecting the hub to see if you get a stable internet connection to rule out a problem with vigor modem

[moose56]

No. will dig it out and give it a try.

[Keith_Beddoe]

---

@imjolly wrote:

Have you tried connecting the hub to see if you get a stable internet connection to rule out a problem with vigor modem

---

I agree that looks like a router issue.

[Liam_]

Out of curiosity what router are you using with the DrayTek?

Are you running on the latest firmware which is Vigor 130 3.8.1.2?

[moose56]

So I have never used the homehub here since we moved in last November although I had been using it in our last house and it had worked fine.

I have connected it just now and it can not connect to the internet. restarted it a couple of times and even did a reset and no luck. Will have to have another look at it over the weekend.

The Vigor is on the latest firmware and up until the week before last had been working fine. 

The router is a Ubiquiti UniFi Security Gateway. That is what the USG stands for in the logs above.