Upgraded relay non show in ATLAS
Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-25 17:41 CET Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.41 seconds From the outside you cant be reached. Markus
On 25. Jan 2018, at 15:12, MLTor Node <ml.tor.node@gmail.com> wrote:
Hi to all! i have a little relay running in my home LAN on Windows 2016 server (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i create two VLan on my home network, one dedicated for my Tor relay. Today i updated service to 3.2.9 release.
After starting tor service, log say that Orport and DIRport are reachable from outside, so it seems to be working without problems. But if i query Atlas, my node seems to be down from 5 days. The IP showed in Atlas is old (i have dynamic IP and dynamic DNS). I stop and start several times service with no luck.
Anyone can help me? My node is small, but i like very much Tor and i want to continue contributing to the project. :-)
-- Marlenio (MLTorNode)
FE4033D750831C32A957174ADD11E40F558A14A9 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Are the ips still valid? https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14... Is the port forward working? IPv4 Starting Nmap 7.60 ( https://nmap.org ) at 2018-01-25 20:20 Romance Standard Time Nmap scan report for host28-237-dynamic.239-95-r.retail.telecomitalia.it (95.239.237.28) Host is up. PORT STATE SERVICE 433/tcp filtered nnsp Nmap done: 1 IP address (1 host up) scanned in 3.50 seconds IPv6 Starting Nmap 7.60 ( https://nmap.org ) at 2018-01-25 20:23 Romance Standard Time Nmap scan report for 2001:470:1f12:62c::2:51 Host is up. PORT STATE SERVICE 433/tcp filtered nnsp Nmap done: 1 IP address (1 host up) scanned in 3.22 seconds On Thu, 25 Jan 2018 at 17:43 niftybunny <abuse@to-surf-and-protect.net> wrote:
On 25. Jan 2018, at 15:12, MLTor Node <ml.tor.node@gmail.com> wrote:
Hi to all! i have a little relay running in my home LAN on Windows 2016 server (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i create two VLan on my home network, one dedicated for my Tor relay. Today i updated service to 3.2.9 release.
After starting tor service, log say that Orport and DIRport are reachable from outside, so it seems to be working without problems. But if i query Atlas, my node seems to be down from 5 days. The IP showed in Atlas is old (i have dynamic IP and dynamic DNS). I stop and start several times service with no luck.
Anyone can help me? My node is small, but i like very much Tor and i want to continue contributing to the project. :-)
-- Marlenio (MLTorNode)
FE4033D750831C32A957174ADD11E40F558A14A9 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I've noticed the port typo, but results are same... On Thu, 25 Jan 2018 at 20:31 r1610091651 <r1610091651@telenet.be> wrote:
Are the ips still valid?
https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14...
Is the port forward working?
IPv4 Starting Nmap 7.60 ( https://nmap.org ) at 2018-01-25 20:20 Romance Standard Time Nmap scan report for host28-237-dynamic.239-95-r.retail.telecomitalia.it (95.239.237.28) Host is up.
PORT STATE SERVICE 433/tcp filtered nnsp
Nmap done: 1 IP address (1 host up) scanned in 3.50 seconds
IPv6 Starting Nmap 7.60 ( https://nmap.org ) at 2018-01-25 20:23 Romance Standard Time Nmap scan report for 2001:470:1f12:62c::2:51 Host is up.
PORT STATE SERVICE 433/tcp filtered nnsp
Nmap done: 1 IP address (1 host up) scanned in 3.22 seconds
On Thu, 25 Jan 2018 at 17:43 niftybunny <abuse@to-surf-and-protect.net> wrote:
On 25. Jan 2018, at 15:12, MLTor Node <ml.tor.node@gmail.com> wrote:
Hi to all! i have a little relay running in my home LAN on Windows 2016 server (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i create two VLan on my home network, one dedicated for my Tor relay. Today i updated service to 3.2.9 release.
After starting tor service, log say that Orport and DIRport are reachable from outside, so it seems to be working without problems. But if i query Atlas, my node seems to be down from 5 days. The IP showed in Atlas is old (i have dynamic IP and dynamic DNS). I stop and start several times service with no luck.
Anyone can help me? My node is small, but i like very much Tor and i want to continue contributing to the project. :-)
-- Marlenio (MLTorNode)
FE4033D750831C32A957174ADD11E40F558A14A9 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Interesting its up for you. From Germany the host still looks down # nmap -p- 95.239.237.28 Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-25 21:28 CET Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.28 seconds # nmap -p 443 95.239.237.28 Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-25 21:31 CET Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 4.38 seconds No clue why …
On 25. Jan 2018, at 20:32, r1610091651 <r1610091651@telenet.be> wrote:
I've noticed the port typo, but results are same...
On Thu, 25 Jan 2018 at 20:31 r1610091651 <r1610091651@telenet.be <mailto:r1610091651@telenet.be>> wrote: Are the ips still valid? https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14... <https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14A9>
Is the port forward working?
IPv4 Starting Nmap 7.60 ( https://nmap.org <https://nmap.org/> ) at 2018-01-25 20:20 Romance Standard Time Nmap scan report for host28-237-dynamic.239-95-r.retail.telecomitalia.it <http://host28-237-dynamic.239-95-r.retail.telecomitalia.it/> (95.239.237.28) Host is up.
PORT STATE SERVICE 433/tcp filtered nnsp
Nmap done: 1 IP address (1 host up) scanned in 3.50 seconds
IPv6 Starting Nmap 7.60 ( https://nmap.org <https://nmap.org/> ) at 2018-01-25 20:23 Romance Standard Time Nmap scan report for 2001:470:1f12:62c::2:51 Host is up.
PORT STATE SERVICE 433/tcp filtered nnsp
Nmap done: 1 IP address (1 host up) scanned in 3.22 seconds
On Thu, 25 Jan 2018 at 17:43 niftybunny <abuse@to-surf-and-protect.net <mailto:abuse@to-surf-and-protect.net>> wrote:
On 25. Jan 2018, at 15:12, MLTor Node <ml.tor.node@gmail.com <mailto:ml.tor.node@gmail.com>> wrote:
Hi to all! i have a little relay running in my home LAN on Windows 2016 server (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i create two VLan on my home network, one dedicated for my Tor relay. Today i updated service to 3.2.9 release.
After starting tor service, log say that Orport and DIRport are reachable from outside, so it seems to be working without problems. But if i query Atlas, my node seems to be down from 5 days. The IP showed in Atlas is old (i have dynamic IP and dynamic DNS). I stop and start several times service with no luck.
Anyone can help me? My node is small, but i like very much Tor and i want to continue contributing to the project. :-)
-- Marlenio (MLTorNode)
FE4033D750831C32A957174ADD11E40F558A14A9 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays> _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 26 Jan 2018, at 01:12, MLTor Node <ml.tor.node@gmail.com> wrote:
i have a little relay running in my home LAN on Windows 2016 server (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i create two VLan on my home network, one dedicated for my Tor relay. Today i updated service to 3.2.9 release.
After starting tor service, log say that Orport and DIRport are reachable from outside, so it seems to be working without problems. But if i query Atlas, my node seems to be down from 5 days. The IP showed in Atlas is old (i have dynamic IP and dynamic DNS). I stop and start several times service with no luck.
Anyone can help me? My node is small, but i like very much Tor and i want to continue contributing to the project. :-)
Only 4 of the 9 directory authorities can make a direct connection to your relay: (large page) https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.ht... The required majority is 5. And for some reason, all the reachable authorities are in North America. Does your provider have very poor transit to Northern Europe? Do they try to block Tor clients? T
On Thu, Jan 25, 2018, at 10:09 PM, teor wrote:
Only 4 of the 9 directory authorities can make a direct connection to your relay: (large page) https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.ht...
The required majority is 5.
And for some reason, all the reachable authorities are in North America. Does your provider have very poor transit to Northern Europe? Do they try to block Tor clients?
http://www.cidr-report.org/cgi-bin/as-report?as=3269&view=2.0 A traceroute from the UK dies at Seabone.
Le vendredi 26 janvier 2018 à 09:09 +1100, teor a écrit :
Only 4 of the 9 directory authorities can make a direct connection to your relay: (large page) https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.ht... #FE4033D750831C32A957174ADD11E40F558A14A9
The required majority is 5.
As a relay operator, how can I find this kind of information? Your link returns a 404 error code. -- Johan Fleury PGP Key ID : 0x5D404386805E56E6
On 26 Jan 2018, at 10:43, Johan Fleury <jfleury@arcaik.net> wrote:
Le vendredi 26 janvier 2018 à 09:09 +1100, teor a écrit : Only 4 of the 9 directory authorities can make a direct connection to your relay: (large page) https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.ht... #FE4033D750831C32A957174ADD11E40F558A14A9
Current consensus: https://consensus-health.torproject.org/consensus-health.html #FE4033D750831C32A957174ADD11E40F558A14A9
The required majority is 5.
As a relay operator, how can I find this kind of information?
The current page is available most of the time. Search for your relays' fingerprints on: https://consensus-health.torproject.org/consensus-health.html
Your link returns a 404 error code.
I opened a ticket for this issue: https://trac.torproject.org/projects/tor/ticket/25032 T
Hey ! I have the exact same problem, I operate 2 instances that had a little bit of downtime for a few weeks. I restarted them a week ago, but they haven't received any tor traffic since then. This line shows up periodically in the logs: `Heartbeat: It seems like we are not in the cached consensus.` The instances are: prospero1 BFB01CAB4C4CFDD398F3548BD071E3F6E204DF0E prospero2 EC5A3E0C3548AB19B53ABDE6B1F9D1DB498DEF29 Both behind 46.105.84.177 and 2001:470:ccfc:201::2. How can I debug this? -- Johan Fleury PGP Key ID : 0x5D404386805E56E6
On 26 Jan 2018, at 10:41, Johan Fleury <jfleury@arcaik.net> wrote:
Hey ! I have the exact same problem, I operate 2 instances that had a little bit of downtime for a few weeks. I restarted them a week ago, but they haven't received any tor traffic since then.
This line shows up periodically in the logs: `Heartbeat: It seems like we are not in the cached consensus.`
The instances are:
prospero1 BFB01CAB4C4CFDD398F3548BD071E3F6E204DF0E prospero2 EC5A3E0C3548AB19B53ABDE6B1F9D1DB498DEF29
Both behind 46.105.84.177 and 2001:470:ccfc:201::2.
How can I debug this?
4 authorities are voting running for your first relay, 5 are not. The authorities that vote running are only on IPv4. Looks like your IPv6 is unreachable. T
Thank you for the hint about IPv6, it was a firewall issue. It's fixed now. -- Johan Fleury PGP Key ID : 0x5D404386805E56E6
participants (6)
-
Geoff Down -
Johan Fleury -
MLTor Node -
niftybunny -
r1610091651 -
teor