[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] Really bad ISP
Hi,
You can check if there is no physical problem on your line, just in case
! Connect to your modem integrated web ui and check ATM statistics of
your DSL line.
Of course the first step is to watch the "DSL" signal light when you are
disconnected. If it's a loss of DSL signal then it's a physical/local
problem ! After some checks you can ask your ISP for maintenance on your
line. Or try another ISP if this one is unable to find and repair your
line (hoping that the next one will be able to do it fine).
But if the DSL connection is running fine when you cannot access
anything anymore, then it's your provider's network that is down (then
you must probably find another one !).
Some useful information :
SNR margin should be, for an optimized bandwidth/stability, 6dB (it
means that the useful signal is 4 times stronger (in milliwatts) than
the noise on your line); it can be moving to 4 to 8 between hours but
it's generally supposed to be smooth along hours. Some providers
settings are different (10dB target margin, with a small loss of
bandwidth).
When connected, check your upload/download ATM Speed and the SNR Margin
for both upload and download. In electronics 3dB is a good minimal
standard, but for telecommunication lines, the standard value is
multiplied by two because of environments induced noise that is moving
along the day. If the Margin is going under 3dB and is still going down,
you're probably going to be disconnected soon, and then reconnected with
a lower bandwidth (and may be a new IP address).
If SNR margin is moving up and down (like 11db, 2db, 7dB, 9dB, 3dB, and
disconnected for example) and a very different bandwidth at each
connection, then you have a problem on your physical line !
Useful tip for reparation : a line is not just a conductor, it's a very
long conductor like an antenna, capacitor and lot of things. Then
"injecting" signal into it needs a certain amount of milliwatts. At the
other side of the line, "reading" the signal doesn't really need to
consume current.
So, when there is a defective contact near your home, your download
bandwidth is quite clean. But your upload bandwith is low and changing
between each new connection. In that case, check all your connections
and cable.
At the opposite, when the is a weak contact into the ISP equipments,
your upload bandwidth is generally fine and stable, but not your
download bandwidth / SNR Margin. Then in that case, it's very easy for
your ISP to fix it.
Sometimes, it's one of the modem at one side that is defective.
Also, if connection problems are occurring at particular events
(switching on some device for example) you can try to find what :
sometimes there is devices (set top boxes or anything else) that are
defective and doing a lot of electronic high frequency noise into cables
and electric wires, it's a frequent case that can make your line (and
your neighbors lines !) to stop working fine. If so, change/repair the
device or his power supply unit ! If it's your neighbors, only an
official technician can do the job to find who and what.
Good luck ;)
Best regards,
Julien ROBIN
Le 26/10/2016 à 10:11, Lluís a écrit :
Hello,
I am a relay operator in Spain (or at least I try to).
I am just desperate with my ISP, he is just leaving the
VDSL2 connection down several times a day, taking the relay with it.
Does anyone know a much more stable, tor-friendly, ISP for an
Spanish user ?
The following record of assigned IPs in a **single** day shows
the dimension of the drama:
95.23.157.152 - Tue Oct 25 01:00:02 CEST 2016
95.23.156.52 - Tue Oct 25 07:00:02 CEST 2016
95.23.157.180 - Tue Oct 25 11:54:06 CEST 2016
188.79.227.152 - Tue Oct 25 12:20:52 CEST 2016
95.23.155.112 - Tue Oct 25 13:12:30 CEST 2016
95.23.144.75 - Tue Oct 25 13:15:19 CEST 2016
188.77.208.15 - Tue Oct 25 13:29:02 CEST 2016
95.23.159.249 - Tue Oct 25 14:00:06 CEST 2016
95.23.146.89 - Tue Oct 25 14:12:12 CEST 2016
95.23.159.163 - Tue Oct 25 14:19:21 CEST 2016
188.79.238.188 - Tue Oct 25 14:34:55 CEST 2016
188.79.237.90 - Tue Oct 25 14:36:05 CEST 2016
188.79.229.164 - Tue Oct 25 14:57:30 CEST 2016
95.23.149.124 - Tue Oct 25 15:08:51 CEST 2016
188.79.237.0 - Tue Oct 25 15:10:12 CEST 2016
188.77.213.199 - Tue Oct 25 16:28:47 CEST 2016
95.23.153.98 - Tue Oct 25 16:32:50 CEST 2016
95.23.146.46 - Tue Oct 25 16:49:03 CEST 2016
188.79.235.239 - Tue Oct 25 17:10:03 CEST 2016
188.77.215.232 - Tue Oct 25 17:20:03 CEST 2016
95.23.146.36 - Tue Oct 25 17:30:03 CEST 2016
95.23.148.238 - Tue Oct 25 18:10:03 CEST 2016
95.23.149.136 - Tue Oct 25 18:20:03 CEST 2016
188.77.211.53 - Tue Oct 25 18:50:03 CEST 2016
188.77.211.90 - Tue Oct 25 19:30:03 CEST 2016
188.79.225.153 - Tue Oct 25 20:10:01 CEST 2016
95.23.157.171 - Tue Oct 25 21:00:02 CEST 2016
188.77.212.227 - Tue Oct 25 22:00:02 CEST 2016
95.23.157.179 - Tue Oct 25 22:30:02 CEST 2016
Thanks for your assintance,
Lluís
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays