Broadband turns off every night at 21:00 GMT

[Fornever]

I have been having a recurring issue where every day, at around 21:00 GMT, my Sky broadband goes out for about two to five minutes. I'm getting sick of this happening almost every day since I am always using the computer and the internet at that time. I want to be paying for a connection that doesn't drop out every time for no explained reason - I want my internet to be up and running 24/7.


Is it Sky doing this? Or could there perhaps be some sort of maintenance going on? I would like to know why this is happening, especially at a time such as 21:00 GMT when everyone is still up.

>Believe in Better
Yeah, maybe when you stop turning off my internet every night and not explaining why, thanks.

[hutchinsondave]

It may be due to some kind of electrical or wireless signal interference. I've heard of cases where central heating or something else operated by a timer has switched on at that time and caused the loss. Christmas tree lights, florescent lights too. Whilst working for another broadband provider there were also instances of electric garage doors causing the issue.

[Isitme]

Is the internet dropping out or is it your wireless connection that is dropping?Copy and paste your router Log here and someone may be able to suggest what is wrong. Router settings>Security tab>Logs.

[Fornever]

Jan 1 00:00:07 (none) user.crit kernel: eth0 Link UP 100 mbps full duplexJan 1 00:00:15 (none) user.crit kernel: Line 0: xDSL G.994 training
Jan 1 00:00:31 (none) user.crit kernel: Line 0: ADSL G.992 started
Jan 1 00:00:36 (none) user.crit kernel: Line 0: ADSL G.992 channel analysis
Jan 1 00:00:42 (none) user.crit kernel: Line 0: ADSL G.992 message exchange
Jan 1 00:00:43 (none) user.crit kernel: Line 0: ADSL link down
Jan 1 00:00:44 (none) user.crit kernel: Line 0: xDSL G.994 training
Jan 1 00:01:00 (none) user.crit kernel: Line 0: ADSL G.992 started
Jan 1 00:01:05 (none) user.crit kernel: Line 0: ADSL G.992 channel analysis
Jan 1 00:01:09 (none) user.crit kernel: eth0 Link DOWN.
Jan 1 00:01:11 (none) user.crit kernel: eth0 Link UP 100 mbps full duplex
Jan 1 00:01:11 (none) user.crit kernel: Line 0: ADSL G.992 message exchange
Jan 1 00:01:12 (none) user.crit kernel: Line 0: ADSL link up, Bearer 0, us=987, ds=3695
Jan 1 00:01:12 (none) user.crit kernel: Line 0: ADSL link up, Bearer 1, us=0, ds=0
Jan 1 00:01:32 (none) daemon.crit syslog: PPP LCP UP.
Jan 1 00:02:34 (none) daemon.crit syslog: Received valid IP address from server. Connection UP.
Dec 8 23:19:10 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=61.174.50.198 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=103 ID=256 PROTO=TCP SPT=6000 DPT=22 WINDOW=16384 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:21:10 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=203.198.119.135 DST=90.201.18.173 LEN=60 TOS=0x00 PREC=0x00 TTL=49 ID=62422 PROTO=TCP SPT=54562 DPT=8080 WINDOW=5840 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:23:25 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=218.77.79.43 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=44256 DPT=23 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:32:58 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=222.186.56.177 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=112 ID=256 PROTO=TCP SPT=77 DPT=8088 WINDOW=16384 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:36:55 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=61.174.51.212 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=103 ID=256 PROTO=TCP SPT=6000 DPT=22 WINDOW=16384 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:38:41 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=183.99.145.131 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=0 DF PROTO=TCP SPT=46438 DPT=23 WINDOW=300 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:44:21 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=61.160.224.128 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=54321 PROTO=TCP SPT=54011 DPT=21 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:49:41 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=1.161.25.11 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=107 ID=256 DF PROTO=TCP SPT=12200 DPT=1080 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:51:48 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=176.41.212.4 DST=90.201.18.173 LEN=52 TOS=0x00 PREC=0x00 TTL=110 ID=32089 DF PROTO=TCP SPT=50366 DPT=443 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:51:49 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=41.142.54.63 DST=90.201.18.173 LEN=64 TOS=0x00 PREC=0x00 TTL=114 ID=39876 DF PROTO=TCP SPT=2464 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:51:51 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=176.41.212.4 DST=90.201.18.173 LEN=52 TOS=0x00 PREC=0x00 TTL=110 ID=32107 DF PROTO=TCP SPT=50366 DPT=443 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:51:51 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=41.142.54.63 DST=90.201.18.173 LEN=64 TOS=0x00 PREC=0x00 TTL=114 ID=40057 DF PROTO=TCP SPT=2464 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 8 23:51:57 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=41.142.54.63 DST=90.201.18.173 LEN=64 TOS=0x00 PREC=0x00 TTL=114 ID=40453 DF PROTO=TCP SPT=2464 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 9 00:06:47 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=88.88.12.226 DST=90.201.18.173 LEN=60 TOS=0x00 PREC=0x00 TTL=57 ID=47418 DF PROTO=TCP SPT=45718 DPT=8080 WINDOW=14600 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 9 00:06:48 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=88.88.12.226 DST=90.201.18.173 LEN=60 TOS=0x00 PREC=0x00 TTL=57 ID=47419 DF PROTO=TCP SPT=45718 DPT=8080 WINDOW=14600 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 9 00:07:10 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=142.217.95.24 DST=90.201.18.173 LEN=52 TOS=0x00 PREC=0x00 TTL=118 ID=20984 DF PROTO=TCP SPT=54896 DPT=80 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 9 00:07:10 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=121.216.155.121 DST=90.201.18.173 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=11382 DF PROTO=TCP SPT=61759 DPT=443 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 9 00:07:13 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=142.217.95.24 DST=90.201.18.173 LEN=52 TOS=0x00 PREC=0x00 TTL=118 ID=20987 DF PROTO=TCP SPT=54896 DPT=80 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 9 00:16:58 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=112.85.42.106 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=49888 PROTO=TCP SPT=40520 DPT=9064 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Dec 9 00:31:18 (none) user.alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=122.226.73.131 DST=90.201.18.173 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=7341 PROTO=TCP SPT=50332 DPT=5432 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000

........

[Isitme]

You are showing a large number of attempted intrusions. You could try power cycling the router by switching off the power for a few minutes then switch on again, this should give you a new IP address, which may cut these out. Unless you really require it, for bandwidth meter or such like, I would also disable 'Respond to ping' on the WAN connection if it is enabled. Some will disagree with this but I believe it is a security risk and it should cut down the intrusion attempts.

[DFM]

Are you using AVAST & F@ST2504n ?

I’ve seen several posts on Sky and Avast forums of people with similar problems since around 20th Nov when AVAST introduced “Home Network Security”
I’ve been running RouterStats-Lites(v9.9) for a few days to log the pattern of cut offs.

I can manually run a Home Network Security scan and it turns the ADSL connection off. It looks like AVAST runs this twice a day.
Turning the feature off on each pc via Settings / Tools and selecting Home Network Security to OFF (and a reboot for it to take effect) seems to have cured the problem.