Yes. wget worked.
ok, so.. was it NOT wget that you used previously? (oh, yum...) what does
yum use in the background and can you test yum as well?
[rramamoo@rramamoo ~]$ wget
http://fedora.secsup.org/linux/releases/10/Everything/x86_64/os/Packages/...
--2009-05-08 10:31:43--
http://fedora.secsup.org/linux/releases/10/Everything/x86_64/os/Packages/...
Resolving fedora.secsup.org... 208.209.50.21, 2600:803:420:2:b00b:b00b:1234:1112,
2600:803:420:2:b00b:b00b:1234:1114, ...
Connecting to fedora.secsup.org|208.209.50.21|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 321670 (314K) [text/plain]
Saving to: `gstreamer-python-0.10.12-1.fc10.x86_64.rpm'
100%[=============================================================================================================>]
321,670 1.62M/s in 0.2s
2009-05-08 10:31:44 (1.62 MB/s) - `gstreamer-python-0.10.12-1.fc10.x86_64.rpm' saved
[321670/321670]
----- Original Message -----
From: "Chris Morrow" <morrowc(a)ops-netman.net>
To: "Raj Ramamoorthy" <rramamoo(a)redhat.com>
Cc: mirror-admin(a)fedoraproject.org, "Matt Domsch" <Matt_Domsch(a)Dell.com>
Sent: Friday, May 8, 2009 10:29:40 AM GMT -06:00 US/Canada Central
Subject: Re:
secsup.org Fedora mirror problem report
On Fri, 8 May 2009, Raj Ramamoorthy wrote:
> [root@rramamoo rramamoo]# tcptraceroute
fedora.secsup.org
> Selected device eth0, address 10.17.14.64, port 42624 for outgoing packets
> Tracing the path to
fedora.secsup.org (208.209.50.21) on TCP port 80 (http), 30 hops
max
> 1 10.17.14.254 0.704 ms 0.287 ms 0.652 ms
> 2
500.Serial3-9.GW3.ATL1.ALTER.NET (157.130.68.181) 1.237 ms 1.215 ms 1.052 ms
> 3
187.at-1-2-0.XR1.ATL1.ALTER.NET (152.63.83.110) 1.338 ms 1.446 ms 1.296 ms
> 4
0.so-1-0-0.XL1.ATL1.ALTER.NET (152.63.86.85) 1.315 ms 1.443 ms 1.454 ms
> 5
0.so-7-0-0.CL1.IAD5.ALTER.NET (152.63.34.142) 62.352 ms 20.014 ms 20.224 ms
> 6
500.ATM4-0.GW5.IAD5.ALTER.NET (152.63.43.137) 20.511 ms 22.391 ms 19.830 ms
> 7
xa-gw2.customer.alter.net (157.130.13.70) 20.590 ms 30.110 ms 20.724 ms
> 8 * * *
> 9 208.209.50.21 [open] 20.334 ms 20.514 ms 22.031 ms
great, does wget work for you? I can test from a bunch of other places,
but I suspect it's going to work for me from everywhere I look...
pls try your download again.
-Chris
>
>
>
>
> ----- Original Message -----
> From: "Chris Morrow" <morrowc(a)ops-netman.net>
> To: "Matt Domsch" <Matt_Domsch(a)Dell.com>
> Cc: rramamoo(a)redhat.com, mirror-admin(a)fedoraproject.org
> Sent: Friday, May 8, 2009 9:47:35 AM GMT -06:00 US/Canada Central
> Subject: RE:
secsup.org Fedora mirror problem report
>
>
>
> On Fri, 8 May 2009, Matt_Domsch(a)Dell.com wrote:
>
>> [rramamoo@rramamoo ~]$ traceroute
fedora.secsup.org
>> traceroute to
fedora.secsup.org (208.209.50.21), 30 hops max, 60 byte packets
>> 1 unused (10.17.14.254) 1.987 ms 2.170 ms 2.127 ms
>> 2
500.Serial3-9.GW3.ATL1.ALTER.NET (157.130.68.181) 2.386 ms 2.331 ms 2.279
ms
>> 3
187.at-1-2-0.XR1.ATL1.ALTER.NET (152.63.83.110) 2.204 ms 2.437 ms 2.392 ms
>> 4
0.so-1-0-0.XL1.ATL1.ALTER.NET (152.63.86.85) 2.345 ms 2.539 ms 2.801 ms
>> 5
0.so-7-0-0.CL1.IAD5.ALTER.NET (152.63.34.142) 20.222 ms 20.180 ms 20.132
ms
>> 6
500.ATM7-0.GW5.IAD5.ALTER.NET (152.63.43.145) 20.026 ms 20.045 ms 20.659
ms
>> 7
xa-gw2.customer.alter.net (157.130.13.70) 20.618 ms 20.915 ms 20.877 ms
>
> that's a firewall, traceroute/ping are rarely your friend for finding
> end-system state... tcptraceroute though might help here.
>
> on the other hand (from a non-701 connected host):
>
> [morrowc@usa1 ~]$ wget
>
http://fedora.secsup.org/linux/releases/10/Everything/x86_64/os/Packages/...
> --2009-05-08 14:46:38--
>
http://fedora.secsup.org/linux/releases/10/Everything/x86_64/os/Packages/...
> Resolving fedora.secsup.org... 208.209.50.21,
> 2600:803:420:2:b00b:b00b:1234:1114, 2600:803:420:2:b00b:b00b:1234:1111,
> ...
> Connecting to fedora.secsup.org|208.209.50.21|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 321670 (314K) [text/plain]
> Saving to: `gstreamer-python-0.10.12-1.fc10.x86_64.rpm'
>
> 100%[======================================>] 321,670 367K/s in
> 0.9s
>
> 2009-05-08 14:46:40 (367 KB/s) -
> `gstreamer-python-0.10.12-1.fc10.x86_64.rpm' saved [321670/321670]
>
>
> so... 'works for me!' ??
>
>> 8 * * *
>> 9 * * *
>> 10 * * *
>> 11 * * *
>> 12 * * *
>> 13 * * *
>> 14 * * *
>>
>> --
>> Matt Domsch
>> Linux Technology Strategist, Dell Office of the CTO
>>
linux.dell.com &
www.dell.com/linux
>>
>>
>>
>>
>> -----Original Message-----
>> From: Raj Ramamoorthy [mailto:rramamoo@redhat.com]
>> Sent: Fri 5/8/2009 8:10 AM
>> To: Chris Morrow
>> Cc: mirror-admin(a)fedoraproject.org; Domsch, Matt
>> Subject: Re:
secsup.org Fedora mirror problem report
>>
>> It failed from my hotel as well (outside Red Hat network).
>>
>> ----- Original Message -----
>> From: "Raj Ramamoorthy" <rramamoo(a)redhat.com>
>> To: "Chris Morrow" <morrowc(a)ops-netman.net>
>> Cc: mirror-admin(a)fedoraproject.org, "Matt Domsch"
<Matt_Domsch(a)Dell.com>
>> Sent: Friday, May 8, 2009 8:09:08 AM GMT -06:00 US/Canada Central
>> Subject: Re:
secsup.org Fedora mirror problem report
>>
>> eth0 Link encap:Ethernet HWaddr 00:24:7E:13:4A:68
>> inet addr:10.17.14.64 Bcast:10.17.14.255 Mask:255.255.255.0
>> inet6 addr: fe80::224:7eff:fe13:4a68/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:1112 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:1081 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:100
>> RX bytes:663504 (647.9 KiB) TX bytes:177423 (173.2 KiB)
>> Memory:fc000000-fc020000
>>
>>
>>
>> ----- Original Message -----
>> From: "Chris Morrow" <morrowc(a)ops-netman.net>
>> To: "Matt Domsch" <Matt_Domsch(a)Dell.com>
>> Cc: rramamoo(a)redhat.com, mirror-admin(a)fedoraproject.org
>> Sent: Friday, May 8, 2009 12:22:10 AM GMT -06:00 US/Canada Central
>> Subject: Re:
secsup.org Fedora mirror problem report
>>
>> which ip address I wonder is the user using? v4/v6? which?
>>
>> On Thu, 7 May 2009, Matt_Domsch(a)Dell.com wrote:
>>
>>> morrowc, any chance this is a known problem? The download succeeds for me at
home on Time Warner, but apparently is failing for this user who works at Red Hat.
>>>
>>>
>>>
https://bugzilla.redhat.com/show_bug.cgi?id=499653
>>>
>>> Description From Rajagopal Ramamoorthy (rramamoo(a)redhat.com) 2009-05-07
10:59:53 EDT (-) [reply]
>>>
>>> Description of problem:
>>>
>>> Downloading Packages:
>>>
http://fedora.secsup.org/linux/releases/10/Everything/x86_64/os/Packages/...:
>>> [Errno 4] IOError: <urlopen error (101, 'Network is
unreachable')>
>>>
>>>
>>> Version-Release number of selected component (if applicable):
>>> Fedora 10 x86_64
>>>
>>> How reproducible:
>>> Everytime since last few days
>>>
>>> Steps to Reproduce:
>>> 1. Just type yum update in 64bit Fedora 10.
>>> 2.
>>> 3.
>>>
>>> Actual results:
>>> yum uses mirror site to update for all packages
>>>
>>> Expected results:
>>> yum should have got to the first site it has in the list if its available.
We
>>> do not expect it to be down for too long.
>>>
>>> Additional info:
>>> My email id rramamoo(a)redhat.com and I am running Fedora 10 x86_64 on Lenovo
>>> laptop ThinkPad T500. I get this error from all networks I have used so far.
>>>
>>>
>>>
>>> --
>>> Matt Domsch
>>> Linux Technology Strategist, Dell Office of the CTO
>>>
linux.dell.com &
www.dell.com/linux
>>>
>>>
>>>
>>>
>>
>