1 |
On Tuesday, April 7, 2020 5:14:14 AM CEST Dale wrote: |
2 |
> Hey, |
3 |
> |
4 |
> As some may recall I bought a new router and modem. I was sort of |
5 |
> hoping one or both of those would solve a issue I've noticed for a good |
6 |
> long while. At times, my internet gets really slow, slower than it |
7 |
> should be at least. I have DSL and it isn't to fast to begin with. At |
8 |
> times tho, I'm only getting about 20 or 30% of what I should. This is |
9 |
> what the modem shows for speed: |
10 |
> |
11 |
> Downstream Rate 1536 Kbps |
12 |
> Upstream Rate 384 Kbps |
13 |
> |
14 |
> Don't laugh OK. I live in the sticks and for many years, I was lucky to |
15 |
> get 26K down on dial-up. I hoping for faster one day but this is better |
16 |
> than dial-up, mostly. ;-) |
17 |
|
18 |
If it works. |
19 |
And I remember when I was stuck with a 14k4 modem in the olden days. |
20 |
|
21 |
> Here's some info. This slow down seems to always happen in the |
22 |
> evenings, somewhere between 6 and 9PM. |
23 |
|
24 |
Isn't this when people sit down to eat and possible start watching netflix or |
25 |
other streaming services? |
26 |
Or the kids playing games before going to bed? |
27 |
|
28 |
> Generally, the rest of the time |
29 |
> it is pretty close to its max speed. Because it works most of the time, |
30 |
> I'm thinking this is not hardware or cable related. I'd think it more |
31 |
> consistently slow if it was. That said, it does the same with any |
32 |
> modem, any router or any sets of cables. I even bought some bulk cable |
33 |
> and ends then made my own cables and tested them with a ohm meter to be |
34 |
> sure they were really good. No improvement. I also disabled the |
35 |
> wireless on my cell phone to be sure it wasn't doing something funny. It |
36 |
> is set to download only when I tell it but there is one google thing |
37 |
> that ignores that. |
38 |
|
39 |
I agree. It doesn't sound like a hardware problem. If it were, the issue would |
40 |
be far more consistent and not limited to a, near fixed, time period. |
41 |
|
42 |
> The only things I see is in the logs. Here is some of the log from the |
43 |
> modem, currently the Netgear 7550. |
44 |
> |
45 |
> |
46 |
> 2020/04/06 21:54:15 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= |
47 |
> MAC= SRC=185.175.93.23 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 |
48 |
> TTL=241 ID=29175 PROTO=TCP SPT=56054 DPT=5937 WINDOW=1024 RES=0x00 SYN |
49 |
> URGP=0 OPT (020405AC) |
50 |
> |
51 |
> 2020/04/06 21:54:13 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= |
52 |
> MAC= SRC=176.113.115.54 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 |
53 |
> TTL=240 ID=34879 PROTO=TCP SPT=50930 DPT=1683 WINDOW=1024 RES=0x00 SYN |
54 |
> URGP=0 OPT (020405AC) 2020/04/06 21:54:03 CDT WRN | kernel | |
55 |
> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=176.113.115.52 |
56 |
> DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240 ID=21875 PROTO=TCP |
57 |
> SPT=50932 DPT=31240 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC) |
58 |
> 2020/04/06 21:53:43 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= |
59 |
> MAC= SRC=185.153.198.249 DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20 |
60 |
> TTL=234 ID=8388 PROTO=TCP SPT=58950 DPT=33995 WINDOW=1024 RES=0x00 SYN |
61 |
> URGP=0 OPT (020405AC) 2020/04/06 21:53:39 CDT WRN | kernel | |
62 |
> ICMP:logOutboundBlocked:IN= OUT=ppp0 SRC=74.188.249.233 |
63 |
> DST=152.32.191.35 LEN=34 TOS=0x00 PREC=0x00 TTL=64 ID=6687 PROTO=ICMP |
64 |
> TYPE=0 CODE=0 ID=16298 SEQ=0 2020/04/06 21:53:32 CDT WRN | kernel | |
65 |
> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=51.178.78.153 DST=74.188.249.233 |
66 |
> LEN=44 TOS=0x08 PREC=0x20 TTL=238 ID=54321 PROTO=TCP SPT=58684 DPT=8000 |
67 |
> WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC) 2020/04/06 21:53:24 CDT |
68 |
> WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC= SRC=185.153.198.240 |
69 |
> DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20 TTL=234 ID=43550 PROTO=TCP |
70 |
> SPT=50631 DPT=47025 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC) |
71 |
> 2020/04/06 21:53:19 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= |
72 |
> MAC= SRC=216.58.193.142 DST=74.188.249.233 LEN=40 TOS=0x00 PREC=0x80 |
73 |
> TTL=121 ID=0 DF PROTO=TCP SPT=443 DPT=50020 WINDOW=0 RES=0x00 RST URGP=0 |
74 |
> 2020/04/06 21:53:01 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= |
75 |
> MAC= SRC=146.88.240.4 DST=74.188.249.233 LEN=78 TOS=0x00 PREC=0x00 |
76 |
> TTL=245 ID=54321 PROTO=UDP SPT=43443 DPT=137 LEN=58 2020/04/06 21:52:58 |
77 |
> CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC= |
78 |
> SRC=176.113.115.247 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240 |
79 |
> ID=64147 PROTO=TCP SPT=50902 DPT=31405 WINDOW=1024 RES=0x00 SYN URGP=0 |
80 |
> OPT (020405AC) 2020/04/06 21:52:50 CDT WRN | kernel | |
81 |
> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=170.106.36.63 DST=74.188.249.233 |
82 |
> LEN=44 TOS=0x08 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=59903 DPT=5938 |
83 |
> WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC) |
84 |
> |
85 |
> |
86 |
> I googled but didn't really find anything, good or bad, about those |
87 |
> entries. This is from the router, the TP-Link I bought a few months ago. |
88 |
|
89 |
Looks like standard port-scanners. The logs indicate they are blocked. So |
90 |
should be ok. Make sure you have all the security settings enabled on the |
91 |
router (and only disable the ones that are causing issues) |
92 |
|
93 |
> Index Time Type Level Log Content |
94 |
> 199 Apr 6 21:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100 |
95 |
> 198 Apr 6 21:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35 |
96 |
> 197 Apr 6 21:21:57 DHCP INFO DHCPS:Send ACK to 192.168.0.101 |
97 |
> 196 Apr 6 21:21:57 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E |
98 |
> 195 Apr 6 20:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100 |
99 |
> 194 Apr 6 20:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35 |
100 |
> 193 Apr 6 20:24:21 DHCP INFO DHCPS:Send ACK to 192.168.0.101 |
101 |
> 192 Apr 6 20:24:21 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E |
102 |
> 191 Apr 6 19:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100 |
103 |
> 190 Apr 6 19:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35 |
104 |
> |
105 |
> I'm only copying a small portion of it because it is very repetitive. |
106 |
> It's pretty much the same thing over and over again. I'm not thinking |
107 |
> those are errors tho. The router sure does send recv DHCP stuff often tho. |
108 |
|
109 |
That's not often. I see 80 entries in the log related to my DHCP server all |
110 |
having the same timestamp. |
111 |
|
112 |
> Does anyone see anything that is a problem here? I'm thinking my ISP is |
113 |
> just overloaded and throttling the connection. I've swapped hardware and |
114 |
> cables to the point that I don't see how it could be that. Possible I |
115 |
> guess but not sure how several cables, two routers and three modems, two |
116 |
> different brands, can all have the same issue. |
117 |
> |
118 |
> Am I missing anything? Any other ideas? Thoughts? |
119 |
|
120 |
Personally, considering the timeperiod you mentioned, I am guessing your |
121 |
neighbours are all using the internet at the same time and the local exchange |
122 |
is not able to provide the full bandwidth to all the customers at the same |
123 |
time. |
124 |
|
125 |
-- |
126 |
Joost |