Regarding web-servers hosting Tor relays, it is much more likely for them to
sit behind a CDN such as Cloudflare for DoS protection and delivery
optimization.
Other services of course, however..
--- Original Message ---
xmrk2 via tor-relays schrieb am Sonntag, 11.
Juni 2023 um 1:46 nac
Yes, I agree 100% with Danny's summary here, so I have to concede, I did not
found enough evidence that Comcast blocks connections *to* tor relays. I
apologize. Specifically, I did some tests with ronqtorrelays at risley.net ,
who is a Comcast Business customer, and he had no problem initiating
Hi xmrk2,
As a fellow relay operator I think it might be helpful for me to add some
clarification to what you saw.
1. "comcast" the ISP didn't block or interfere with traffic to/from the
relay IP. (Thanks Jason for the clarification.)
However,
2. an average "comcast user" (with ISP-provided modem
>As to the blog post you mention… Your statements are very generic: now you
>talk about "not blocking tor", but tor is not just one webpage, one server, a
>monolithic entity. I would appreciate details: If your customer has "advanced
>security" activated, can he connect to any ORPort of any tor
Hello,
It is a good sign that Comcast cares and wants to defend itself. Another
positive is that you did not try things like "tor is only for
criminals/terrorists".
As to the blog post you mention. (Note that to see the post one may need to
delete the trailing full stop from the url, the corre
I have only experienced similar problems while running tor exit node, even with
very restricted exit policy. Allowing exit only to port X, and unable to
initiate connections to port Y (typically Y=HTTPS=443, of course X =/= Y).
Note that those problems are not Comcast's fault, although they do p
Hi – Dropping into this thread from Comcast to say that we DO NOT BLOCK Tor.
Feel free to refer back to my 2014 blog statement on this at
https://corporate.comcast.com/comcast-voices/setting-the-record-straight-on-tor.
Jason Livingood
Technology Policy, Product & Standards
Comcast
__
I have the same problem here in germany with also two sites. I'm running
an non-exit relay.
So far I can not access the sites "banking.ing-diba.de" and
"www.elster.de" when the tor server is running after some time.
The only thing which helps when I renew my public ip address. Then the
access
I was running a Tor Relay for a while from a Comcast residential, non-business
account up until a couple of months ago with no issues from Comcast.
I did, however start experiencing issues accessing other commercial websites
from the same Internet address. When I accessed those sites from a diff
Starting from the most interesting info - another Comcast customer contacted
me, lets call him CCB, and the first Comcast customer I mentioned previously
will be CCA. CCB claims he had to disable some settings - probably "Advanced
Security" - in his Comcast router, because before doing so, nobod
Okay, you planted some doubt. This is a quote what my peer wrote me about the
issue, I hope it is ok to quote, contains no personal or sensitive info,
emphasis added:
> Comcast/Xfinity! has a bumpy past with tor. They periodically block it, get
> yelled out by their subscribers and the media, t
> On Jun 11, 2023, at 04:46, xmrk2 via tor-relays
> wrote:
>
> I believe Comcast blocks all traffic between its customers and public tor
> relay nodes
I'm a reluctant Comcast Business user. Here's my experience (briefly, as I'm
typing with a newly-fractured wrist):
Though during install I
On Sonntag, 11. Juni 2023 13:46:06 CEST xmrk2 via tor-relays wrote:
> Background: I am running a lightning node, lightning is a layer 2 protocol
> to scale Bitcoin. Lightning nodes need to be connected to each other
> ideally 24/7. I was contacted by the operator of another Lightning node,
> compl
> This sucks big time, if true. I am trying to ping Comcast from a middle
> relay IP address and it seams, to work, I guess you mean AS33651 -
> Comcast Cable LLC.
The peer's IP address is in ASN 7922, according to whatismyipaddress.com . Note
that my test was always opening a TCP4 connection t
FWIW I haven't ever experienced any issues using Tor on multiple Comcast
residential and business lines.
I use Tor as a client daily from a Comcast residential connection and
have never been unable to connect to directories or relays.
I also have a directory client running 24/7 on Comcast bus
If we could get EFF to announce a boycott of any corporation known to
act maliciously against Tor or other privacy-friendly technology (such
as VPNs), that would go a long way.
I will also write to EFF. I have donated money to them, so maybe they
will listen. If they won't support a boycott
xmrk2 via tor-relays wrote:
Any ideas on how to combat this? I was thinking about including some
false positives in tor relay list. Imagine including some Google
servers' IP addresses - Comcast customers suddenly cannot connect to
Google, unless Comcast stops this blocking... or simply whitelis
I'd like to raise awareness of the Comcast blocking.
As stated in subject, I believe Comcast blocks all traffic between its
customers and public tor relay nodes. That is, the blocking is not limited to
tor-related traffic, all other services / ports on the tor relay are blocked.
Background: I a
18 matches
Mail list logo
