Page 2 of 2
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Fri Jan 15, 2010 6:47 pm
by username
Giorgio Maone wrote:username wrote:Giorgio Maone wrote:Could some customer of theirs (therube?) call pointing them to this thread? Thanks.
I have spoken to them (Security Department) before starting this thread, they have blocked your ip deliberately and though I asked them to review their decision, it didn't seem like that would be enough. They suggested that you (the ip/site owner) call them (888-565-4329) to resolve this. You seem to be reluctant, why?
Because my landline is currently broken and I'm in queue since 3 hours ago on my cell phone to talk with a f**g Tiscali technician.
I can ask the Comcast security tech I spoke to, to email you. Would you like that? What address should I give him?
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Fri Jan 15, 2010 7:49 pm
by Giorgio Maone
username wrote:I can ask the Comcast security tech I spoke to, to email you. Would you like that? What address should I give him?
The same listed
here, thanks.
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Fri Jan 15, 2010 10:07 pm
by Giorgio Maone
OK, after half an hour they mailed that they couldn't call back me and gave me a mail address of a technician were to write.
I did, waited one hour but received no answer.
Then I finally gave up trying to have my landline repaired (tech support at Tiscali is apparently on strike, I stayed in queue on my cell phone almost 5 hours today) and called 888-565-4329 with my cell phone (international mobile fees). After a while, a "technician" replied, and apparently knew something about this issue (they had my email address filed somewhere somehow).
As far as I could understand, he tried to explain me they cannot selectively block a port on an IP: they can just block the whole IP (which sounds brain-damaged to me, especially for such a big provider).
However I offered to close port 25 on my side, so there should be no "suspicious" traffic anymore, and he took my phone number saying they would call me back briefly to resolve this issue together.
This was more than one hour ago, I did not hear anybody back, and as far as tracepath can tell the blockage is still there.
In other words, dear NoScript/FlashGot users, Comcast doesn't give a s**t about you.
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Fri Jan 15, 2010 10:24 pm
by Giorgio Maone
This is an email I just sent to the customer care people who gave me the technician's mail address (a Yahoo one!):
To Comcast wrote:
Hi.
(Ticket xxxxxxxx, ref.
http://forums.informaction.com/viewtopic.php?p=15149 )
I've sent an email to that Yahoo (!) address you gave me 3 hours ago, and had no reply.
So I finally gave up trying to have my landline repaired (tech support at Tiscali is apparently on strike, I stayed in queue on my cell phone almost 5 hours today) and called 888-565-4329 with my cell phone (international mobile fees). After a while, a "technician" replied, and apparently knew something about this issue (he had my email address filed somewhere somehow).
As far as I could understand, he tried to explain me you cannot selectively block a port on an IP: you can just block the whole IP (which sounds brain-damaged to me, especially for such a big provider).
However I offered to close port 25 on my side, so there should be no "suspicious" traffic anymore, and he took my phone number saying they would call me back briefly to resolve this issue together.
This was more than one hour ago, I did not hear anybody back, and as far as tracepath can tell the blockage is still there.
Notice that I actually closed port 25 on 82.103.134.102 in the meanwhile, so there's absolutely no sane reason to keep that IP blocked anymore.
Could you please act immediately?
Or is really the message to the *millions* of FlashGot and NoScript users (
https://addons.mozilla.org/en-US/firefo ... r#featured ) "Comcast doesn't give a s**t about you"?
Thanks for listening
--
Giorgio Maone
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Sat Jan 16, 2010 2:42 am
by (therube)
(therube)
Still no go for me.
Spoke with Comcast (as a customer of their's that I am) a short while ago. Fellow was amiable & showed genuine interest. Hopefully the issue will be resolved shortly
.
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Sat Jan 16, 2010 12:56 pm
by Guest
So much for soon
.
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Sat Jan 16, 2010 2:18 pm
by Giorgio Maone
Based on the feedback received so far, I quite despair to have this fixed before next week.
Therefore I just changed the relevant DNS records to point *.informaction.com and (noscript|flashgot).net to a different IP. These new pointers should be propagated and effective in a few hours.
However I'm very upset for this whole story: does it really mean that if I hate someone who depends on his web services and I want to kick him in his balls, all I need to do is infecting a few Comcast customers with a slightly different strain of this trojan, just modified to connect to his IP(s)?
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Sat Jan 16, 2010 2:41 pm
by username
Giorgio Maone wrote:does it really mean that if I hate someone who depends on his web services and I want to kick him in his balls, all I need to do is infecting a few Comcast customers with a slightly different strain of this trojan, just modified to connect to his IP(s)?
If they mindlessly block any ip that a trojan connects to, which they appear to be doing, then yes, they give trojan writers the power to block arbitrary web sites and services.
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Sat Jan 16, 2010 3:15 pm
by ace
[quote="Giorgio Maone"]Based on the feedback received so far, I quite despair to have this fixed before next week.
Therefore I just changed the relevant DNS records to point *.informaction.com and (noscript|flashgot).net to a different IP. These new pointers should be propagated and effective in a few hours.
As of 10:00 AM EST 1/16/10 82.103.134.102 (noscript, informaction, flashgot.net) are now functional via Comcast ISP. Your personal website
http://maone.net/ status continues (page not loading) Yesterday I called the Comcast Security Assurance department they are friendly but won't tell you much. (They said they are working on it within 24 hours.) They are probably instructed to "dumb down" their responses. In my opinion that technique slows communication and stops progress. Anyway we are fully operational for now. Thanks Giorgio for your help! FlashGotters and NoScripters of all lands, unite!
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Sat Jan 16, 2010 3:23 pm
by Giorgio Maone
ace wrote:As of 10:00 AM EST 1/16/10 82.103.134.102 (noscript, informaction, flashgot.net) are now functional via Comcast ISP.
Nope, as far as my tracepath can see 82.103.134.102 is still blocked.
What you're probably reaching is 82.103.139.52, which is the IP I changed them to.
ace wrote: Your personal website
http://maone.net/ status continues (page not loading)
In fact, I did not modify the DNS for that domain and you're not able to reach it, indeed.
So Comcast did not do anything so far to fix this issue. QED.
Re: Comcast blocking 82.103.134.102 (noscript, informaction)
Posted: Sat Jan 16, 2010 3:35 pm
by ace
Giorgio Maone wrote:Nope, as far as my tracepath can see 82.103.134.102 is still blocked.
What you're probably reaching is 82.103.139.52, which is the IP I changed them to.
Yes you are right. Comcast did not do anything. No surprise.
Giorgio Maone wrote: Nope, as far as my tracepath can see 82.103.134.102 is still blocked.
What you're probably reaching is 82.103.139.52, which is the IP I changed them to.
In fact, I did not modify the DNS for that domain and you're not able to reach it, indeed.
So Comcast did not do anything so far to fix this issue. QED.
This is true. At first I thought it was something Comcast did to unblock, but now I see in your posts that you redirected the IP. My bad.