[tor-relays] new exit node

support at ruggedinbox.com support at ruggedinbox.com
Sat Sep 26 06:53:39 UTC 2015


Ok some traffic is starting to get thru, even if we understand that the
whole process will take more than 2 months.

The relay is now flagged as 'exit', to celebrate we upgraded Tor to
version 0.2.6.10-1 (using the torproject deb repository)
and increased the RelayBandwidth to 2048 / 2560, hoping it will also get
the 'fast' flag.

Thanks all for your help and great suggestions,
RIB team


Josef 'veloc1ty' Stautner:
> I run mine without any kind of that.
> When I receive an abuse I block the target IP for some time via
> ExitPolicy reject so my provider and the target stay happy.
> 
> I collected for some time HTTP POST requests and tried to block comment
> bots but quit stuff like that.
> 
> Am 25.09.2015 um 13:58 schrieb support at ruggedinbox.com:
>> Hello Josef, added fingerprint to MyFamily, thank you.
>>
>> Talking about ports and abuses .. it is advised to filter the outgoing
>> traffic with, say, snort-inline (ips) and in general try to mitigate
>> simple brute force attacks and spiders ?
>>
>> Or is against the idea of the proxy being just a carrier ?
>>
>> TY
>>
>> Josef 'veloc1ty' Stautner:
>>> Hello,
>>>
>>> add some family information and it should be fine.
>>> Are you sure you want to open port 22?
>>>
>>> ~Josef
>>>
>>> Am 25.09.2015 um 12:00 schrieb support at ruggedinbox.com:
>>>> Hi we are running from few hours a new Tor exit node: 87.120.37.163
>>>> aka tor-exit-node-01.cryptonoid.com
>>>> aka cryptonoid.com
>>>>
>>>> We couldn't register the IP with ARIN but of course the data center
>>>> knows what we are doing and is willing to take the risk,
>>>> we hope to be able to handle the abuses notices
>>>> and are here to learn :)
>>>>
>>>> The current configuration is:
>>>>
>>>> ORPort 9001
>>>> Address tor-exit-node-01.cryptonoid.com
>>>> Nickname cryptonoid01
>>>> RelayBandwidthRate 768 KB
>>>> RelayBandwidthBurst 1024 KB
>>>> ContactInfo RuggedInbox team <support at ruggedinbox.com>
>>>> DirPort 9030
>>>> DirPortFrontPage /etc/tor/tor-exit-notice.html
>>>>
>>>> ExitPolicy accept *:22
>>>> ExitPolicy accept *:80
>>>> ExitPolicy accept *:443
>>>> ExitPolicy accept *:465
>>>> ExitPolicy accept *:993
>>>> ExitPolicy accept *:995
>>>> ExitPolicy reject *:*
>>>>
>>>>
>>>> Does it looks good to you ?
>>>>
>>>> Currently both https://torstatus.blutmagie.de and
>>>> https://atlas.torproject.org/#search/87.120.37.163
>>>> show the server as 'relay', not as exit.
>>>> Is that normal ?
>>>>
>>>>
>>>> Thank you,
>>>> RuggedInbox team
>>>> _______________________________________________
>>>> 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
>>>
>> _______________________________________________
>> 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
> 


More information about the tor-relays mailing list