[arch-general] IPv6 causing wget/curl to hang for a long time?
I use the following line to get my current external IP in conky. Recently Its been hanging for ages before responding, so I tried it out and it seems to try an ipv6 address first before timing out and succeeding on the ipv4 address. I know I can just disable ipv6, but since on June 8th (AFAICR) there's gonna be a large scale test of that on the interwebz, probably a good thing to keep around. Any suggestions what the problem could be? Is it simply a faulty DNS server (I'm using my local ISP's DNS)? wget -O -i icanhazip.com --2011-06-05 18:28:04-- http://icanhazip.com/ Resolving icanhazip.com... 2001:470:1f10:d57:feed:beef:cafe:d00d, 50.56.84.181 Connecting to icanhazip.com|2001:470:1f10:d57:feed:beef:cafe:d00d|:80... failed: Connection timed out. Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 16 [text/plain] Saving to: “-i” 100%[====================================================================================================================>] 16 --.-K/s in 0s
On Sun, Jun 5, 2011 at 16:06, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
I use the following line to get my current external IP in conky. Recently Its been hanging for ages before responding, so I tried it out and it seems to try an ipv6 address first before timing out and succeeding on the ipv4 address. I know I can just disable ipv6, but since on June 8th (AFAICR) there's gonna be a large scale test of that on the interwebz, probably a good thing to keep around. Any suggestions what the problem could be? Is it simply a faulty DNS server (I'm using my local ISP's DNS)?
wget -O -i icanhazip.com --2011-06-05 18:28:04-- http://icanhazip.com/ Resolving icanhazip.com... 2001:470:1f10:d57:feed:beef:cafe:d00d, 50.56.84.181 Connecting to icanhazip.com|2001:470:1f10:d57:feed:beef:cafe:d00d|:80... failed: Connection timed out. Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 16 [text/plain] Saving to: “-i”
100%[====================================================================================================================>] 16 --.-K/s in 0s
I had the same problem and i disabled ipv6. If the ipv6 module is not loaded and no ipv6 dns are defined (see http://www.chaz6.com/files/resolv.conf for a list of public ipv6 dns addresses), then you won't get this problem. The June 8th IPv6 test is for the same reason, browsers trying ipv6 address (till time-out) before fall-back to IPv4 address (if ipv6 module is loaded). Or you can use a IPv6 tunnel broker like freenet6 or Hurricane Electric and enable ipv6 module and ipv6 dns. Regards. Keshav
wget -O -i icanhazip.com --2011-06-05 18:28:04-- http://icanhazip.com/ Resolving icanhazip.com... 2001:470:1f10:d57:feed:beef:cafe:d00d, 50.56.84.181 Connecting to icanhazip.com|2001:470:1f10:d57:feed:beef:cafe:d00d|:80... failed: Connection timed out. Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 16 [text/plain] Saving to: “-i”
btw the -O flag expects a filename, I guess you have some file called "-i" lying around somewhere... :)
On Sun, Jun 5, 2011 at 7:27 PM, Martti Kühne <mysatyre@gmail.com> wrote:
wget -O -i icanhazip.com --2011-06-05 18:28:04-- http://icanhazip.com/ Resolving icanhazip.com... 2001:470:1f10:d57:feed:beef:cafe:d00d, 50.56.84.181 Connecting to icanhazip.com|2001:470:1f10:d57:feed:beef:cafe:d00d|:80... failed: Connection timed out. Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 16 [text/plain] Saving to: “-i”
btw the -O flag expects a filename, I guess you have some file called "-i" lying around somewhere... :)
Yes, I already deleted it =). No file editor wants to look at it, funnily enough =p So if I disable ipv6 will I lose connectivity on june 8th? Don't really know too much about what's being changed exactly, just that its being tested for 24 hours.
On june 8th some major internet sites will turn ipv6 support on for 24h, ipv4 will not be disabled. -- (\_ /) copy the bunny to your profile (0.o ) to help him achieve world domination. (> <) come join the dark side. /_|_\ (we have cookies.)
On Sun, Jun 05, 2011 at 10:20:36PM +0800, Oon-Ee Ng wrote:
So if I disable ipv6 will I lose connectivity on june 8th? Don't really know too much about what's being changed exactly, just that its being tested for 24 hours.
No. Most of the sites should remain dual-stacked. However, why disable IPv6 outright? Find and fix the root of the problem, instead of doing silly workarounds.
On Sun, Jun 05, 2011 at 10:20:36PM +0800, Oon-Ee Ng wrote:
So if I disable ipv6 will I lose connectivity on june 8th? Don't really know too much about what's being changed exactly, just that its being tested for 24 hours.
No issue here. I am using hurricane electric tunnelling. Are you using any other other tunnelling? What is the result of ping6 or traceroute6 icanhazip.com? My DNS server by default is google.
On Sun, Jun 5, 2011 at 12:36 PM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
I use the following line to get my current external IP in conky. Recently Its been hanging for ages before responding, so I tried it out and it seems to try an ipv6 address first before timing out and succeeding on the ipv4 address. I know I can just disable ipv6, but since on June 8th (AFAICR) there's gonna be a large scale test of that on the interwebz, probably a good thing to keep around. Any suggestions what the problem could be? Is it simply a faulty DNS server (I'm using my local ISP's DNS)?
wget -O -i icanhazip.com --2011-06-05 18:28:04-- http://icanhazip.com/ Resolving icanhazip.com... 2001:470:1f10:d57:feed:beef:cafe:d00d, 50.56.84.181 Connecting to icanhazip.com|2001:470:1f10:d57:feed:beef:cafe:d00d|:80... failed: Connection timed out. Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 16 [text/plain] Saving to: “-i”
100%[====================================================================================================================>] 16 --.-K/s in 0s
For it to even try connecting to IPv6 addresses, your computer would have to have routes set up for them. Now, the question is where do these routes come from? If they're added by autoconfiguration, there's something in your network advertising itself as a IPv6 router, but it's not actually functional. That's where the problem lies, then.
On Mon, Jun 6, 2011 at 1:37 PM, Jan Steffens <jan.steffens@gmail.com> wrote:
On Sun, Jun 5, 2011 at 12:36 PM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
I use the following line to get my current external IP in conky. Recently Its been hanging for ages before responding, so I tried it out and it seems to try an ipv6 address first before timing out and succeeding on the ipv4 address. I know I can just disable ipv6, but since on June 8th (AFAICR) there's gonna be a large scale test of that on the interwebz, probably a good thing to keep around. Any suggestions what the problem could be? Is it simply a faulty DNS server (I'm using my local ISP's DNS)?
wget -O -i icanhazip.com --2011-06-05 18:28:04-- http://icanhazip.com/ Resolving icanhazip.com... 2001:470:1f10:d57:feed:beef:cafe:d00d, 50.56.84.181 Connecting to icanhazip.com|2001:470:1f10:d57:feed:beef:cafe:d00d|:80... failed: Connection timed out. Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 16 [text/plain] Saving to: “-i”
100%[====================================================================================================================>] 16 --.-K/s in 0s
For it to even try connecting to IPv6 addresses, your computer would have to have routes set up for them. Now, the question is where do these routes come from?
If they're added by autoconfiguration, there's something in your network advertising itself as a IPv6 router, but it's not actually functional. That's where the problem lies, then.
That seems consistent with what I'm experiencing, this does not happen in my university. I get the following:- ngoonee@ngoonee-laptop ~ % wget -O - icanhazip.com --2011-06-06 14:21:38-- http://icanhazip.com/ Resolving icanhazip.com... 50.56.84.181, 2001:470:1f10:d57:feed:beef:cafe:d00d Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 14 [text/plain] Saving to: “STDOUT” 0% [ ] 0 --.-K/s 59.191.194.87 100%[====================================================================================================================>] 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....
On Mon, Jun 6, 2011 at 2:23 PM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
That seems consistent with what I'm experiencing, this does not happen in my university. I get the following:-
ngoonee@ngoonee-laptop ~ % wget -O - icanhazip.com --2011-06-06 14:21:38-- http://icanhazip.com/ Resolving icanhazip.com... 50.56.84.181, 2001:470:1f10:d57:feed:beef:cafe:d00d Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 14 [text/plain] Saving to: “STDOUT”
0% [ ] 0 --.-K/s 59.191.194.87
100%[====================================================================================================================>] 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 8.8.8.8. can you ping6 ipv6.google.com?
On Mon, Jun 6, 2011 at 12:30, Abdul Halim <sagikliwon@gmail.com> wrote:
On Mon, Jun 6, 2011 at 2:23 PM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
That seems consistent with what I'm experiencing, this does not happen in my university. I get the following:-
ngoonee@ngoonee-laptop ~ % wget -O - icanhazip.com --2011-06-06 14:21:38-- http://icanhazip.com/ Resolving icanhazip.com... 50.56.84.181, 2001:470:1f10:d57:feed:beef:cafe:d00d Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 14 [text/plain] Saving to: “STDOUT”
0% [ ] 0 --.-K/s 59.191.194.87
100%[====================================================================================================================>] 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 8.8.8.8. can you ping6 ipv6.google.com?
For now use wget --inet4-only # or curl --ipv4 to ensure both use only ipv4 addresses. Regards. Keshav
On 06/06/2011 10:54, KESHAV P.R. wrote:
For now use
wget --inet4-only # or curl --ipv4
to ensure both use only ipv4 addresses.
Or shorter: wget -4 curl -4 -- slubman
participants (8)
-
Abdul Halim
-
Harry Strongburg
-
Jan Steffens
-
jesse jaara
-
KESHAV P.R.
-
Martti Kühne
-
Oon-Ee Ng
-
slubman