RSS Logo

by Mountaineerbr

#31 - Arrgh! Internet Issues


Estava um pouco preocupado que minha brincadeira de configurar uma conexão com a rede do bitcoin pudesse ter atraído olhares de pares ruins, mas nada disso.

Os problemas de internet que tenho sofrendo há duas semanas foram finalmente esclarecidos hoje quando um técnico do provedor de serviço de internet veio até minha casa. Não achou nada anormal com meu router. Falou que outro vizinho estava com o mesmo problema e que eles então iriam fazer manutenção em uma central do meu bairro. Mas os problemas ainda não acabaram..


The internet service provider technician came to my home and checked my local connection and the modem and that was all fine.

There was a huge problem going on with the neighbourhood internet for the past two weeks and only today I was let know about that!

The problemas were a very slow internet connection, specially bas was the upload transmission, and pinging from Linux Shell or even from the router itself (through the tools page), showed a 30% or more packet loss!

I was a little worried when the technician asked to use my laptop to test internet speed and to log in to the router. Maybe he would start typing speedtest for example, and Firefox would suggest him naughty websites starting with suck.. and alike. I don't know why these sort of suggestions pop up sometimes but I told the guy to ignore anything unusual in my computer..

After the guy finished checking the router, he said they would work on hardware maintenance in my area as another neighbour client of mine was having similar issues and noise was detected by another technician guy in one of their distribution equipment about my neighbourhood.

I was a little preoccupied my messing with opening ports and granting access from bitcoin network had attracted attention from bad peers but, alas, that seems to have been just a regular a problem of the internet provider..

The technician did reconfigure my router so now it has got a new SSID and password. The administration login name and its password to access router settings, such as opening ports, also changed and these were not given to me and I forgot to ask. Even though internet speed is nominal now, I had to schedule another technical visit for tomorrow.. Hopefully that will be the last for a long time!


On another note, I am messing about with a tumblelog from John Bokma. It is really a nice micro blog generator and I am using it, with modifications, to present a stand-alone version of podcast episode index.

There is some work left to be done so I am not yet adding any links to it from other pages, but eventually there will be more hints to find it.


Finally, internet is super fast and with the router administrator details in hand port forwarding could be enabled!


Table 1. Ssample of bitcoind connections. That is the output from bitcoin-cli getpeerinfo.
Software version Connection type
/Satoshi:0.18.0/ ipv4
/Satoshi:0.18.1/ onion
/Satoshi:0.21.0/ ipv4
/Satoshi:0.20.1/ ipv4
/Satoshi:0.21.0/ ipv4
/Satoshi:0.21.0/ ipv4
/dsn.tm.kit.edu/bitcoin:0.9.99/ ipv6
/Satoshi:0.21.0/ ipv4
/Satoshi:0.20.1/ ipv4
/Satoshi:0.20.0/ ipv4
/dsn.tm.kit.edu/bitcoin:0.9.99/ ipv6
/bitnodes.io:0.2/ ipv6
/bitnodes.earn.com:0.1/ ipv6
/bitnodes.io:0.2/ ipv6
/Satoshi:0.19.1/ ipv4
/Satoshi:0.21.0/ ipv6
/nodes.multiven.io:0.1/ ipv6
Bitcoind screenshot
Fig. 1 Running bitcoind on clearnet and onion networks with inbound and outbound connections on IPv4 and IPv6. Most onion peers are running an inferior bitcoind versions (Tor v3 vs. v2 incompatibility) so it may be a few days before inbound connections are made with onion peers..