Forum Index | Search | Register (New User) | Login (Existing User) | Who's Online | FAQ | Main Site

Technical Discussion
>> Technical Issues

Register (or login) on our website and you will not see this ad.

Pages in this thread: 1 | 2 | 3 | 4 | >> (show all)

Standard User

deleted
(deleted) Mon 09-Jan-17 00:19:47

Print Post

Internet connection drops for 30 seconds frequently

[link to this post]

Hi guys,

New BT Infinity customer here, had it for about 2 months now. I've called up BT and asked for help, they they haven't been helpful. My last provider was fine, wasn't getting any drops.

I frequently lose connection. It's random but can happen every few minutes or I can stay connected for an hour or two. When a disconnect occurs the connection drops for maybe 20-30 seconds, which is too short for a router crash & restart (lights don't seem to flash any other colour and looks normal) but long enough for Skype or any game I'm playing to disconnect

I've brought and changed to a new ADSL filter. I changed the ethernet cables from my computer to my powerlines and hub. I was sent another BT HH6, that didnt change anything. I've called 17070 and selected option 2, there dosn't seem to be any loud noise. What other options are there?

Thanks

Administrator

MrSaffron
(staff) Mon 09-Jan-17 10:28:28

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

What does the status page of the router show?

It is not clear if this is when using wireless or an Ethernet connection? With the description of the lights sounds more like a DNS problem rather than the actual connection falling over

Andrew Ferguson, [email protected]
www.thinkbroadband.com
See if your ADSL stats are any good | UK broadband availability checker | Speed test for PC, tablets and mobiles

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.

Standard User

deleted
(deleted) Mon 09-Jan-17 11:21:22

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

What is the speed you're getting? I get 2 MBps and when I switched to Plusnet a few months ago, they decided not to enable ADSL2+ for me (since I'd never achieve these speeds), just ADSL1.
Logical enough, but I had exactly same resync issue as you're describing. Phoned them, they switched my line to 21CN and enabled ADSL2+, and the issues stopped.

Edited by deleted (Mon 09-Jan-17 11:22:00)

Register (or login) on our website and you will not see this ad.

Standard User

ukhardy07
(knowledge is power) Mon 09-Jan-17 11:48:14

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Can you pop here:

http://192.168.1.254/0000013200/gui/#/main/

Click Advanced Settings

Click Technical Log

Copy and paste the output on this page, it will help us see if your lines dropping a lot and provide us stats.

Generally speaking if the hub light is solid blue, not orange, your line has not dropped and the connection was ok, indicating wireless or the system in use may be the problem.

Standard User

deleted
(deleted) Mon 09-Jan-17 13:52:36

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: ukhardy07] [link to this post]

I'm not sure what the status page shows. But next time i disconnect I will quickly go look at it.

At the moment I have my hub connected to a powerline adapter downstairs and then a powerline adapter upstairs connected to a switch and from there it connects to 2 PCs and my PS4.

On the hub status page is says I'm getting Downstream sync speed: 55.00 Mbps and Upstream sync speed: 10.00 Mbps. speedtest.net says I'm getting: 8 ping, 38.02 download, 9.52 upload.

This is the eventlog from my connection drop just now.

13:43:53, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:45b6:36c5:3760:4138 is set active

13:43:51, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::ae22:bff:fea6:9243 is set active

13:43:51, 09 Jan.

wl1:A WiFi device <AC:22:0B:A6:92:43> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

13:43:51, 09 Jan.

wl1:A WiFi device <C0:EE:FB:50:1D:CA> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

13:43:39, 09 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

13:43:31, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:54f2:aa9:835:9f1 is set active

13:43:24, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:45b6:36c5:3760:4138 is set active

13:43:19, 09 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

13:43:19, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:bdb2:b1bf:d415:88b3 is set active

13:43:10, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:54f2:aa9:835:9f1 is set active

13:42:52, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:bdb2:b1bf:d415:88b3 is set active

13:42:46, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:45b6:36c5:3760:4138 is set active

13:42:25, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:45b6:36c5:3760:4138 is set active

13:42:23, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:45b6:36c5:3760:4138 is set inactive

13:42:23, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:1dca is set inactive

13:42:14, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:bdb2:b1bf:d415:88b3 is set active

13:41:42, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:45b6:36c5:3760:4138 is set active

13:41:42, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:bdb2:b1bf:d415:88b3 is set active

13:41:40, 09 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

13:41:31, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:1dca is set active

13:41:23, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:54f2:aa9:835:9f1 is set inactive

13:41:14, 09 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

13:41:03, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:1dca is set active

13:41:03, 09 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:bdb2:b1bf:d415:88b3 is set active

Standard User

deleted
(deleted) Mon 09-Jan-17 14:20:35

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Your problems are probably down to the powerline adapters.
Can you replace them with an ethernet cable?

Standard User

deleted
(deleted) Mon 09-Jan-17 14:54:11

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

I've never had a problem with it when I was with Virgin Media. Anyway, I've now connected an Ethernet cable directly to the hub.

Standard User

deleted
(deleted) Mon 09-Jan-17 17:11:57

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

There are indications that VDSL2 and powerline adapters can interfere with each other as they may use similar frequencies.

Standard User

deleted
(deleted) Mon 09-Jan-17 17:39:34

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

I'm still getting the same drop even connected directly to the hub. Do you think maybe the Hub BT gave me is awful?

Edited by deleted (Mon 09-Jan-17 17:40:35)

Standard User

RobertoS
(elder) Mon 09-Jan-17 18:03:51

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Are the powerline adapters still in plugged in and switched on? (Either or both is the same thing). It's a concern about them screwing up the service, not the connection of the particular computer smile

smile

.

_{^{Kindness isn't going to cure the world of all its awfulness but it's a good place to begin. Daisy Ridley.}}
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 54999/14466Kbps @ 600m. BQMs - IPv4 & IPv6

Standard User

deleted
(deleted) Mon 09-Jan-17 18:42:09

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Maybe. They usually are

Standard User

deleted
(deleted) Mon 09-Jan-17 18:52:27

Print Post

Re: Internet connection drops for 30 seconds frequently DELETED

[re: deleted] [link to this post]

Post deleted by iced_dragon

Standard User

deleted
(deleted) Mon 09-Jan-17 18:54:33

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: RobertoS] [link to this post]

I turned the powerline adapters off. I still have it connected directly to the hub. It's still dropping.

Standard User

RobertoS
(elder) Mon 09-Jan-17 19:19:21

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Ummm. Not that then frown

frown

.

Can you find and post the firmware version?

_{^{Kindness isn't going to cure the world of all its awfulness but it's a good place to begin. Daisy Ridley.}}
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 54999/14466Kbps @ 600m. BQMs - IPv4 & IPv6

Standard User

deleted
(deleted) Mon 09-Jan-17 20:55:34

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: RobertoS] [link to this post]

Firmware version: SG4B10002244
Firmware updated: 15-Dec-2016

Standard User

ian007jen
(committed) Tue 10-Jan-17 08:11:10

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

are you connecting via wireless?

Have you "split" the wifi frequencies?

Standard User

deleted
(deleted) Tue 10-Jan-17 17:01:10

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: ian007jen] [link to this post]

I have a ethernet cable connected to the hub directly from my computer.

Standard User

ukhardy07
(knowledge is power) Tue 10-Jan-17 18:53:37

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Can you pop here:

http://192.168.1.254/

Click Advanced Settings

Click Technical Log

Copy and paste the output on this page.

This will help us 100x

Also what is the hub displaying as your connection uptime?

Edited by ukhardy07 (Tue 10-Jan-17 18:55:35)

Standard User

deleted
(deleted) Thu 12-Jan-17 00:00:47

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: ukhardy07] [link to this post]

I borrowed a homehub5 to see if it was my smart hub that was acting up. Heres the log from HH5 with my recent drop. Will having a mix of CAT6 and CAT5 cables be a problem?

23:37:13, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [145.253.85.94]:4810 ppp3 NAPT)
23:37:12, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [46.33.134.66]:36679 ppp3 NAPT)
23:37:10, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [76.11.105.158]:6889 ppp3 NAPT)
23:37:10, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [201.215.55.217]:42926 ppp3 NAPT)
23:37:08, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [211.184.197.28]:40585 ppp3 NAPT)
23:37:07, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [73.76.21.32]:8999 ppp3 NAPT)
23:37:05, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [1.252.162.175]:41181 ppp3 NAPT)
23:37:05, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [73.76.21.32]:8999 ppp3 NAPT)
23:37:03, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [82.242.254.58]:30295 ppp3 NAPT)
23:37:03, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [46.129.106.37]:50321 ppp3 NAPT)
23:37:03, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [173.212.205.73]:51493 ppp3 NAPT)
23:37:02, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [84.0.185.25]:14270 ppp3 NAPT)
23:37:01, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [47.138.246.72]:26897 ppp3 NAPT)
23:37:00, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [74.65.64.89]:6889 ppp3 NAPT)
23:36:59, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [27.84.227.163]:11521 ppp3 NAPT)
23:36:59, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [81.26.169.219]:42467 ppp3 NAPT)
23:36:58, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [122.245.55.134]:6890 ppp3 NAPT)
23:36:58, 11 Jan. IN: BLOCK [12] Spoofing protection (IGMP 86.176.199.28->224.0.0.22 on ppp3)
23:36:57, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [187.101.57.14]:42459 ppp3 NAPT)
23:36:56, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [135.23.47.152]:49759 ppp3 NAPT)
23:36:55, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [84.212.92.64]:37114 ppp3 NAPT)
23:36:54, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [188.49.32.168]:20094 ppp3 NAPT)
23:36:53, 11 Jan. IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254->224.0.0.22 on ptm0.101)
23:36:53, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [126.235.4.82]:20280 ppp3 NAPT)
23:36:51, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [89.138.110.226]:1054 ppp3 NAPT)
23:36:50, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [24.36.105.32]:50321 ppp3 NAPT)
23:36:49, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [194.44.153.133]:57341 ppp3 NAPT)
23:36:48, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [213.144.12.56]:51384 ppp3 NAPT)
23:36:48, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [5.199.145.31]:6881 ppp3 NAPT)
23:36:47, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [60.68.165.28]:7862 ppp3 NAPT)
23:36:46, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [124.121.73.140]:17510 ppp3 NAPT)
23:36:46, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [179.62.77.164]:38791 ppp3 NAPT)
23:36:44, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [175.182.250.110]:6889 ppp3 NAPT)
23:36:44, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: TCP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [91.61.13.14]:52919 TIME_WAIT/CLOSED ppp3 NAPT)
23:36:44, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [119.73.104.200]:6881 ppp3 NAPT)
23:36:43, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: TCP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [91.61.13.14]:52919 CLOSED/SYN_SENT ppp3 NAPT)
23:36:43, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [61.184.86.89]:13027 ppp3 NAPT)
23:36:42, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [95.90.206.159]:5701 ppp3 NAPT)
23:36:41, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [60.241.73.3]:20860 ppp3 NAPT)
23:36:40, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [89.25.60.243]:50321 ppp3 NAPT)
23:36:38, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [60.52.23.28]:16001 ppp3 NAPT)
23:36:38, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [80.66.39.142]:6881 ppp3 NAPT)
23:36:37, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [176.104.162.178]:65363 ppp3 NAPT)
23:36:37, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [59.125.105.197]:13032 ppp3 NAPT)
23:36:36, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [74.115.5.29]:21906 ppp3 NAPT)
23:36:35, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [69.251.117.191]:37644 ppp3 NAPT)
23:36:35, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [46.44.21.124]:13480 ppp3 NAPT)
23:36:35, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [101.109.214.203]:19980 ppp3 NAPT)
23:36:33, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [222.167.114.13]:27489 ppp3 NAPT)
23:36:31, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [213.144.20.155]:26737 ppp3 NAPT)
23:36:31, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [182.52.22.27]:21475 ppp3 NAPT)
23:36:31, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [90.231.75.83]:6881 ppp3 NAPT)
23:36:31, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [36.238.89.115]:27185 ppp3 NAPT)
23:36:31, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [75.169.254.139]:55979 ppp3 NAPT)
23:36:30, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [175.141.162.46]:54025 ppp3 NAPT)
23:36:30, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [202.78.228.101]:15461 ppp3 NAPT)
23:36:29, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [1.42.242.131]:27008 ppp3 NAPT)
23:36:28, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [172.58.110.219]:63624 ppp3 NAPT)
23:36:26, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:34144 <--> [86.176.199.28]:34144 - - - [148.252.129.106]:33856 ppp3 NAPT)
23:36:26, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [210.219.180.75]:50926 ppp3 NAPT)
23:36:26, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [188.66.171.46]:41692 ppp3 NAPT)
23:36:25, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [178.201.201.57]:6889 ppp3 NAPT)
23:36:25, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [88.171.152.132]:40959 ppp3 NAPT)
23:36:25, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [183.193.169.169]:3348 ppp3 NAPT)
23:36:23, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [109.241.77.228]:12325 ppp3 NAPT)
23:36:21, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [80.7.6.142]:64488 ppp3 NAPT)
23:36:21, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [61.197.36.91]:61534 ppp3 NAPT)
23:36:19, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [176.130.216.162]:1259 ppp3 NAPT)
23:36:18, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [117.174.138.86]:37658 ppp3 NAPT)
23:36:18, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [200.8.44.195]:15594 ppp3 NAPT)
23:36:18, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [222.110.102.134]:39157 ppp3 NAPT)
23:36:18, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [133.236.16.41]:8599 ppp3 NAPT)
23:36:17, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [88.88.146.169]:16516 ppp3 NAPT)
23:36:16, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [109.201.134.108]:20010 ppp3 NAPT)
23:36:15, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [222.117.152.37]:63116 ppp3 NAPT)
23:36:15, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [37.48.119.25]:55230 ppp3 NAPT)
23:36:15, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [110.170.39.99]:49651 ppp3 NAPT)
23:36:14, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [76.109.224.110]:20152 ppp3 NAPT)
23:36:13, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [88.117.111.147]:6881 ppp3 NAPT)
23:36:12, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [88.8.130.119]:49012 ppp3 NAPT)
23:36:12, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [173.212.202.248]:51425 ppp3 NAPT)
23:36:12, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [99.226.164.71]:50321 ppp3 NAPT)
23:36:11, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [61.224.48.65]:8628 ppp3 NAPT)
23:36:10, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [81.195.10.40]:46526 ppp3 NAPT)
23:36:10, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [49.76.208.150]:33287 ppp3 NAPT)
23:36:10, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [200.161.137.181]:16062 ppp3 NAPT)
23:36:07, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [109.96.82.46]:21183 ppp3 NAPT)
23:36:06, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [61.82.30.220]:54312 ppp3 NAPT)
23:36:06, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [82.2.50.243]:24358 ppp3 NAPT)
23:36:06, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [1.229.94.220]:6881 ppp3 NAPT)
23:36:06, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [24.44.121.227]:6889 ppp3 NAPT)
23:36:05, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [104.200.153.100]:12545 ppp3 NAPT)
23:36:04, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [116.39.91.188]:6889 ppp3 NAPT)
23:36:04, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [213.144.12.56]:46635 ppp3 NAPT)
23:36:02, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [89.164.44.170]:7944 ppp3 NAPT)
23:36:02, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [46.237.204.219]:4912 ppp3 NAPT)
23:36:02, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [208.54.39.220]:20073 ppp3 NAPT)
23:36:01, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [113.174.29.40]:3800 ppp3 NAPT)
23:36:01, 11 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [118.81.124.173]:16001 ppp3 NAPT)
23:35:59, 11 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.103]:16061 <--> [86.176.199.28]:16061 - - - [213.144.12.56]:48004 ppp3 NAPT)

Standard User

deleted
(deleted) Thu 12-Jan-17 00:07:43

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

In reply to a post by iced_dragon:
I borrowed a homehub5 to see if it was my smart hub that was acting up. Heres the log from HH5 with my recent drop.

What time was the drop?

Will having a mix of CAT6 and CAT5 cables be a problem?

No

Standard User

deleted
(deleted) Fri 13-Jan-17 22:39:50

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

I dropped at 22:12 and 22:32, I feel like where is says "eth1:IGMP join received for group 226.178.217.5 on interface eth1" is when my connection is dropping.

22:11:03, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:10:49, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:10:48, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:10:36, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:10:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:10:28, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:10:25, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:10:14, 13 Jan.

ppp1:DNS name resolution failure (teredo.ipv6.microsoft.com)

22:10:11, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:10:09, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:09:58, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set inactive

22:09:51, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:09:40, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:09:35, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:09:16, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:09:12, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:09:06, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:08:58, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set inactive

22:08:58, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set inactive

22:08:42, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:08:40, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:08:37, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:08:23, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:08:14, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:08:11, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:08:10, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:08:02, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:07:59, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:07:56, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:07:44, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:07:43, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set inactive

22:07:34, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:07:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:07:27, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set inactive

22:07:22, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:07:21, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:07:11, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:07:05, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:06:57, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:06:55, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:06:52, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:06:37, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:06:35, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:06:33, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:06:27, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set inactive

22:06:24, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:06:21, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:06:18, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:06:09, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:06:08, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:06:05, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:05:58, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:05:57, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set inactive

22:05:57, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set inactive

22:05:55, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:05:49, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:05:46, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:05:44, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:05:26, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:05:25, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:05:16, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:05:16, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:05:11, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:04:53, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:04:37, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:04:35, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:04:35, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:04:33, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:04:24, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:04:20, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:04:19, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:04:13, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:04:05, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:04:01, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:03:57, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set inactive

22:03:57, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set inactive

22:03:48, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:03:46, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:03:34, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:03:19, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:03:14, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:03:11, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:03:07, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:02:51, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:02:43, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:02:42, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set inactive

22:02:41, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:02:38, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:02:30, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:02:27, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set inactive

22:02:21, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:02:20, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set active

22:02:17, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:02:12, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d563:ece8:8d5c:2173 is set inactive

22:02:12, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:8df4:245d:ae99:19f2 is set inactive

22:02:08, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:02:05, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::cd2:a5dd:f188:88f1 is set active

22:01:49, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:01:43, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:01:39, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:34:37, 13 Jan.

:HTTP UserAdmin login from 192.168.1.64 successfully

22:34:34, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:34:17, 13 Jan.

:HTTP UserBasic login from 192.168.1.64 successfully

22:34:17, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:34:09, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:33:56, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:33:55, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:33:42, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:33:29, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:33:23, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:33:19, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:33:17, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set inactive

22:33:12, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:32:54, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:32:45, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:32:36, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:32:34, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:32:32, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set inactive

22:32:17, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:32:16, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:1dca is set inactive

22:32:13, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:32:08, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:32:01, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set inactive

22:31:56, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:31:52, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:31:46, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::ae22:bff:fea6:9243 is set inactive

22:31:46, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set inactive

22:31:42, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:31:34, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:31:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set inactive

22:31:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:31:29, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:31:23, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:1dca is set active

22:31:18, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:31:16, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:31:07, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:31:05, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::ae22:bff:fea6:9243 is set active

22:31:03, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:31:01, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set inactive

22:30:59, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:30:48, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:30:44, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:30:43, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:1dca is set active

22:30:43, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::ae22:bff:fea6:9243 is set active

22:30:43, 13 Jan.

wl1:A WiFi device <C0:EE:FB:50:1D:CA> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

22:30:38, 13 Jan.

wl1:A WiFi device <AC:22:0B:A6:92:43> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

22:30:22, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:30:18, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set active

22:30:16, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:1dca is set active

22:30:16, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:30:14, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:30:08, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:29:55, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:29:53, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:29:46, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:29:45, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:29:32, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:29:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set inactive

22:29:24, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:29:18, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:29:13, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:29:01, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:29:01, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set inactive

22:29:00, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:28:32, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:28:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:28:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::d1cb:63f3:d190:c40f is set inactive

22:28:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set inactive

22:28:24, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:28:15, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:27:44, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:27:42, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::d1cb:63f3:d190:c40f is set active

22:27:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:27:30, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:27:14, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:27:14, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::d1cb:63f3:d190:c40f is set active

22:27:13, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:27:08, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:27:02, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:27:01, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set inactive

22:27:00, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:26:51, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:26:46, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set inactive

22:26:34, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::c2ee:fbff:fe50:904f is set active

22:26:25, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:26:25, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:26:15, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::d1cb:63f3:d190:c40f is set inactive

22:26:02, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set active

22:25:57, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:25:56, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:25:52, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:25:45, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1cb:63f3:d190:c40f is set inactive

22:25:40, 13 Jan.

ppp1:DNS name resolution failure (teredo.ipv6.microsoft.com)

22:25:33, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d508:8954:e989:acda is set active

22:25:31, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::d1cb:63f3:d190:c40f is set active

22:25:30, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host fe80::a111:855:710e:e62f is set inactive

22:25:29, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:494:a627:28d3:dab4 is set active

22:25:23, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

22:25:11, 13 Jan.

BR_LAN:LAN Neighbor Discovery : Host 2a00:23c4:3305:6b00:d1e0:2655:835a:e95e is set active

22:25:03, 13 Jan.

eth1:IGMP join received for group 226.178.217.5 on interface eth1

Standard User

deleted
(deleted) Sat 14-Jan-17 03:07:01

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

I can't believe this thread is still going on. What stops you from calling BT again and getting them to raise a fault? I understand that (some of them) are Indians, but someone eventually must realize there's a serious problem when they see reconnection graph similar to this:
[IMG]http://i63.tinypic.com/21lsiaa.png[/IMG]
Just call them again.
As for the logs you're providing, they do not contain any relevant entries from wan or ppp interfaces - looks like your router doesn't log them.

Standard User

ukhardy07
(knowledge is power) Sat 14-Jan-17 13:08:05

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

I have asked you for stats at least twice now, nothing yet, this will help everyone a lot more than these IPV6 messages and logs which frankly we all see.

Standard User

ukhardy07
(knowledge is power) Sat 14-Jan-17 13:37:11

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

I ask again please provide the stats I've asked for twice all the stuff you're posting does nothing to help us... You are barking up the wrong tree looking at these things. Let us help you.

Standard User

deleted
(deleted) Sat 14-Jan-17 20:38:15

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: ukhardy07] [link to this post]

In reply to a post by Mml:
I can't believe this thread is still going on. What stops you from calling BT again and getting them to raise a fault? I understand that (some of them) are Indians, but someone eventually must realize there's a serious problem when they see reconnection graph similar to this:
[IMG]http://i63.tinypic.com/21lsiaa.png[/IMG]
Just call them again.
As for the logs you're providing, they do not contain any relevant entries from wan or ppp interfaces - looks like your router doesn't log them.

Nothing has stopped me from calling BT. They're the first people I contacted. My recent conversation with them they have suggested it may be a congestion problem on the network Which maybe the problem as when I'm on the PS4 playing, mid-game I will switch on my computer and I will instantly disconnect from the internet on my PS4. Any idea what I can do?

In reply to a post by ukhardy07:
I ask again please provide the stats I've asked for twice all the stuff you're posting does nothing to help us... You are barking up the wrong tree looking at these things. Let us help you.

Sorry that's my fault. Is this what you wanted?

Serial number: +084319+NQ63063146
Firmware version: SG4B10002244
Firmware updated: 15-Dec-2016
Board version: 1.0
Gui version: 1.32.0
DSL uptime: 2 Days, 2 Hours 59 Minutes 55 Seconds
Data rate: 10.00 kbps / 55.00 kbps
Maximum data rate: 25325 / 69733
Noise margin: 22.5 / 10.4
Line attenuation: 16.7
Signal attenuation:
VPI / VCI: 0/38
Modulation: G_993_2_ANNEX_B
Latency type: Fast Path
Data sent / received: 3822 MB Uploaded / 717 MB Downloaded
BT Wi-fi: Active
2.4 GHz wireless network name: BTHub6-PTMC
2.4 GHz wireless channel: Smart (Channel 11)
5 GHz wireless network name: BTHub6-PTMC
5 GHz wireless channel: Smart (Channel 36)
Wireless security: WPA2 (Recommended)
Band steering: Off
Wireless mode: Mode 1
Firewall: On
Software variant: -
Boot loader: 7.33.1

Administrator

MrSaffron
(staff) Sun 15-Jan-17 10:40:08

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Offshore call centre staff are frequently working with limited flexibility to diverge from scripted help and the same problems can and do occur no matter where a call centre is based.

THUS the phrase (some of them) are Indians is inappropriate, since it carries an undertone that the support is bad solely because the call centre staff are Indian.

NOTE: I am not saying you cannot say support is bad, if it is bad call it bad, but don't bring the nationality of the individual into the equation.

Andrew Ferguson, [email protected]
www.thinkbroadband.com
See if your ADSL stats are any good | UK broadband availability checker | Speed test for PC, tablets and mobiles

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.

Standard User

XRaySpeX
(eat-sleep-adslguide) Mon 16-Jan-17 19:42:27

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

Those stats don't make sense. 55K bps, or is it 10K bps, I can't make out which. on a Fibre line?

1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC

Standard User

IanBB
(committed) Mon 16-Jan-17 19:50:50

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: XRaySpeX] [link to this post]

They make sense if you substitute Mbps for kbps.

eg Data rate: 10.00 Mbps / 55.00 Mbps

Edited by IanBB (Mon 16-Jan-17 19:52:57)

Standard User

deleted
(deleted) Mon 16-Jan-17 19:57:11

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: deleted] [link to this post]

3822MB upload in two days at that speed is a lot... its not beyond the bounds of possibility that your connection is being flooded from within.

Standard User

XRaySpeX
(eat-sleep-adslguide) Mon 16-Jan-17 19:58:16

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: IanBB] [link to this post]

It does & if in the following line (Max Rate) you add ",000" to each side. Coincidence?

Are you telling me that the BT HH writes "K" when it means "M" or is OP hand editing his stats?

It has no trouble with MBs loaded. Why translate speeds?

1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC

Edited by XRaySpeX (Mon 16-Jan-17 20:04:10)

Standard User

RobertoS
(elder) Mon 16-Jan-17 22:07:41

Print Post

Re: Internet connection drops for 30 seconds frequently

[re: IanBB] [link to this post]

In reply to a post by IanBB:
They make sense if you substitute Mbps for kbps.

eg Data rate: 10.00 Mbps / 55.00 Mbps

In particular, given the attainable speeds, the OP would seem to be on the Openreach 55/10 product.

_{^{Kindness isn't going to cure the world of all its awfulness but it's a good place to begin. Daisy Ridley.}}
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 54999/14466Kbps @ 600m. BQMs - IPv4 & IPv6

Pages in this thread: 1 | 2 | 3 | 4 | >> (show all)

Jump to