On Mon, Jun 6, 2011 at 12:30, Abdul Halim <sagikliwon@xxxxxxxxx> wrote: > On Mon, Jun 6, 2011 at 2:23 PM, Oon-Ee Ng <ngoonee.talk@xxxxxxxxx> 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
