Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 [2]

Author Topic: Set up tunnel and now only ipv6.google.com works, but other sites ping fine.  (Read 13841 times)

AndrejaKo

  • Newbie
  • *
  • Posts: 16

It doesn't work on OpenWRT. I get No such process when I try to use server ipv4 address and I get an inet address is expected when I try to use IPv6 address.


Also, if I have problem with routes, why would Google and ping work fine?


Also, I think I forgot to mention,  stopping firewall service doesn't help.
« Last Edit: February 25, 2011, 10:20:58 AM by AndrejaKo »
Logged

Mierdin

  • Newbie
  • *
  • Posts: 30

Here's the linux version - windows makes this all nice by showing both tables with a netstat -rn but it needs some arguments on the linux side

Code: [Select]
[root@localhost ~]# ip -f inet6 route
2001:470:FFFF:FFFF::/64 dev eth0  proto kernel  metric 256  expires 214710sec mtu 1500 advmss 1440 hoplimit 64
fe80::/64 dev eth0  metric 256  expires 2099218sec mtu 1500 advmss 1440 hoplimit 64
ff00::/8 dev eth0  metric 256  expires 2099218sec mtu 1500 advmss 1440 hoplimit 1
default via fe80::2aa:aaff:feaa:aaaa dev eth0  proto kernel  metric 1024  expires 175sec mtu 1500 advmss 1440 hoplimit 64
unreachable default dev lo  proto none  metric -1  error -101 hoplimit 255
[root@localhost ~]#

I don't run OpenWRT so I'm only assuming you can run that

Also - yours will hopefully look a bit different - this device isn't configured for IPv6 in any intelligent way

« Last Edit: February 25, 2011, 12:12:26 PM by Mierdin »
Logged

Mierdin

  • Newbie
  • *
  • Posts: 30

In addition:
I would ping henet's DNS server for example (2001:470:20::2) from your windows client. If the problem is DNS related, you might have basic IP connectivity, and this will prove that. Would also rule out routing problems.

Also - how are you distributing DNS info to your clients? To rule it out, I'd statically set your DNS server to HE.NET's DNS server on your windows clients (assuming you could get to that server successfully in the first test) for resolution.
« Last Edit: February 25, 2011, 12:18:37 PM by Mierdin »
Logged

AndrejaKo

  • Newbie
  • *
  • Posts: 16

Here:
Code: [Select]
root@OpenWrt:/# ip -f inet6 route
2001:470:1f0a:de5::/64 via :: dev 6in4-henet  proto kernel  metric 256  mtu 1280 advmss 1220 hoplimit 0
2001:470:1f0b:de5::/64 dev br-lan  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev br-lan  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0.1  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0.2  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 0
fe80::/64 via :: dev 6in4-henet  proto kernel  metric 256  mtu 1280 advmss 1220 hoplimit 0
default dev 6in4-henet  metric 1024  mtu 1280 advmss 1220 hoplimit 0

I can ping the DNS server fine from windows. Setting DNS server by hand didn't help.

As for DNS info, right now I have the RDNSS field in RADVD empty and rely on DNS servers which computers get from IPv4 DHCP. I'm using servers form my local ISP and Google's 8.8.8.8 and I didn't have any problems with name resolution so far. Name resolution seems to be working fine with HE's servers too.
Logged

Mierdin

  • Newbie
  • *
  • Posts: 30

Its not a routing issue, you have the correct entry for a default route to your tunnel IF. As you said, pings all work fine for any valid address (correct?)

So ipv6.google.com loads in FF but no other page does? What about whatismyipv6.com?

If that's true, my vote's for gremlins.  ::) Usually my first instinct is "shut off firewall, work from there" but reading back it looks like that didn't work.
Does this behavior manifest on other PCs on your network?
« Last Edit: February 26, 2011, 03:06:57 AM by Mierdin »
Logged

AndrejaKo

  • Newbie
  • *
  • Posts: 16

I just tried with two other PCs and same problems happen to them too. I also tried with openSUSE 11.3 and it too doesn't work, so this could still be a router issue. Maybe I'm having firewall problems? But if that was the case, everything would be working fine with firewall off.

whatismyipv6 only works over IPv4.

Here are some pings and tracerts:
Code: [Select]
Pinging whatismyipv6.com [2001:4870:a24f:2::90] with 32 bytes of data:
Reply from 2001:4870:a24f:2::90: time=222ms
Reply from 2001:4870:a24f:2::90: time=217ms
Reply from 2001:4870:a24f:2::90: time=221ms
Reply from 2001:4870:a24f:2::90: time=219ms

Ping statistics for 2001:4870:a24f:2::90:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 217ms, Maximum = 222ms, Average = 219ms

Code: [Select]
Tracing route to whatismyipv6.com [2001:4870:a24f:2::90]
over a maximum of 30 hops:

  1     7 ms     1 ms     1 ms  2001:470:1f0b:de5::1
  2    69 ms    70 ms    63 ms  AndrejaKo-1.tunnel.tserv6.fra1.ipv6.he.net [2001:470:1f0a:de5::1]
  3    57 ms    65 ms    58 ms  gige-g2-4.core1.fra1.he.net [2001:470:0:69::1]
  4    73 ms    74 ms    75 ms  10gigabitethernet1-4.core1.ams1.he.net [2001:470:0:47::1]
  5    71 ms    74 ms    76 ms  10gigabitethernet1-4.core1.lon1.he.net [2001:470:0:3f::1]
  6   141 ms   149 ms   148 ms  10gigabitethernet2-3.core1.nyc4.he.net [2001:470:0:3e::1]
  7   141 ms   147 ms   143 ms  10gigabitethernet1-2.core1.nyc1.he.net [2001:470:0:37::2]
  8   144 ms   145 ms   142 ms  2001:504:1::a500:4323:1
  9   226 ms   225 ms   218 ms  2001:4870:a240::2
 10   220 ms   224 ms   219 ms  2001:4870:a240::2
 11   219 ms   218 ms   220 ms  2001:4870:a24f::2
 12   221 ms   222 ms   220 ms  www.whatismyipv6.com [2001:4870:a24f:2::90]

Trace complete.

Code: [Select]
Tracing route to ipv6.l.google.com [2a00:1450:8004::68]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  2001:470:1f0b:de5::1
  2    67 ms    63 ms    64 ms  AndrejaKo-1.tunnel.tserv6.fra1.ipv6.he.net [2001:470:1f0a:de5::1]
  3    58 ms    57 ms    60 ms  gige-g2-4.core1.fra1.he.net [2001:470:0:69::1]
  4    61 ms    88 ms    60 ms  de-cix20.net.google.com [2001:7f8::3b41:0:2]
  5    61 ms    64 ms    60 ms  2001:4860::1:0:11
  6    74 ms    71 ms    70 ms  2001:4860::1:0:fdd
  7    78 ms    74 ms    74 ms  2001:4860::1:0:60d
  8    73 ms   245 ms    78 ms  2001:4860::2:0:612
  9    75 ms     *       76 ms  2001:4860:0:1::9d
 10    76 ms    74 ms    73 ms  2a00:1450:8004::68

Trace complete.

Code: [Select]
Tracing route to orange.kame.net [2001:200:dff:fff1:216:3eff:feb1:44d7]
over a maximum of 30 hops:

  1     4 ms     1 ms     1 ms  2001:470:1f0b:de5::1
  2    65 ms    68 ms    64 ms  AndrejaKo-1.tunnel.tserv6.fra1.ipv6.he.net [2001:470:1f0a:de5::1]
  3    60 ms    65 ms    56 ms  gige-g2-4.core1.fra1.he.net [2001:470:0:69::1]
  4    60 ms    58 ms    58 ms  xe-0.de-cix.frnkge03.de.bb.gin.ntt.net [2001:7f8::b62:0:1]
  5    62 ms    62 ms    64 ms  ae-0.r21.frnkge04.de.bb.gin.ntt.net [2001:728:0:2000::2]
  6    64 ms    69 ms    67 ms  as-1.r23.amstnl02.nl.bb.gin.ntt.net [2001:728:0:2000::13d]
  7    71 ms    65 ms    63 ms  as-0.r22.amstnl02.nl.bb.gin.ntt.net [2001:728:0:2000::11]
  8   375 ms   384 ms   373 ms  as-0.r25.tokyjp01.jp.bb.gin.ntt.net [2001:418:0:2000::16]
  9   449 ms   372 ms   418 ms  ae-9.r20.tokyjp01.jp.bb.gin.ntt.net [2001:218:0:2000::1c5]
 10   377 ms   379 ms   378 ms  po-1.a15.tokyjp01.jp.ra.gin.ntt.net [2001:218:0:6000::10e]
 11   333 ms   329 ms   334 ms  ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net [2001:218:2000:5000::82]
 12   331 ms   341 ms   332 ms  ve44.foundry6.otemachi.wide.ad.jp [2001:200:0:10::141]
 13   333 ms   333 ms   331 ms  ve42.foundry4.nezu.wide.ad.jp [2001:200:0:11::66]
 14   331 ms   329 ms   331 ms  cloud-net1.wide.ad.jp [2001:200:0:1c0a:218:8bff:fe43:d1d0]
 15   331 ms   334 ms   330 ms  2001:200:dff:fff1:216:3eff:feb1:44d7

Trace complete.

Code: [Select]
Tracing route to orange.kame.net [2001:200:dff:fff1:216:3eff:feb1:44d7]
over a maximum of 30 hops:

  1     4 ms     1 ms     1 ms  2001:470:1f0b:de5::1
  2    65 ms    68 ms    64 ms  AndrejaKo-1.tunnel.tserv6.fra1.ipv6.he.net [2001:470:1f0a:de5::1]
  3    60 ms    65 ms    56 ms  gige-g2-4.core1.fra1.he.net [2001:470:0:69::1]
  4    60 ms    58 ms    58 ms  xe-0.de-cix.frnkge03.de.bb.gin.ntt.net [2001:7f8::b62:0:1]
  5    62 ms    62 ms    64 ms  ae-0.r21.frnkge04.de.bb.gin.ntt.net [2001:728:0:2000::2]
  6    64 ms    69 ms    67 ms  as-1.r23.amstnl02.nl.bb.gin.ntt.net [2001:728:0:2000::13d]
  7    71 ms    65 ms    63 ms  as-0.r22.amstnl02.nl.bb.gin.ntt.net [2001:728:0:2000::11]
  8   375 ms   384 ms   373 ms  as-0.r25.tokyjp01.jp.bb.gin.ntt.net [2001:418:0:2000::16]
  9   449 ms   372 ms   418 ms  ae-9.r20.tokyjp01.jp.bb.gin.ntt.net [2001:218:0:2000::1c5]
 10   377 ms   379 ms   378 ms  po-1.a15.tokyjp01.jp.ra.gin.ntt.net [2001:218:0:6000::10e]
 11   333 ms   329 ms   334 ms  ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net [2001:218:2000:5000::82]
 12   331 ms   341 ms   332 ms  ve44.foundry6.otemachi.wide.ad.jp [2001:200:0:10::141]
 13   333 ms   333 ms   331 ms  ve42.foundry4.nezu.wide.ad.jp [2001:200:0:11::66]
 14   331 ms   329 ms   331 ms  cloud-net1.wide.ad.jp [2001:200:0:1c0a:218:8bff:fe43:d1d0]
 15   331 ms   334 ms   330 ms  2001:200:dff:fff1:216:3eff:feb1:44d7

Trace complete.


Logged

AndrejaKo

  • Newbie
  • *
  • Posts: 16

People at OpenWRT forums solved the issue. I set up MTU advertised over radvd to 1280 and everything is working fine now.
Logged
Pages: 1 [2]