[gentoo-user] Internet slow at times. Can't figure out why. ISP??

[gentoo-user] Internet slow at times. Can't figure out why. ISP??

[Dale]

[-- Attachment #1: Type: text/plain, Size: 5399 bytes --]

Hey,

As some may recall I bought a new router and modem.  I was sort of
hoping one or both of those would solve a issue I've noticed for a good
long while.  At times, my internet gets really slow, slower than it
should be at least.  I have DSL and it isn't to fast to begin with.  At
times tho, I'm only getting about 20 or 30% of what I should.  This is
what the modem shows for speed:


Downstream Rate     1536 Kbps
Upstream Rate     384 Kbps


Don't laugh OK.  I live in the sticks and for many years, I was lucky to
get 26K down on dial-up.  I hoping for faster one day but this is better
than dial-up, mostly.  ;-) 

Here's some info.  This slow down seems to always happen in the
evenings, somewhere between 6 and 9PM.  Generally, the rest of the time
it is pretty close to its max speed.  Because it works most of the time,
I'm thinking this is not hardware or cable related.  I'd think it more
consistently slow if it was.  That said, it does the same with any
modem, any router or any sets of cables.  I even bought some bulk cable
and ends then made my own cables and tested them with a ohm meter to be
sure they were really good.  No improvement.  I also disabled the
wireless on my cell phone to be sure it wasn't doing something funny. It
is set to download only when I tell it but there is one google thing
that ignores that. 

The only things I see is in the logs.  Here is some of the log from the
modem, currently the Netgear 7550. 


2020/04/06 21:54:15 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
MAC= SRC=185.175.93.23 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00
TTL=241 ID=29175 PROTO=TCP SPT=56054 DPT=5937 WINDOW=1024 RES=0x00 SYN
URGP=0 OPT (020405AC)

2020/04/06 21:54:13 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
MAC= SRC=176.113.115.54 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00
TTL=240 ID=34879 PROTO=TCP SPT=50930 DPT=1683 WINDOW=1024 RES=0x00 SYN
URGP=0 OPT (020405AC) 2020/04/06 21:54:03 CDT WRN | kernel |
logInboundBlocked:IN=ppp0 OUT= MAC= SRC=176.113.115.52
DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240 ID=21875 PROTO=TCP
SPT=50932 DPT=31240 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC)
2020/04/06 21:53:43 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
MAC= SRC=185.153.198.249 DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20
TTL=234 ID=8388 PROTO=TCP SPT=58950 DPT=33995 WINDOW=1024 RES=0x00 SYN
URGP=0 OPT (020405AC) 2020/04/06 21:53:39 CDT WRN | kernel |
ICMP:logOutboundBlocked:IN= OUT=ppp0 SRC=74.188.249.233
DST=152.32.191.35 LEN=34 TOS=0x00 PREC=0x00 TTL=64 ID=6687 PROTO=ICMP
TYPE=0 CODE=0 ID=16298 SEQ=0 2020/04/06 21:53:32 CDT WRN | kernel |
logInboundBlocked:IN=ppp0 OUT= MAC= SRC=51.178.78.153 DST=74.188.249.233
LEN=44 TOS=0x08 PREC=0x20 TTL=238 ID=54321 PROTO=TCP SPT=58684 DPT=8000
WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC) 2020/04/06 21:53:24 CDT
WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC= SRC=185.153.198.240
DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20 TTL=234 ID=43550 PROTO=TCP
SPT=50631 DPT=47025 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC)
2020/04/06 21:53:19 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
MAC= SRC=216.58.193.142 DST=74.188.249.233 LEN=40 TOS=0x00 PREC=0x80
TTL=121 ID=0 DF PROTO=TCP SPT=443 DPT=50020 WINDOW=0 RES=0x00 RST URGP=0
2020/04/06 21:53:01 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
MAC= SRC=146.88.240.4 DST=74.188.249.233 LEN=78 TOS=0x00 PREC=0x00
TTL=245 ID=54321 PROTO=UDP SPT=43443 DPT=137 LEN=58 2020/04/06 21:52:58
CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC=
SRC=176.113.115.247 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240
ID=64147 PROTO=TCP SPT=50902 DPT=31405 WINDOW=1024 RES=0x00 SYN URGP=0
OPT (020405AC) 2020/04/06 21:52:50 CDT WRN | kernel |
logInboundBlocked:IN=ppp0 OUT= MAC= SRC=170.106.36.63 DST=74.188.249.233
LEN=44 TOS=0x08 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=59903 DPT=5938
WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC)


I googled but didn't really find anything, good or bad, about those
entries. This is from the router, the TP-Link I bought a few months ago.


Index Time Type Level Log Content
199 Apr 6 21:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
198 Apr 6 21:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
197 Apr 6 21:21:57 DHCP INFO DHCPS:Send ACK to 192.168.0.101
196 Apr 6 21:21:57 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E
195 Apr 6 20:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
194 Apr 6 20:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
193 Apr 6 20:24:21 DHCP INFO DHCPS:Send ACK to 192.168.0.101
192 Apr 6 20:24:21 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E
191 Apr 6 19:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
190 Apr 6 19:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35


I'm only copying a small portion of it because it is very repetitive.
It's pretty much the same thing over and over again. I'm not thinking
those are errors tho. The router sure does send recv DHCP stuff often tho.

Does anyone see anything that is a problem here? I'm thinking my ISP is
just overloaded and throttling the connection. I've swapped hardware and
cables to the point that I don't see how it could be that. Possible I
guess but not sure how several cables, two routers and three modems, two
different brands, can all have the same issue.

Am I missing anything? Any other ideas? Thoughts?

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 6407 bytes --]

[gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[Ian Zimmerman]

On 2020-04-06 22:14, Dale wrote:

> I have DSL and it isn't to fast to begin with.  At
> times tho, I'm only getting about 20 or 30% of what I should.

Are you often on the phone at those times?  May it be poor filtering?

At my last residence - also "in the sticks", LOL - we had to give up on
DSL completely, because 6 times out of 10 when we got a phone call the
internet dropped.  Seriously.  We're not proud to support the Comcast
monopoly, but what a difference.

-- 
Ian

Re: [gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[J. Roeleveld]

On Tuesday, April 7, 2020 5:54:25 AM CEST Ian Zimmerman wrote:
> On 2020-04-06 22:14, Dale wrote:
> > I have DSL and it isn't to fast to begin with.  At
> > times tho, I'm only getting about 20 or 30% of what I should.
> 
> Are you often on the phone at those times?  May it be poor filtering?
> 
> At my last residence - also "in the sticks", LOL - we had to give up on
> DSL completely, because 6 times out of 10 when we got a phone call the
> internet dropped.  Seriously.  We're not proud to support the Comcast
> monopoly, but what a difference.

This is likely caused by NOT having a filter for every device.

Longer version:

DSL requires a splitter/filter between the wall-socket (where the phone 
normally plugs in) and the DSL modem. It also has a 2nd connection for the 
phone.

This filter needs to be installed between ALL phone-wall-sockets and any 
device plugged in.

(Alternatively, you place the filter at the main entry-point and connect the 
router from that filter and run the "phone" port to the rest of the house.)

Re: [gentoo-user] Internet slow at times. Can't figure out why. ISP??

[J. Roeleveld]

On Tuesday, April 7, 2020 5:14:14 AM CEST Dale wrote:
> Hey,
> 
> As some may recall I bought a new router and modem.  I was sort of
> hoping one or both of those would solve a issue I've noticed for a good
> long while.  At times, my internet gets really slow, slower than it
> should be at least.  I have DSL and it isn't to fast to begin with.  At
> times tho, I'm only getting about 20 or 30% of what I should.  This is
> what the modem shows for speed:
> 
> Downstream Rate     1536 Kbps
> Upstream Rate     384 Kbps
> 
> Don't laugh OK.  I live in the sticks and for many years, I was lucky to
> get 26K down on dial-up.  I hoping for faster one day but this is better
> than dial-up, mostly.  ;-)

If it works.
And I remember when I was stuck with a 14k4 modem in the olden days.

> Here's some info.  This slow down seems to always happen in the
> evenings, somewhere between 6 and 9PM.

Isn't this when people sit down to eat and possible start watching netflix or 
other streaming services?
Or the kids playing games before going to bed?

> Generally, the rest of the time
> it is pretty close to its max speed.  Because it works most of the time,
> I'm thinking this is not hardware or cable related.  I'd think it more
> consistently slow if it was.  That said, it does the same with any
> modem, any router or any sets of cables.  I even bought some bulk cable
> and ends then made my own cables and tested them with a ohm meter to be
> sure they were really good.  No improvement.  I also disabled the
> wireless on my cell phone to be sure it wasn't doing something funny. It
> is set to download only when I tell it but there is one google thing
> that ignores that. 

I agree. It doesn't sound like a hardware problem. If it were, the issue would 
be far more consistent and not limited to a, near fixed, time period.

> The only things I see is in the logs.  Here is some of the log from the
> modem, currently the Netgear 7550. 
> 
> 
> 2020/04/06 21:54:15 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
> MAC= SRC=185.175.93.23 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00
> TTL=241 ID=29175 PROTO=TCP SPT=56054 DPT=5937 WINDOW=1024 RES=0x00 SYN
> URGP=0 OPT (020405AC)
> 
> 2020/04/06 21:54:13 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
> MAC= SRC=176.113.115.54 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00
> TTL=240 ID=34879 PROTO=TCP SPT=50930 DPT=1683 WINDOW=1024 RES=0x00 SYN
> URGP=0 OPT (020405AC) 2020/04/06 21:54:03 CDT WRN | kernel |
> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=176.113.115.52
> DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240 ID=21875 PROTO=TCP
> SPT=50932 DPT=31240 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC)
> 2020/04/06 21:53:43 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
> MAC= SRC=185.153.198.249 DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20
> TTL=234 ID=8388 PROTO=TCP SPT=58950 DPT=33995 WINDOW=1024 RES=0x00 SYN
> URGP=0 OPT (020405AC) 2020/04/06 21:53:39 CDT WRN | kernel |
> ICMP:logOutboundBlocked:IN= OUT=ppp0 SRC=74.188.249.233
> DST=152.32.191.35 LEN=34 TOS=0x00 PREC=0x00 TTL=64 ID=6687 PROTO=ICMP
> TYPE=0 CODE=0 ID=16298 SEQ=0 2020/04/06 21:53:32 CDT WRN | kernel |
> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=51.178.78.153 DST=74.188.249.233
> LEN=44 TOS=0x08 PREC=0x20 TTL=238 ID=54321 PROTO=TCP SPT=58684 DPT=8000
> WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC) 2020/04/06 21:53:24 CDT
> WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC= SRC=185.153.198.240
> DST=74.188.249.233 LEN=44 TOS=0x08 PREC=0x20 TTL=234 ID=43550 PROTO=TCP
> SPT=50631 DPT=47025 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405AC)
> 2020/04/06 21:53:19 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
> MAC= SRC=216.58.193.142 DST=74.188.249.233 LEN=40 TOS=0x00 PREC=0x80
> TTL=121 ID=0 DF PROTO=TCP SPT=443 DPT=50020 WINDOW=0 RES=0x00 RST URGP=0
> 2020/04/06 21:53:01 CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT=
> MAC= SRC=146.88.240.4 DST=74.188.249.233 LEN=78 TOS=0x00 PREC=0x00
> TTL=245 ID=54321 PROTO=UDP SPT=43443 DPT=137 LEN=58 2020/04/06 21:52:58
> CDT WRN | kernel | logInboundBlocked:IN=ppp0 OUT= MAC=
> SRC=176.113.115.247 DST=74.188.249.233 LEN=44 TOS=0x00 PREC=0x00 TTL=240
> ID=64147 PROTO=TCP SPT=50902 DPT=31405 WINDOW=1024 RES=0x00 SYN URGP=0
> OPT (020405AC) 2020/04/06 21:52:50 CDT WRN | kernel |
> logInboundBlocked:IN=ppp0 OUT= MAC= SRC=170.106.36.63 DST=74.188.249.233
> LEN=44 TOS=0x08 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=59903 DPT=5938
> WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC)
> 
> 
> I googled but didn't really find anything, good or bad, about those
> entries. This is from the router, the TP-Link I bought a few months ago.

Looks like standard port-scanners. The logs indicate they are blocked. So 
should be ok. Make sure you have all the security settings enabled on the 
router (and only disable the ones that are causing issues)

> Index Time Type Level Log Content
> 199 Apr 6 21:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
> 198 Apr 6 21:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
> 197 Apr 6 21:21:57 DHCP INFO DHCPS:Send ACK to 192.168.0.101
> 196 Apr 6 21:21:57 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E
> 195 Apr 6 20:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
> 194 Apr 6 20:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
> 193 Apr 6 20:24:21 DHCP INFO DHCPS:Send ACK to 192.168.0.101
> 192 Apr 6 20:24:21 DHCP INFO DHCPS:Recv REQUEST from A8:87:B3:B4:F9:5E
> 191 Apr 6 19:57:17 DHCP INFO DHCPS:Send ACK to 192.168.0.100
> 190 Apr 6 19:57:17 DHCP INFO DHCPS:Recv REQUEST from 00:01:53:80:DC:35
> 
> I'm only copying a small portion of it because it is very repetitive.
> It's pretty much the same thing over and over again. I'm not thinking
> those are errors tho. The router sure does send recv DHCP stuff often tho.

That's not often. I see 80 entries in the log related to my DHCP server all 
having the same timestamp.

> Does anyone see anything that is a problem here? I'm thinking my ISP is
> just overloaded and throttling the connection. I've swapped hardware and
> cables to the point that I don't see how it could be that. Possible I
> guess but not sure how several cables, two routers and three modems, two
> different brands, can all have the same issue.
> 
> Am I missing anything? Any other ideas? Thoughts?

Personally, considering the timeperiod you mentioned, I am guessing your 
neighbours are all using the internet at the same time and the local exchange 
is not able to provide the full bandwidth to all the customers at the same 
time.

--
Joost

Re: [gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[Dale]

J. Roeleveld wrote:
> On Tuesday, April 7, 2020 5:54:25 AM CEST Ian Zimmerman wrote:
>> On 2020-04-06 22:14, Dale wrote:
>>> I have DSL and it isn't to fast to begin with.  At
>>> times tho, I'm only getting about 20 or 30% of what I should.
>> Are you often on the phone at those times?  May it be poor filtering?
>>
>> At my last residence - also "in the sticks", LOL - we had to give up on
>> DSL completely, because 6 times out of 10 when we got a phone call the
>> internet dropped.  Seriously.  We're not proud to support the Comcast
>> monopoly, but what a difference.
> This is likely caused by NOT having a filter for every device.
>
> Longer version:
>
> DSL requires a splitter/filter between the wall-socket (where the phone 
> normally plugs in) and the DSL modem. It also has a 2nd connection for the 
> phone.
>
> This filter needs to be installed between ALL phone-wall-sockets and any 
> device plugged in.
>
> (Alternatively, you place the filter at the main entry-point and connect the 
> router from that filter and run the "phone" port to the rest of the house.)
>
>

The phone part has been cut off for a long time.  The only wire left is
the one to the modem itself.  I forgot but I ran a brand new wire a good
while back when I moved the jack.  This is a long term issue tho.  I
might add, the DSL box up the road is full.  The only way a new person
can get DSL is if someone else cuts theirs off.  It's been full since
about three months after they installed the DSL box.  I actually have
some extra filters tho.  Since I don't have any use for them anymore.  lol 

It was a good thought tho.  I had a filter go bad once and it did wreak
havoc on the DSL.  Poor internet, DSL signal lost at times.  If the
phone rang or anyone picked up a phone, dead DSL for sure. 

Dale

:-)  :-) 

Re: [gentoo-user] Internet slow at times. Can't figure out why. ISP??

[Dale]

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

That's my thinking too.  At first, I thought it might just be the
websites I was visiting.  Keep in mind, I download videos, a lot.  I
thought maybe they were just being hit hard with users, as you say,
people eating dinner and watching videos, kids playing games etc.  I
tried other sites, even downloaded a source tarball that was large to
test the theory.  It was a little better but very little.  I know one of
my neighbors watches Netflix and other paid services a lot.  I was told
once that each DSL card is shared by two customers.  I wonder if I'm on
the same card as my neighbor and that card is the bottleneck?  Of
course, it could be the whole neighborhood too.  lol 

I thought I would mention just in case there was something I was missing
or those logs had some clue that went over my head.  Even tho google
didn't turn up any problems, it doesn't mean there wasn't one.  It was
worth a try a guess. 

Dale

:-)  :-) 

P. S. Got half my garden plowed up.  Waiting on a fresh batch of rain
later tonight and tomorrow, and maybe the next day too.  Killed the
weeds tho.  :/ 

Re: [gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[Michael]

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

On Tuesday, 7 April 2020 04:54:25 BST Ian Zimmerman wrote:
> On 2020-04-06 22:14, Dale wrote:
> > I have DSL and it isn't to fast to begin with.  At
> > times tho, I'm only getting about 20 or 30% of what I should.
> 
> Are you often on the phone at those times?  May it be poor filtering?
> 
> At my last residence - also "in the sticks", LOL - we had to give up on
> DSL completely, because 6 times out of 10 when we got a phone call the
> internet dropped.  Seriously.  We're not proud to support the Comcast
> monopoly, but what a difference.

This may have been caused by an MTU installed somewhere on the external line, 
which should be removed,[1] or it could have been a DECT phone - some were 
causing these problems and needed replacement or more than one ADSL filter 
inline - or it could be lengthy telephone extensions inside the house making 
acting as aerials and making the connection marginal for ADSL purposes.

[1] https://rdist.root.org/2009/02/04/fixing-dsl-lost-sync-problem/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[Michael]

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

On Tuesday, 7 April 2020 05:55:06 BST J. Roeleveld wrote:
> On Tuesday, April 7, 2020 5:54:25 AM CEST Ian Zimmerman wrote:
> > On 2020-04-06 22:14, Dale wrote:
> > > I have DSL and it isn't to fast to begin with.  At
> > > times tho, I'm only getting about 20 or 30% of what I should.
> > 
> > Are you often on the phone at those times?  May it be poor filtering?
> > 
> > At my last residence - also "in the sticks", LOL - we had to give up on
> > DSL completely, because 6 times out of 10 when we got a phone call the
> > internet dropped.  Seriously.  We're not proud to support the Comcast
> > monopoly, but what a difference.
> 
> This is likely caused by NOT having a filter for every device.
> 
> Longer version:
> 
> DSL requires a splitter/filter between the wall-socket (where the phone
> normally plugs in) and the DSL modem. It also has a 2nd connection for the
> phone.

It is not the ADSL modem which requires the filter, but the analogue 
telephone.  The filter cuts out audible frequencies so you can't hear them 
when you're making a call.  A failed/failing ADSL z-filter will be noticed 
because the line will suddenly have an audible hum/buz when you pick up the 
phone and press a button - or perform a quiet line test.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[Michael]

[-- Attachment #1: Type: text/plain, Size: 4799 bytes --]

On Tuesday, 7 April 2020 06:56:04 BST Dale wrote:
> J. Roeleveld wrote:
> > On Tuesday, April 7, 2020 5:54:25 AM CEST Ian Zimmerman wrote:
> >> On 2020-04-06 22:14, Dale wrote:
> >>> I have DSL and it isn't to fast to begin with.  At
> >>> times tho, I'm only getting about 20 or 30% of what I should.
> >> 
> >> Are you often on the phone at those times?  May it be poor filtering?
> >> 
> >> At my last residence - also "in the sticks", LOL - we had to give up on
> >> DSL completely, because 6 times out of 10 when we got a phone call the
> >> internet dropped.  Seriously.  We're not proud to support the Comcast
> >> monopoly, but what a difference.
> > 
> > This is likely caused by NOT having a filter for every device.
> > 
> > Longer version:
> > 
> > DSL requires a splitter/filter between the wall-socket (where the phone
> > normally plugs in) and the DSL modem. It also has a 2nd connection for the
> > phone.
> > 
> > This filter needs to be installed between ALL phone-wall-sockets and any
> > device plugged in.
> > 
> > (Alternatively, you place the filter at the main entry-point and connect
> > the router from that filter and run the "phone" port to the rest of the
> > house.)
> The phone part has been cut off for a long time.  The only wire left is
> the one to the modem itself.  I forgot but I ran a brand new wire a good
> while back when I moved the jack.  This is a long term issue tho.  I
> might add, the DSL box up the road is full.  The only way a new person
> can get DSL is if someone else cuts theirs off.  It's been full since
> about three months after they installed the DSL box.  I actually have
> some extra filters tho.  Since I don't have any use for them anymore.  lol 
> 
> It was a good thought tho.  I had a filter go bad once and it did wreak
> havoc on the DSL.  Poor internet, DSL signal lost at times.  If the
> phone rang or anyone picked up a phone, dead DSL for sure. 
> 
> Dale
> 
> :-)  :-) 

Removing/reducing unneeded internal telephone wiring and placing the modem as 
close as possible to the drop wire when it enters the house, is the best way 
to reduce noise on the line and be able to sync at higher speeds.

Getting the telecom provider to test the copper wire connections for high 
resistance faults between your house and the telephone exchange, is another 
approach to getting a higher ADSL sync speed.  It is unlikely privatised 
monopoly suppliers will get out of bed to do this on your request, no matter 
how much subsidy they pocket from the government supposedly to improve their 
infrastructure.

However, the problem you are describing is only related to poor wiring and 
copper telephone circuit faults if the modem reports dropped connections to 
the exchange.  If the modem remains connected without suddenly re-syncing with 
the exchange at lower speeds, but your downloads from the Internet reduce all 
the same, then the problem is one of an over-subscribed ADSL line.

Many ISPs tend to seek profit maximisation by over-subscribing their limited 
capacity infrastructure to more and more customers.  The contention ratio 
becomes too high if all customers suddenly start downloading 4K UHD videos 
from the Internet at the same time every evening, while using an 
infrastructure which was designed before the Internet was invented.  It used 
to be the case kids would return from school, go on the Internet and hammer 
youtube video downloads.  So just before dinner time the Internet grinds to 
halt, only to pick up again speed later at night, until early in the morning.  
In countries with free market competition (OK, don't laugh) there should be 
other ISPs available, who for a price will be able to offer you an ADSL 
service with a lower contention ratio.  Usually they sell these packages to 
business customers and of course charge more for the privilege.

In the last couple of weeks, in many countries around the world there has been 
a lockdown to reduce the spread of the Coronavirus and many people who can, 
now work from home.  This has increased the amount of videoconferencing and 
consequently the already burdened infrastructure is further constrained.  
However, this would cause a reduction in speeds during the day, than in the 
evening and it would be cause by upstream capacity getting exhausted, rather 
than what your ISP has provisioned your local exchange with.

A final point to note:  Bufferbloat.

On assymetric DSL the achievable downstream speed is limited by the capacity/
load on the upstream path.  Setting up traffic-shaping on your router on the 
upstream path will allow you to saturate the upstream and therefore maximise 
whatever downstream rate your line can deliver.

You can read more about it here:  

https://www.linksysinfo.org/index.php?threads/qos-tutorial.68795/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[Grant Edwards]

On 2020-04-07, Michael <confabulate@kintzios.com> wrote:
> On Tuesday, 7 April 2020 05:55:06 BST J. Roeleveld wrote:
>> On Tuesday, April 7, 2020 5:54:25 AM CEST Ian Zimmerman wrote:
>> > On 2020-04-06 22:14, Dale wrote:
>> > > I have DSL and it isn't to fast to begin with.  At
>> > > times tho, I'm only getting about 20 or 30% of what I should.
>> > 
>> > Are you often on the phone at those times?  May it be poor filtering?
>> > 
>> > At my last residence - also "in the sticks", LOL - we had to give up on
>> > DSL completely, because 6 times out of 10 when we got a phone call the
>> > internet dropped.  Seriously.  We're not proud to support the Comcast
>> > monopoly, but what a difference.
>> 
>> This is likely caused by NOT having a filter for every device.
>> 
>> Longer version:
>> 
>> DSL requires a splitter/filter between the wall-socket (where the phone
>> normally plugs in) and the DSL modem. It also has a 2nd connection for the
>> phone.
>
> It is not the ADSL modem which requires the filter, but the analogue 
> telephone.

My experience with multiple different installations is that lack of a
filter can pretty much kill the ADSL signal and redner the DSL mode
useless.


> The filter cuts out audible frequencies so you can't hear them 
> when you're making a call.

In my experience, it often also prevents the phones and connected
lines from presenting such a screwed up impedance to the DSL signal
that DSL stops working.

--
Grant

Re: [gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[J. Roeleveld]

On 7 April 2020 21:40:56 CEST, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>On 2020-04-07, Michael <confabulate@kintzios.com> wrote:
>> On Tuesday, 7 April 2020 05:55:06 BST J. Roeleveld wrote:
>>> On Tuesday, April 7, 2020 5:54:25 AM CEST Ian Zimmerman wrote:
>>> > On 2020-04-06 22:14, Dale wrote:
>>> > > I have DSL and it isn't to fast to begin with.  At
>>> > > times tho, I'm only getting about 20 or 30% of what I should.
>>> > 
>>> > Are you often on the phone at those times?  May it be poor
>filtering?
>>> > 
>>> > At my last residence - also "in the sticks", LOL - we had to give
>up on
>>> > DSL completely, because 6 times out of 10 when we got a phone call
>the
>>> > internet dropped.  Seriously.  We're not proud to support the
>Comcast
>>> > monopoly, but what a difference.
>>> 
>>> This is likely caused by NOT having a filter for every device.
>>> 
>>> Longer version:
>>> 
>>> DSL requires a splitter/filter between the wall-socket (where the
>phone
>>> normally plugs in) and the DSL modem. It also has a 2nd connection
>for the
>>> phone.
>>
>> It is not the ADSL modem which requires the filter, but the analogue 
>> telephone.
>
>My experience with multiple different installations is that lack of a
>filter can pretty much kill the ADSL signal and redner the DSL mode
>useless.
>
>
>> The filter cuts out audible frequencies so you can't hear them 
>> when you're making a call.
>
>In my experience, it often also prevents the phones and connected
>lines from presenting such a screwed up impedance to the DSL signal
>that DSL stops working.
>
>--
>Grant

The only time I have seen DSL work without a filter is when the modem is connected directly to the incoming port and no analog device can be connected anywhere in the line.

That location gets 60meg down and 20meg up.

I am also 100÷ certain noone can connect an analog phone as there is no plug available.

Reason why I said a filter is needed everywhere is because I have seen locations where the ADSL router was behind a filter, but the phone, connected to a different port, was not behind a filter.
The occupant of that house were quick to blame the router and ISP, but had difficulty realising the consistency of the connection dropping as soon as someone picked up the phone or the phone starting to ring.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: Internet slow at times. Can't figure out why. ISP??

[Dale]

J. Roeleveld wrote:
>
> The only time I have seen DSL work without a filter is when the modem is connected directly to the incoming port and no analog device can be connected anywhere in the line.
>
> That location gets 60meg down and 20meg up.
>
> I am also 100÷ certain noone can connect an analog phone as there is no plug available.
>
> Reason why I said a filter is needed everywhere is because I have seen locations where the ADSL router was behind a filter, but the phone, connected to a different port, was not behind a filter.
> The occupant of that house were quick to blame the router and ISP, but had difficulty realising the consistency of the connection dropping as soon as someone picked up the phone or the phone starting to ring.
>
> --
> Joost


The info that came with the modem and install kit also says that each
phone port must have a filter.  The modem however does not, unless you
use a filter and plug it into the modem port.  Basically, the modem has
to be connected directly to the phone line.  The phones have to be
filtered.  The filter removes or attenuates/isolates the DSL signal so
that the voice part still works. 

When I rewired the phone lines after cutting off the phone part, I only
connected the wire that goes to my modem, nothing else.  I removed the
wires that went to the old satellite box, the living room and other
phone lines that went somewhere.  Since I no longer have phone service,
why run those wires at all. 

Right now it is just after 3PM here.  My connection is already slow. 
It's been raining so I suspect everyone is inside watching TV and
surfing the net tho.  I'm getting around 40K down according to gkrellm. 
On occasion, I get several seconds of full speed or very close to it.  I
suspect the DSL box is just getting to much traffic. 

It is rumored that our local power company is about to offer internet
service.  One friend who has seen some info said it is well over
10MBs/sec.  I think she said her cost would be just a few dollars more
than what I'm paying now for 1.5MBs/sec.  You can bet, if it does come
here, I'm switching at lightening speed.  Of all the things I enjoy
most, internet and what I can do with it is the most important.  Videos
is the top thing, placing orders online and then being able to access
banking and such comes after that.  The first one is the bandwidth hog
tho.  It's also what I do most. 

I left dial-up behind.  Now I'm hoping for either cable or something
else faster, power company is possible, so I can leave this slow DSL
behind. 

Dale

:-)  :-)