hello i'm running a node and it's supposed to be an exit node, but i don't know why it's not getting the exit flag. Fingerprint: AFD3E441204DD828FD1EF1401742D379814D2A55 Tor version 0.3.1.9 (git-df96a13e9155c7bf). torrc: https://pastebin.com/R9qmYiX5 Any tips to fix that? --
It looks fine, it will take a few more days for exit traffic to start emerging. Check here: https://atlas.torproject.org/#details/AFD3E441204DD828FD1EF1401742D379814D2A... https://blog.torproject.org/lifecycle-new-relay On January 4, 2018 6:20:38 PM UTC, Guilherme Rigon <guilherme@rigon.info> wrote:
hello
i'm running a node and it's supposed to be an exit node, but i don't know why it's not getting the exit flag.
Fingerprint: AFD3E441204DD828FD1EF1401742D379814D2A55 Tor version 0.3.1.9 (git-df96a13e9155c7bf). torrc: https://pastebin.com/R9qmYiX5
Any tips to fix that?
--
-- Spiros Andreou
On 5 Jan 2018, at 05:20, Guilherme Rigon <guilherme@rigon.info> wrote:
hello
i'm running a node and it's supposed to be an exit node, but i don't know why it's not getting the exit flag.
Fingerprint: AFD3E441204DD828FD1EF1401742D379814D2A55 Tor version 0.3.1.9 (git-df96a13e9155c7bf). torrc: https://pastebin.com/R9qmYiX5
Your torrc looks fine. Try commenting out OutboundBindAddress, tor uses the OS default. But if it's wrong, it could be causing you connection issues.
Any tips to fix that?
Send us the notice-level logs that tor prints when it starts up, And any warnings it prints, ever. I've just checked your relay's flag votes from the directory authorities at: https://consensus-health.torproject.org/consensus-health-2018-01-04-18-00.ht... (Large page) 3 authorities don't think your relay is Running Is your relay behind a home router? Does your relay have good enough connectivity to be a relay or exit? If it's a connection limit issue, you should run a bridge instead. 5 authorities don't think your relay is Exit The Exit flag should just be calculated from your policy. So the authorities should agree on it. (Exit flag disagreements are rare, there are only 20 out of 6000 relays.) Did you set up two instances with the same keys? T
2018-01-04 19:38 GMT-02:00 teor <teor2345@gmail.com>:
On 5 Jan 2018, at 05:20, Guilherme Rigon <guilherme@rigon.info> wrote:
hello
i'm running a node and it's supposed to be an exit node, but i don't know why it's not getting the exit flag.
Fingerprint: AFD3E441204DD828FD1EF1401742D379814D2A55 Tor version 0.3.1.9 (git-df96a13e9155c7bf). torrc: https://pastebin.com/R9qmYiX5
Your torrc looks fine.
Try commenting out OutboundBindAddress, tor uses the OS default. But if it's wrong, it could be causing you connection issues.
Any tips to fix that?
Send us the notice-level logs that tor prints when it starts up, And any warnings it prints, ever.
I've just checked your relay's flag votes from the directory authorities at: https://consensus-health.torproject.org/consensus- health-2018-01-04-18-00.html#AFD3E441204DD828FD1EF1401742D379814D2A55 (Large page)
3 authorities don't think your relay is Running
Is your relay behind a home router? Does your relay have good enough connectivity to be a relay or exit? If it's a connection limit issue, you should run a bridge instead.
5 authorities don't think your relay is Exit
The Exit flag should just be calculated from your policy. So the authorities should agree on it. (Exit flag disagreements are rare, there are only 20 out of 6000 relays.)
Did you set up two instances with the same keys?
T
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello, Here's the connection status: https://pastebin.com/Rsytmgs0 With commented out OutboundBindAddress this is the log from notice.log: https://pastebin.com/0MqpcYGq About the connection, it's behind a router with NAT for Dir and OR Ports. -- ---------- Guilherme Rigon
2018-01-04 19:58 GMT-02:00 Guilherme Rigon <guilherme@rigon.info>:
2018-01-04 19:38 GMT-02:00 teor <teor2345@gmail.com>:
On 5 Jan 2018, at 05:20, Guilherme Rigon <guilherme@rigon.info> wrote:
[image: Imagem inline 1] hello
i'm running a node and it's supposed to be an exit node, but i don't know why it's not getting the exit flag.
Fingerprint: AFD3E441204DD828FD1EF1401742D379814D2A55 Tor version 0.3.1.9 (git-df96a13e9155c7bf). torrc: https://pastebin.com/R9qmYiX5
Your torrc looks fine.
Try commenting out OutboundBindAddress, tor uses the OS default. But if it's wrong, it could be causing you connection issues.
Any tips to fix that?
Send us the notice-level logs that tor prints when it starts up, And any warnings it prints, ever.
I've just checked your relay's flag votes from the directory authorities at: https://consensus-health.torproject.org/consensus-health- 2018-01-04-18-00.html#AFD3E441204DD828FD1EF1401742D379814D2A55 (Large page)
3 authorities don't think your relay is Running
Is your relay behind a home router? Does your relay have good enough connectivity to be a relay or exit? If it's a connection limit issue, you should run a bridge instead.
5 authorities don't think your relay is Exit
The Exit flag should just be calculated from your policy. So the authorities should agree on it. (Exit flag disagreements are rare, there are only 20 out of 6000 relays.)
Did you set up two instances with the same keys?
T
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello,
Here's the connection status: https://pastebin.com/Rsytmgs0
With commented out OutboundBindAddress this is the log from notice.log: https://pastebin.com/0MqpcYGq
About the connection, it's behind a router with NAT for Dir and OR Ports.
-- ---------- Guilherme Rigon
Updated notice.log: https://pastebin.com/jwfcMbk5 There are connections failed now -- ---------- Guilherme Rigon
On 5 Jan 2018, at 08:58, Guilherme Rigon <guilherme@rigon.info> wrote:
Here's the connection status: https://pastebin.com/Rsytmgs0
We don't publicly post connection IP addresses, because some of them may be client addresses. (This list is probably ok, it is probably just your relay's Guards.)
With commented out OutboundBindAddress this is the log from notice.log
Some connections failures are normal, the Tor network is under extra load right now. Please wait until your relay gets to 100%, and then wait 20 minutes for it to checking its ORPort and DirPort reachability, then send the logs.
About the connection, it's behind a router with NAT for Dir and OR Ports.
This might not work as a relay or exit, because some routers don't support 6000 simultaneous connections, which is what relays need. Exits need more. T
participants (3)
-
Guilherme Rigon -
Spiros Andreou -
teor