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