Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: problems accessing ipv6.google.com  (Read 529 times)

tezzanet

  • Newbie
  • *
  • Posts: 3
    • View Profile
problems accessing ipv6.google.com
« on: April 10, 2017, 12:08:08 AM »

Hi all,
I am having problems accessing any website over the 6in4 tunnel.
i can ping the server at the far end of the tunnel, i can ping ipv6google.com but i CANT access the site with either browser or wget,
system is debian jessie (8). after MUCH playing with config for the tunnel (as the new debian uses the new ip command for setting up interfaces not the old ifconfig if-up if-down format.
when i try to connect to ipv6.google.com it comes up with the address and says connected but then sits there forever waiting for the site to send data.

included is  my ifconfig output, ip addr output ip -6 route output and ping6 output.
Code: [Select]
ifconfig output:

eth0      Link encap:Ethernet  HWaddr 00:1e:90:fe:d7:ae 
          inet addr:10.0.0.88  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:90ff:fefe:d7ae/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:29475 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9872 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:23690538 (22.5 MiB)  TX bytes:1748662 (1.6 MiB)

he-ipv6   Link encap:IPv6-in-IPv4 
          inet6 addr: fe80::ac10:5801/64 Scope:Link
          inet6 addr: 2001:470:36:d7f::1/64 Scope:Global
          inet6 addr: fe80::a00:57/64 Scope:Link
          inet6 addr: fe80::a00:58/64 Scope:Link
          inet6 addr: fe80::c0a8:9401/64 Scope:Link
          inet6 addr: 2001:470:35:d7f::2/64 Scope:Global
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:279 errors:0 dropped:0 overruns:0 frame:0
          TX packets:752 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:67846 (66.2 KiB)  TX bytes:149989 (146.4 KiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:578 errors:0 dropped:0 overruns:0 frame:0
          TX packets:578 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:36725 (35.8 KiB)  TX bytes:36725 (35.8 KiB)

wlan0     Link encap:Ethernet  HWaddr 48:5d:60:1f:48:67 
          inet addr:10.0.0.87  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::4a5d:60ff:fe1f:4867/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:308124 errors:0 dropped:0 overruns:0 frame:0
          TX packets:284793 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:438050142 (417.7 MiB)  TX bytes:27899342 (26.6 MiB)

ip -6 route output

2001:470:35:d7f::/64 dev he-ipv6  proto kernel  metric 256
2001:470:36:d7f::/64 dev he-ipv6  proto kernel  metric 256
2000::/3 dev he-ipv6  metric 1024
fe80::/64 via fe80::267f:20ff:fe76:dbc dev wlan0  proto ra  metric 10
fe80::/64 dev wlan0  proto kernel  metric 256  mtu 1488
fe80::/64 dev vmnet1  proto kernel  metric 256
fe80::/64 dev vmnet8  proto kernel  metric 256
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1488
fe80::/64 dev he-ipv6  proto kernel  metric 256
default dev he-ipv6  metric 1024

ip -6 addr output

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::21e:90ff:fefe:d7ae/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::4a5d:60ff:fe1f:4867/64 scope link
       valid_lft forever preferred_lft forever
4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::250:56ff:fec0:1/64 scope link
       valid_lft forever preferred_lft forever
5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::250:56ff:fec0:8/64 scope link
       valid_lft forever preferred_lft forever
7: he-ipv6@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480
    inet6 2001:470:36:d7f::1/64 scope global
       valid_lft forever preferred_lft forever
    inet6 2001:470:35:d7f::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::c0a8:9401/64 scope link
       valid_lft forever preferred_lft forever
    inet6 fe80::ac10:5801/64 scope link
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:57/64 scope link
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:58/64 scope link
       valid_lft forever preferred_lft forever

ping6 ipv6.google.com output

PING ipv6.google.com(syd09s01-in-x0e.1e100.net) 56 data bytes
64 bytes from syd09s01-in-x0e.1e100.net: icmp_seq=1 ttl=55 time=458 ms
64 bytes from syd09s01-in-x0e.1e100.net: icmp_seq=2 ttl=55 time=454 ms
64 bytes from syd09s01-in-x0e.1e100.net: icmp_seq=3 ttl=55 time=449 ms

--- ipv6.google.com ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3003ms
rtt min/avg/max/mdev = 449.052/453.842/458.423/3.906 ms
Hope someone can help, this is driving me nuts.
my ISP telstra.com.au SAYS they allow IPv6 but there is NO ipv6 router advertisments coming through to the router and i cant send ipv6 out through the router,(it drops all outbound ipv6 packets) i have also heard that they block 6in4 tunnels although it SEEMS to work in a limited way.
thanks in advance. Tezza.
Logged

snarked

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: problems accessing ipv6.google.com
« Reply #1 on: April 10, 2017, 01:25:43 PM »

First:  Only one of these should be on your 6in4 interface.  The other should be on your Ethernet (or Wi-Fi):

inet6 addr: 2001:470:35:d7f::2/64 Scope:Global
inet6 addr: 2001:470:36:d7f::1/64 Scope:Global

The second one looks like the one that should be on your Ethernet.  Fixing that will allow other machines on your local network to access the outside world.

Second:  Try an MTU of 1280.

Third:  Check your firewall - both IPv4 and IPv6 (although the pings worked, maybe you're blocking something else).
Logged

tezzanet

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: problems accessing ipv6.google.com
« Reply #2 on: April 10, 2017, 06:45:24 PM »

well,
i can now access ipv6.google.com and ap-ipv6tf.org (which shows my ipv6 address in the top right corner of the pagenot ipv4 address) so i think its good now.
BUT i still dont pass the explorers test,
the address given in the example is non existant, unreachable by ping or browseing. so if thats the site you must contact to complete the exam that makes the explorers exam a bit pointless.
Logged

tezzanet

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: problems accessing ipv6.google.com
« Reply #3 on: April 10, 2017, 11:46:46 PM »

After changing the MTU of the tunnel to 1280 still cant load the ipv6.he.net website (used the address obtained by dig from the nameserver 2001:470:0:64::2) while i can still load the ipv6.google.com website. got me totally confused. and ive been working with networking for well over 20 years.
Logged