Gentoo Archives: gentoo-user

From: Dale <rdalek1967@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Internet slow at times. Can't figure out why. ISP??
Date: Tue, 07 Apr 2020 06:04:38
Message-Id: 9acf6741-f4f9-3cea-f4f6-a443799fdea4@gmail.com
In Reply to: Re: [gentoo-user] Internet slow at times. Can't figure out why. ISP?? by "J. Roeleveld"
1 J. Roeleveld wrote:
2 > On Tuesday, April 7, 2020 5:14:14 AM CEST Dale wrote:
3 >> Hey,
4 >>
5 >> As some may recall I bought a new router and modem. I was sort of
6 >> hoping one or both of those would solve a issue I've noticed for a good
7 >> long while. At times, my internet gets really slow, slower than it
8 >> should be at least. I have DSL and it isn't to fast to begin with. At
9 >> times tho, I'm only getting about 20 or 30% of what I should. This is
10 >> what the modem shows for speed:
11 >>
12 >> Downstream Rate 1536 Kbps
13 >> Upstream Rate 384 Kbps
14 >>
15 >> Don't laugh OK. I live in the sticks and for many years, I was lucky to
16 >> get 26K down on dial-up. I hoping for faster one day but this is better
17 >> than dial-up, mostly. ;-)
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 > Isn't this when people sit down to eat and possible start watching netflix or
24 > other streaming services?
25 > Or the kids playing games before going to bed?
26 >
27 >> Generally, the rest of the time
28 >> it is pretty close to its max speed. Because it works most of the time,
29 >> I'm thinking this is not hardware or cable related. I'd think it more
30 >> consistently slow if it was. That said, it does the same with any
31 >> modem, any router or any sets of cables. I even bought some bulk cable
32 >> and ends then made my own cables and tested them with a ohm meter to be
33 >> sure they were really good. No improvement. I also disabled the
34 >> wireless on my cell phone to be sure it wasn't doing something funny. It
35 >> is set to download only when I tell it but there is one google thing
36 >> that ignores that.
37 > I agree. It doesn't sound like a hardware problem. If it were, the issue would
38 > be far more consistent and not limited to a, near fixed, time period.
39 >
40 >> The only things I see is in the logs. Here is some of the log from the
41 >> modem, currently the Netgear 7550.
42 >>
43 >>
44 >> 2020/04/06 21:54:15 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
45 >> MAC= SRC=185.175.93.23 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00
46 >> TTL=241 ID=29175 PROTO=TCP SPT=56054 DPT=5937 WINDOW=1024 RES=0x00 SYN
47 >> URGP=0 OPT (020405AC)
48 >>
49 >> 2020/04/06 21:54:13 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
50 >> MAC= SRC=176.113.115.54 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00
51 >> TTL=240 ID=34879 PROTO=TCP SPT=50930 DPT=1683 WINDOW=1024 RES=0x00 SYN
52 >> URGP=0 OPT (020405AC) 2020/04/06 21:54:03 CDT WRN | kernel |
53 >> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=176.113.115.52
54 >> DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240 ID=21875 PROTO=TCP
55 >> SPT=50932 DPT=31240 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC)
56 >> 2020/04/06 21:53:43 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
57 >> MAC= SRC=185.153.198.249 DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20
58 >> TTL=234 ID=8388 PROTO=TCP SPT=58950 DPT=33995 WINDOW=1024 RES=0x00 SYN
59 >> URGP=0 OPT (020405AC) 2020/04/06 21:53:39 CDT WRN | kernel |
60 >> ICMP:logOutboundBlocked:IN= OUT=ppp0 SRC=74.188.249.233
61 >> DST=152.32.191.35 LEN=34 TOS=0x00 PREC=0x00 TTL=64 ID=6687 PROTO=ICMP
62 >> TYPE=0 CODE=0 ID=16298 SEQ=0 2020/04/06 21:53:32 CDT WRN | kernel |
63 >> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=51.178.78.153 DST=74.188.249.233
64 >> LEN=44 TOS=0x08 PREC=0x20 TTL=238 ID=54321 PROTO=TCP SPT=58684 DPT=8000
65 >> WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC) 2020/04/06 21:53:24 CDT
66 >> WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC= SRC=185.153.198.240
67 >> DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20 TTL=234 ID=43550 PROTO=TCP
68 >> SPT=50631 DPT=47025 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC)
69 >> 2020/04/06 21:53:19 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
70 >> MAC= SRC=216.58.193.142 DST=74.188.249.233 LEN=40 TOS=0x00 PREC=0x80
71 >> TTL=121 ID=0 DF PROTO=TCP SPT=443 DPT=50020 WINDOW=0 RES=0x00 RST URGP=0
72 >> 2020/04/06 21:53:01 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
73 >> MAC= SRC=146.88.240.4 DST=74.188.249.233 LEN=78 TOS=0x00 PREC=0x00
74 >> TTL=245 ID=54321 PROTO=UDP SPT=43443 DPT=137 LEN=58 2020/04/06 21:52:58
75 >> CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC=
76 >> SRC=176.113.115.247 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240
77 >> ID=64147 PROTO=TCP SPT=50902 DPT=31405 WINDOW=1024 RES=0x00 SYN URGP=0
78 >> OPT (020405AC) 2020/04/06 21:52:50 CDT WRN | kernel |
79 >> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=170.106.36.63 DST=74.188.249.233
80 >> LEN=44 TOS=0x08 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=59903 DPT=5938
81 >> WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC)
82 >>
83 >>
84 >> I googled but didn't really find anything, good or bad, about those
85 >> entries. This is from the router, the TP-Link I bought a few months ago.
86 > Looks like standard port-scanners. The logs indicate they are blocked. So
87 > should be ok. Make sure you have all the security settings enabled on the
88 > router (and only disable the ones that are causing issues)
89 >
90 >> Index Time Type Level Log Content
91 >> 199 Apr 6 21:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
92 >> 198 Apr 6 21:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
93 >> 197 Apr 6 21:21:57 DHCP INFO DHCPS:Send ACK to 192.168.0.101
94 >> 196 Apr 6 21:21:57 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E
95 >> 195 Apr 6 20:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
96 >> 194 Apr 6 20:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
97 >> 193 Apr 6 20:24:21 DHCP INFO DHCPS:Send ACK to 192.168.0.101
98 >> 192 Apr 6 20:24:21 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E
99 >> 191 Apr 6 19:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
100 >> 190 Apr 6 19:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
101 >>
102 >> I'm only copying a small portion of it because it is very repetitive.
103 >> It's pretty much the same thing over and over again. I'm not thinking
104 >> those are errors tho. The router sure does send recv DHCP stuff often tho.
105 > That's not often. I see 80 entries in the log related to my DHCP server all
106 > having the same timestamp.
107 >
108 >> Does anyone see anything that is a problem here? I'm thinking my ISP is
109 >> just overloaded and throttling the connection. I've swapped hardware and
110 >> cables to the point that I don't see how it could be that. Possible I
111 >> guess but not sure how several cables, two routers and three modems, two
112 >> different brands, can all have the same issue.
113 >>
114 >> Am I missing anything? Any other ideas? Thoughts?
115 > Personally, considering the timeperiod you mentioned, I am guessing your
116 > neighbours are all using the internet at the same time and the local exchange
117 > is not able to provide the full bandwidth to all the customers at the same
118 > time.
119 >
120 > --
121 > Joost
122 >
123 >
124
125 That's my thinking too.  At first, I thought it might just be the
126 websites I was visiting.  Keep in mind, I download videos, a lot.  I
127 thought maybe they were just being hit hard with users, as you say,
128 people eating dinner and watching videos, kids playing games etc.  I
129 tried other sites, even downloaded a source tarball that was large to
130 test the theory.  It was a little better but very little.  I know one of
131 my neighbors watches Netflix and other paid services a lot.  I was told
132 once that each DSL card is shared by two customers.  I wonder if I'm on
133 the same card as my neighbor and that card is the bottleneck?  Of
134 course, it could be the whole neighborhood too.  lol 
135
136 I thought I would mention just in case there was something I was missing
137 or those logs had some clue that went over my head.  Even tho google
138 didn't turn up any problems, it doesn't mean there wasn't one.  It was
139 worth a try a guess. 
140
141 Dale
142
143 :-)  :-) 
144
145 P. S. Got half my garden plowed up.  Waiting on a fresh batch of rain
146 later tonight and tomorrow, and maybe the next day too.  Killed the
147 weeds tho.  :/