[arch-general] IPv6 causing wget/curl to hang for a long time?
skodabenz at gmail.com
Mon Jun 6 04:54:19 EDT 2011
On Mon, Jun 6, 2011 at 12:30, Abdul Halim <sagikliwon at gmail.com> wrote:
> On Mon, Jun 6, 2011 at 2:23 PM, Oon-Ee Ng <ngoonee.talk at gmail.com> wrote:
>> That seems consistent with what I'm experiencing, this does not happen
>> in my university. I get the following:-
>> ngoonee at ngoonee-laptop ~ % wget -O - icanhazip.com
>> --2011-06-06 14:21:38-- http://icanhazip.com/
>> Resolving icanhazip.com... 220.127.116.11,
>> Connecting to icanhazip.com|18.104.22.168|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 14 [text/plain]
>> Saving to: “STDOUT”
>> 0% [
>> ] 0
>> --.-K/s 22.214.171.124
>> 14 --.-K/s in 0s
>> 2011-06-06 14:21:39 (650 KB/s) - written to stdout [14/14]
>> So it looks like a problem with my ISP at home. Not surprising. Wonder
>> whether its worth even letting them know. Could it perhaps be
>> something set wrongly in my router? ping6 just hangs....
> Try change to gGogle dns server namely 126.96.36.199. can you ping6
For now use
wget --inet4-only # or
to ensure both use only ipv4 addresses.
More information about the arch-general