[tor-relays] BadExit why?

[Olaf Grimm]

Thank you for the answer. I try to get a new IP from the Trabia support.

Olaf



Am 12.02.19 um 21:51 schrieb David Goulet:
> On 12 Feb (21:35:29), Olaf Grimm wrote:
>>  inet 178.175.148.15
> Thanks Olaf!
>
> That IP was flagged as rewritting bitcoin addresses on Jan 21st, 2019.
>
> It appears you re-used a malicious IP from I.C.S. Trabia-Network S.R.L.
>
> Do you have an easy way to request a new IP for that Exit node or it is kind
> of a pain?
>
> Un-blacklisting a relay that is still not considered expired from our reject
> rule set can be a laborious process because essentially, we have to make a
> case to the directory authorities and they decide if they remove the rule or
> not based on our arguments ;).
>
> So changing the IP would be definitely the easiest way else we can try to
> convince the dirauth :).
>
> Sorry for the inconvenience!
> David
>
>> Am 12.02.19 um 21:34 schrieb David Goulet:
>>> On 12 Feb (21:30:10), Olaf Grimm wrote:
>>>> Hello !
>>>>
>>>> I provisioning a new exit since two hours. It is a totally new relay in
>>>> a VM. My other relays at the same provider are ok. Why I see "BadExit"
>>>> in Nyx??? Now my first bad experience with my 11 relays...
>>>>
>>>> fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD
>>>> Nickname Hydra10
>>> This relay is not yet on Relay Search:
>>>
>>> http://rougmnvswfsmd4dq.onion/rs.html#search/CCDC4A28392C7448A34E98DF872213BC16DB27CD
>>>
>>> I'm guessing it is quite new.
>>>
>>> That fingerprint is *not* set as a BadExit so this means you might have gotten
>>> the IP address of an old BadExit.
>>>
>>> Can you share the address so I can look it up?
>>>
>>> Thanks!
>>> David
>>>
>>>> At all exits I have the same firewall rules and torrc configs:
>>>>
>>>> ufw status
>>>> Status: active
>>>>
>>>> To                         Action      From
>>>> --                         ------      ----
>>>> 22/tcp                     ALLOW       Anywhere                 
>>>> 9001/tcp                   ALLOW       Anywhere                 
>>>> 9030/tcp                   ALLOW       Anywhere                 
>>>> 80/tcp                     ALLOW       Anywhere                 
>>>> 443/tcp                    ALLOW       Anywhere                 
>>>> 1194/tcp                   ALLOW       Anywhere                 
>>>> 53/tcp                     ALLOW       Anywhere                 
>>>> 53/udp                     ALLOW       Anywhere                 
>>>> 1194/udp                   ALLOW       Anywhere                 
>>>> 22/tcp (v6)                ALLOW       Anywhere (v6)            
>>>> 9001/tcp (v6)              ALLOW       Anywhere (v6)            
>>>> 9030/tcp (v6)              ALLOW       Anywhere (v6)            
>>>> 80/tcp (v6)                ALLOW       Anywhere (v6)            
>>>> 443/tcp (v6)               ALLOW       Anywhere (v6)            
>>>> 1194/tcp (v6)              ALLOW       Anywhere (v6)            
>>>> 53/tcp (v6)                ALLOW       Anywhere (v6)            
>>>> 53/udp (v6)                ALLOW       Anywhere (v6)            
>>>> 1194/udp (v6)              ALLOW       Anywhere (v6)
>>>>
>>>> Please take a look what happens.
>>>>
>>>> Olaf
>>>> _______________________________________________
>>>> tor-relays mailing list
>>>> tor-relays at lists.torproject.org
>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>> _______________________________________________
>>> tor-relays mailing list
>>> tor-relays at lists.torproject.org
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20190212/bcd9feec/attachment-0001.sig>