Closed Bug 589023 Opened 14 years ago Closed 14 years ago

cm-bbot-linux-002 can't connect to 82.94.164.168:80

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

All
Other
task
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: catlee, Assigned: arzhel)

Details

connections time out. other random ips, like 74.125.224.18:80 (google.ca) also timeout.
Assignee: server-ops → dmoore
tcpdump for working host: 12:59:39.077131 IP 63.245.210.48.37395 > 74.125.224.17.80: S 3205756890:3205756890(0) win 5840 <mss 1460> 12:59:39.079979 IP 74.125.224.17.80 > 63.245.210.48.37395: S 2044567194:2044567194(0) ack 3205756891 win 5720 <mss 1430> 12:59:39.080001 IP 63.245.210.48.37395 > 74.125.224.17.80: . ack 1 win 5840 tcpdump for broken host: 12:59:50.446263 IP 63.245.210.48.46772 > 74.125.224.18.80: S 1699587781:1699587781(0) win 5840 <mss 1460> 12:59:50.449426 IP 74.125.224.18.80 > 63.245.210.48.46772: S 483330778:483330778(0) ack 1699587782 win 5720 <mss 1430> 12:59:50.847667 IP 74.125.224.18.80 > 63.245.210.48.46772: S 483330778:483330778(0) ack 1699587782 win 5720 <mss 1430> 12:59:51.447750 IP 74.125.224.18.80 > 63.245.210.48.46772: S 483330778:483330778(0) ack 1699587782 win 5720 <mss 1430>
Component: Server Operations → Server Operations: Netops
Assignee: dmoore → ayounsi
root@cm-bbot-linux-002:~# telnet 74.125.224.18 80 Trying 74.125.224.18... Connected to 74.125.224.18 same with 82.94.164.168:80 feel free to reopen if it happens again.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.