Hurricane Electric's IPv6 Tunnel Broker Forums
June 18, 2013, 09:35:35 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to Hurricane Electric's Tunnelbroker.net forums!
 
   Home   Help Search Login Register  
Hurricane Electric's IPv6 Tunnel Broker Forums > Tunnelbroker.net Specific Topics > Questions & Answers > www.ripe.net unreachable over ipv6
Pages: [1]
« previous next »
  Print  
Author Topic: www.ripe.net unreachable over ipv6  (Read 1580 times)
ewr
Newbie
*
Posts: 1


View Profile
« on: April 04, 2012, 05:41:06 pm »
Greetings.

My English is not very good, excuse me, if I said something wrong

Just created new tunnel. All seem works properly, ipv6.google.com reachable. But since ipv6 activated on my home computer, www.ripe.net site become unreachable at least from mozilla browser. I can reach this site only if disable ipv6 DNS resolving. What could be the reason? Maybe I did something wrong?

'mtr -6' to ww.ripe.net

Host                                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2001:470:71ed:1::1                                       0.0%    27    0.2   0.2   0.2   1.2   0.2
 2. Huh
 3. gige-g2-4.core1.fra1.he.net                              0.0%    27   56.3  60.4  56.1  70.8   4.6
 4. 10gigabitethernet1-4.core1.ams1.he.net                   0.0%    27   70.6  66.2  63.0  74.3   3.8
 5. amsix-501.xe-0-0-0.jun1.bit-1.network.bit.nl             0.0%    27   65.0  64.9  64.6  65.3   0.2
 6. gw.ipv6.amsix.telrtr.ripe.net                            0.0%    27   65.2  68.2  65.0 134.3  13.3
 7. Huh

And 'mtr -6' to ipv6.google.com
Host                                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2001:470:71ed:1::1                                       0.0%     8    0.2   0.3   0.2   1.3   0.4
 2. Huh
 3. gige-g2-4.core1.fra1.he.net                              0.0%     8   56.3  57.5  56.1  65.7   3.3
 4. de-cix10.net.google.com                                  0.0%     8   57.3  57.3  57.1  57.5   0.1
 5. 2001:4860::1:0:10                                        0.0%     7   57.4  57.9  57.4  59.7   0.8
 6. 2001:4860::4:0:5                                         0.0%     7   64.6  84.7  64.6 165.5  38.3
 7. 2001:4860::1:0:2b                                        0.0%     7   72.6  72.5  72.2  72.8   0.2
 8. 2001:4860:0:1::2ef                                       0.0%     7   72.6  72.5  72.3  72.8   0.2
 9. bud01s09-in-x14.1e100.net                                0.0%     7   72.2  72.0  71.8  72.2   0.2
Logged
cholzhauer
Hero Member
*****
Posts: 2094


View Profile
« Reply #1 on: April 05, 2012, 05:34:39 am »
I don't have any problems browsing to or pinging ripe.net
Logged
kasperd
Founder, Netiter ApS
Hero Member
*****
Posts: 767


View Profile
« Reply #2 on: April 05, 2012, 05:39:05 am »
I am using the same tunnel server, and I don't see the problem. I do see a few intermediate routers, that don't respond, but the final destination does respond. I suggest you try again.

I did recently see some similar symptoms recently, that turned out to be caused by a bug in mtr. I suggest you try using an ordinary traceroute command as well to verify if it shows you the same results as mtr.
Logged
DAR2133576
readonly_member
Newbie
*
Posts: 3


View Profile WWW
« Reply #3 on: April 17, 2012, 01:11:32 am »
I tried the same and it looks like everything is working fine here too.
Logged
jsarenik
Newbie
*
Posts: 2


View Profile
« Reply #4 on: May 01, 2012, 11:14:23 am »
Quote from: ewr on April 04, 2012, 05:41:06 pm
Just created new tunnel. All seem works properly, ipv6.google.com reachable. But since ipv6 activated on my home computer, www.ripe.net site become unreachable at least from mozilla browser. I can reach this site only if disable ipv6 DNS resolving. What could be the reason? Maybe I did something wrong?

The same here.

To state it more exactly, I can access all the servers (including HE IPv6 and RIPE) from "Client IPv6 Address", which is in my case 2001:470:6e:128::2/64, but from "Routed /64", i.e. 2001:470:6f:127::/64, I can not access www.ripe.net and IPv6 HE servers, though I can ssh to and from a non-HE IPv6 network to this routed segment, where the machine running IPv6 tunnel to HE is acting as a IPv6 router.

Tested with OpenBSD and Linux, each as server (tunnel+RA+router) and client trying to access www.ripe.net through the server. Ping6 to HE and RIPE machines works always.
Logged
jtcloe
Newbie
*
Posts: 46


View Profile
« Reply #5 on: May 01, 2012, 10:56:35 pm »
I just hit http://www.ripe.net/ from part of my routed /64 (not from the tunnel endpoint), and got to it just fine and it reported my ipv6 address on a little widget on the page.

I've also always been able to hit all of the HE servers as well from my routed /64.

If you can ping, but can't get a web page, that almost sounds more like a firewall issue, but that's just a guess without more info.
Logged
jsarenik
Newbie
*
Posts: 2


View Profile
« Reply #6 on: May 01, 2012, 11:22:44 pm »
Of course it was an MTU problem, because I am tunnelling through DSL.

For more info, see http://www.tunnelbroker.net/forums/index.php?topic=1408.0
« Last Edit: May 01, 2012, 11:39:25 pm by jsarenik » Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!