[tor-relays] Identifying a relay

Eddie stunnel at attglobal.net
Thu Jun 16 13:16:28 UTC 2022


Unfortunately that option is very specifically disallowed as it's 
considered as trying to hide the source IP.

Cheers.


On 6/16/2022 1:33 AM, Gary C. New via tor-relays wrote:
> Eddie,
>
> When experiencing similar issues, the recommended solution I received, 
> from this list, and that seems to work best is a VPN for affected traffic.
>
> With dnsmasq, iptables or reverse proxy, and a dedicated split-tunnel 
> vpn, I shunt affect traffic over the split-tunnel vpn without 
> end-users on my local network even knowing.
>
> Seems to work fairly well.
>
> Best of luck.
>
>
> Gary
>> This Message Originated by the Sun.
> iBigBlue 63W Solar Array (~12 Hour Charge)
> + 2 x Charmast 26800mAh Power Banks
> = iPhone XS Max 512GB (~2 Weeks Charged)
>
>
> On Wednesday, June 15, 2022, 11:56:37 PM PDT, Eddie 
> <stunnel at attglobal.net> wrote:
>
>
> Have a question about how a server I connect to can tell I am running a
> guard/middle relay.  All I can think of is that they check the published
> list of tor nodes against the IP.  Or (maybe, but unlikely) portscan the
> IP and probe any open ports to determine the service.  Are there any
> other methods that can be used.
>
> Background:  The corp my wife works for blocked our IP.  The excuse they
> gave was that it was due to a change made by a vendor they use to
> identify malicious IP addresses.  I have been running the relay for
> almost 5 years without any previous flagging.  They also state that
> running a middle relay is not in violation of any policy, but the vendor
> mis-identified our relay as an exit, hence blocking it.
>
> After changing the IP, the new IP was also blocked in less than 24
> hours.  My feeling is that the vendor is now just using the full list of
> tor nodes and indiscriminately blocking everything, despite what the
> corp security folks say.
>
> I'm looking for some sort of validation I can use to counter their claims.
> _______________________________________________
> 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 --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20220616/fedd73d2/attachment.htm>


More information about the tor-relays mailing list