Request #6507
From:
marcmagus
Account Type:
Unknown
Support category:
Time posted:
Thu, 10 Jun 2010 15:38:49 GMT (795 weeks ago)
Status:
closed (10 points to ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
chemicallace)
chemicallace)
Summary:
Can't connect to *.dreamwidth.org on port 80 from home network
Original Request:
I can't make any connection to http://www.dreamwidth.org/ -- attempt to load in the browser hangs.
Am able to connect to https://www.dreamwidth.org/ but the page is incomplete because content from http://www.dreamwidth.org/ won't load.
My ISP is AT&T UVerse. They tell me it's nothing on their end, that either you're blocking the traffic or that something is misconfigured on my end. At this point I'm quite confident that the problem isn't on my end. Could I be in an IP block that dreamwidth is blocking? Current IP is 99.114.90.58
[I'm connecting through an anonymizer so I could get to this form]
Thanks,
Marc
Diagnostics: http://Anonymouse.org/ (Unix)
Am able to connect to https://www.dreamwidth.org/ but the page is incomplete because content from http://www.dreamwidth.org/ won't load.
My ISP is AT&T UVerse. They tell me it's nothing on their end, that either you're blocking the traffic or that something is misconfigured on my end. At this point I'm quite confident that the problem isn't on my end. Could I be in an IP block that dreamwidth is blocking? Current IP is 99.114.90.58
[I'm connecting through an anonymizer so I could get to this form]
Thanks,
Marc
Diagnostics: http://Anonymouse.org/ (Unix)
Hello Marc,
We're not blocking any IPs from AT&T UVerse. Would you mind doing a traceroute of your path to dreamwidth.org?
Anonymouse.org hides your OS and browser information, so I can't give you specific directions on how to do a traceroute on your OS. If you don't know how to perform one, please comment back to this request with your OS and I'll give you detailed directions.
Best,
ChemicalLace
We're not blocking any IPs from AT&T UVerse. Would you mind doing a traceroute of your path to dreamwidth.org?
Anonymouse.org hides your OS and browser information, so I can't give you specific directions on how to do a traceroute on your OS. If you don't know how to perform one, please comment back to this request with your OS and I'll give you detailed directions.
Best,
ChemicalLace
Sure, no problem.
[I'm on Gentoo Linux behind a DD-WRT router behind the UVerse supplied modem/gateway/router. I'm using Firefox as a browser. Sorry about the anonymouse hiding information]
[This computer is connected directly to the DD-WRT via ethernet, but also fails to connect when wired directly to the UVerse router. My laptop with Opera fails using a wireless connection to the DD-WRT as well.]
I observed in my earlier diagnostics that their router logs dropping ICMP responses when I send a ping/traceroute to dreamwidth.org from my side of the router. However, there are no logged dropped packets from the actual attempts to connect to dreamwidth.org:80.
Traceroute from the UVerse router using whatever their traceroute utility is:
traceroute 69.174.244.50 with 64 packetsize
1: 99-114-88-2.lightspeed.miamfl.sbcglobal.net (99.114.88.2) 25 ms
2: 99.167.140.22 26 ms
3: 99.167.141.24 26 ms
4: 99.167.141.12 23 ms
5: 70.159.201.246 22 ms
6: 12.83.4.196 25 ms
7: 12.83.4.236 23 ms
8: 74.175.192.166 28 ms
9: cr81.fldfl.ip.att.net (12.122.106.94) 42 ms
10: cr2.ormfl.ip.att.net (12.122.1.45) 42 ms
11: cr1.attga.ip.att.net (12.122.5.142) 41 ms
12: ggr4.attga.ip.att.net (12.122.141.89) 40 ms
13: 192.205.36.238 66 ms
14: te9-2.ccr02.atl01.atlas.cogentco.com (154.54.40.249) 67 ms
15: te2-1.ccr01.iah01.atlas.cogentco.com (154.54.29.2) 63 ms
16: te7-1.ccr01.sat01.atlas.cogentco.com (154.54.29.34) 69 ms
17: 38.104.164.38 66 ms
18: 216.187.124.98 67 ms
19: dreamwidth.org (69.174.244.50) 69 ms
Traceroute from my DD-WRT router shows no responses.
Traceroute from my desktop shows only the DD-WRT router.
[I'm on Gentoo Linux behind a DD-WRT router behind the UVerse supplied modem/gateway/router. I'm using Firefox as a browser. Sorry about the anonymouse hiding information]
[This computer is connected directly to the DD-WRT via ethernet, but also fails to connect when wired directly to the UVerse router. My laptop with Opera fails using a wireless connection to the DD-WRT as well.]
I observed in my earlier diagnostics that their router logs dropping ICMP responses when I send a ping/traceroute to dreamwidth.org from my side of the router. However, there are no logged dropped packets from the actual attempts to connect to dreamwidth.org:80.
Traceroute from the UVerse router using whatever their traceroute utility is:
traceroute 69.174.244.50 with 64 packetsize
1: 99-114-88-2.lightspeed.miamfl.sbcglobal.net (99.114.88.2) 25 ms
2: 99.167.140.22 26 ms
3: 99.167.141.24 26 ms
4: 99.167.141.12 23 ms
5: 70.159.201.246 22 ms
6: 12.83.4.196 25 ms
7: 12.83.4.236 23 ms
8: 74.175.192.166 28 ms
9: cr81.fldfl.ip.att.net (12.122.106.94) 42 ms
10: cr2.ormfl.ip.att.net (12.122.1.45) 42 ms
11: cr1.attga.ip.att.net (12.122.5.142) 41 ms
12: ggr4.attga.ip.att.net (12.122.141.89) 40 ms
13: 192.205.36.238 66 ms
14: te9-2.ccr02.atl01.atlas.cogentco.com (154.54.40.249) 67 ms
15: te2-1.ccr01.iah01.atlas.cogentco.com (154.54.29.2) 63 ms
16: te7-1.ccr01.sat01.atlas.cogentco.com (154.54.29.34) 69 ms
17: 38.104.164.38 66 ms
18: 216.187.124.98 67 ms
19: dreamwidth.org (69.174.244.50) 69 ms
Traceroute from my DD-WRT router shows no responses.
Traceroute from my desktop shows only the DD-WRT router.
It seems to have magically fixed itself this morning. I suspect some problem internal to the AT&T network [I certainly didn't change anything, and I leave my computer on all the time] which they quietly corrected.
Closing this now and hoping for the best.
Closing this now and hoping for the best.
Stopped working again this morning. This is mysterious and frustrating.
Have also contacted AT&T.
Have also contacted AT&T.
My IP address is still 99.114.90.58, and appears to have been that while things were working as well.
After trying some things suggested by the wonderful folk in IRC:
Connections to http://69.174.244.39/ show the exact same behavior as dreamwidth.org or 69.174.244.50.
Connection to http://69.174.244.47/ works cleanly.
Investigation with wireshark shows that when I attempt to connect to the servers which fail on port 80 a SYN packet goes out, but no ACK ever comes back. Neither router in the chain reports dropping the SYN, even with logging turned up as high as I can get it.
Using telnet to ports 80 and 443 confirms the effects described above.
I don't seem to be using a proxy.
I don't have an inordinate number of TCP connections open either in general or specifically to Dreamwidth at any point in the chain under my control (including the AT&T-provided router/modem).
I observe that there's a Known Issue regarding AT&T and email and speculate they may be related if the problem is on the AT&T end.
After trying some things suggested by the wonderful folk in IRC:
Connections to http://69.174.244.39/ show the exact same behavior as dreamwidth.org or 69.174.244.50.
Connection to http://69.174.244.47/ works cleanly.
Investigation with wireshark shows that when I attempt to connect to the servers which fail on port 80 a SYN packet goes out, but no ACK ever comes back. Neither router in the chain reports dropping the SYN, even with logging turned up as high as I can get it.
Using telnet to ports 80 and 443 confirms the effects described above.
I don't seem to be using a proxy.
I don't have an inordinate number of TCP connections open either in general or specifically to Dreamwidth at any point in the chain under my control (including the AT&T-provided router/modem).
I observe that there's a Known Issue regarding AT&T and email and speculate they may be related if the problem is on the AT&T end.
Hi Marc,
We've done some digging and I can confirm that we don't have any sysbans for your IP address. Have you had any contact back from AT&T?
Best,
Dom
We've done some digging and I can confirm that we don't have any sysbans for your IP address. Have you had any contact back from AT&T?
Best,
Dom
Some more information:
mark found the other day when this repeated that my IP is finding its way onto a temporary block list because it's somehow hammering the server with requests.
In response I've scaled back firefox's connections/server to the defaults and made certain not to refresh DW within a couple minutes on two computers.
Last night when I went to sleep (c. 2010-06-24T01:30 EDT) it was working. This morning when I awoke (c. 09:30 EDT) it wasn't working.
There are 3 computers on the LAN which were up during that time: my desktop and netbook running Gentoo were unattended and untouched the entire time. My partner's Macintosh was used for some light surfing [not DW directly, but potentially links to DW] this morning.
Note: two things have changed that I'm aware of since a month ago when I never had this problem. I've moved and thus changed ISP and IP, and I've moved away from my old housemates and in with my partner (so one new computer in my LAN)
mark found the other day when this repeated that my IP is finding its way onto a temporary block list because it's somehow hammering the server with requests.
In response I've scaled back firefox's connections/server to the defaults and made certain not to refresh DW within a couple minutes on two computers.
Last night when I went to sleep (c. 2010-06-24T01:30 EDT) it was working. This morning when I awoke (c. 09:30 EDT) it wasn't working.
There are 3 computers on the LAN which were up during that time: my desktop and netbook running Gentoo were unattended and untouched the entire time. My partner's Macintosh was used for some light surfing [not DW directly, but potentially links to DW] this morning.
Note: two things have changed that I'm aware of since a month ago when I never had this problem. I've moved and thus changed ISP and IP, and I've moved away from my old housemates and in with my partner (so one new computer in my LAN)
Hi Marc,
I noticed you posted to your journal that AT&T admitted this was an issue and came out and replaced your modem and perhaps did something else. Did this fix the issue? Were they able to provide any more information on the likely cause
If not, the next step would likely be to try and arrange for packet capture on both your end and ours. Either some machine on your network has a virus that is causing it to hammer us with requests, which sounds unlikely from all the troubleshooting you've done, or someone else periodically gets your IP address who is hammering us and putting the IP on the block list.
Best,
ChemicalLace
I noticed you posted to your journal that AT&T admitted this was an issue and came out and replaced your modem and perhaps did something else. Did this fix the issue? Were they able to provide any more information on the likely cause
If not, the next step would likely be to try and arrange for packet capture on both your end and ours. Either some machine on your network has a virus that is causing it to hammer us with requests, which sounds unlikely from all the troubleshooting you've done, or someone else periodically gets your IP address who is hammering us and putting the IP on the block list.
Best,
ChemicalLace
Go to: previous open request, next open request
Return to the list of open requests.
Back to the Support Area.