Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: v6 on extreme with os/x clients behind it can't ping  (Read 3894 times)

kencrozier

  • Newbie
  • *
  • Posts: 4
v6 on extreme with os/x clients behind it can't ping
« on: December 25, 2010, 11:19:28 AM »

Hi, I have upgraded my extreme's firmware to 7.5.2 and don't get any messages about the tunnel to HE not working  (i wish apple would give a status of the tunnel) ... however I am still having problems pinging and resolving v6 addresses... Here's the configs for everything, the extreme is connected directly to the DSL.

He tunnel config is ...   

IPv6 Tunnel Endpoints
Server IPv4 address:   66.220.18.42
Server IPv6 address:    2001:470:c:c77::1/64
Client IPv4 address:    71.139.20.48
Client IPv6 address:    2001:470:c:c77::2/64
Available DNS Resolvers
Anycasted IPv6 Caching Nameserver:   2001:470:20::2
Anycasted IPv4 Caching Nameserver:   74.82.42.42
Routed IPv6 Prefixes and rDNS Delegations
Routed /48:    2001:470:f2e6::/48
Routed /64:    2001:470:d:c77::/64

extreme V6 setup

IPv6 mode = Tunnel
Block incoming ipv6 connections
config ipv6 = manually
remote ipv4 addr. = 66.220.18.42
wan ipv6 addr. = 2001:470:c:c77::2
ipv6 default route = 2001:470:c:c77::1
lan ipv6 addr. = 2001:470:d:c77::

Imac is set to get v6 addr automatically

imac if/netstat/ping6s and traceroute6 are ....

Kens-iMac:~ ken$ ping6 2001:470:c:c77::1
PING6(56=40+8+8 bytes) 2001:470:d:c77:d69a:20ff:fec1:aa98 --> 2001:470:c:c77::1
Request timeout for icmp_seq=0
Request timeout for icmp_seq=1
Request timeout for icmp_seq=2
Request timeout for icmp_seq=3
^C
--- 2001:470:c:c77::1 ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

Kens-iMac:~ ken$ ping6 2001:470:c:c77::2
PING6(56=40+8+8 bytes) 2001:470:d:c77:d69a:20ff:fec1:aa98 --> 2001:470:c:c77::2
16 bytes from 2001:470:c:c77::2, icmp_seq=0 hlim=64 time=6.313 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=1 hlim=64 time=0.365 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=2 hlim=64 time=0.364 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=3 hlim=64 time=0.329 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=4 hlim=64 time=0.356 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=5 hlim=64 time=0.354 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=6 hlim=64 time=0.352 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=7 hlim=64 time=0.366 ms
16 bytes from 2001:470:c:c77::2, icmp_seq=8 hlim=64 time=0.356 ms
^C
--- 2001:470:c:c77::2 ping6 statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.329/1.017/6.313/1.872 ms

Kens-iMac:~ ken$ traceroute6 ipv6.google.com
traceroute6 to ipv6.l.google.com (2001:4860:8010::67) from 2001:470:d:c77:d69a:20ff:fec1:aa98, 64 hops max, 12 byte packets
 1  2001:470:d:c77:21e:52ff:fef0:5ea2  0.434 ms  0.418 ms  0.364 ms
 2  * * *
 3  * * *
 4  * *^C
Kens-iMac:~ ken$ if
>
Kens-iMac:~ ken$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
   inet6 ::1 prefixlen 128
   inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
   inet 127.0.0.1 netmask 0xff000000
   inet6 fd84:bec3:f7d5:e761:d69a:20ff:fec1:aa98 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ether d4:9a:20:c1:aa:98
   inet6 fe80::d69a:20ff:fec1:aa98%en0 prefixlen 64 scopeid 0x4
   inet 192.168.1.4 netmask 0xffffff00 broadcast 192.168.1.255
   inet6 2001:470:d:c77:d69a:20ff:fec1:aa98 prefixlen 64 autoconf
   media: autoselect (1000baseT <full-duplex,flow-control>)
   status: active
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
   lladdr d4:9a:20:ff:fe:c1:aa:98
   media: autoselect <full-duplex>
   status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ether d4:9a:20:5c:2e:b7
   media: autoselect (<unknown type>)
   status: inactive
vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ether 00:50:56:c0:00:08
   inet 172.16.96.1 netmask 0xffffff00 broadcast 172.16.96.255
vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ether 00:50:56:c0:00:01
   inet 172.16.202.1 netmask 0xffffff00 broadcast 172.16.202.255
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
   inet6 fe80::d69a:20ff:fec1:aa98%utun0 prefixlen 64 scopeid 0x9
   inet6 fd00:6587:52d7:42:d69a:20ff:fec1:aa98 prefixlen 64
Kens-iMac:~ ken$ netstat -r
Routing tables

Internet:
Destination        Gateway            Flags        Refs      Use   Netif Expire
default            192.168.1.1        UGSc           55        0     en0
127                localhost          UCS             0        0     lo0
localhost          localhost          UH              4   396004     lo0
169.254            link#4             UCS             1        0     en0
169.254.1.0        link#4             UHRLW           1     1258     en0      5
172.16.96/24       link#7             UC              1        0  vmnet8
172.16.96.255      link#7             UHLWbI          1      629  vmnet8
172.16.202/24      link#8             UC              1        0  vmnet1
172.16.202.255     link#8             UHLWbI          2      627  vmnet1
192.168.1          link#4             UCS             4        0     en0
192.168.1.1        0:1e:52:f0:5e:a2   UHLWI          73      874     en0   1120
192.168.1.4        localhost          UHS             0        0     lo0
192.168.1.5        0:11:24:6f:9:5e    UHLWI           2     5449     en0     39
192.168.1.38       0:22:41:1b:25:b4   UHLWI           0        0     en0    582
192.168.1.255      link#4             UHLWbI          1      626     en0

Internet6:
Destination        Gateway            Flags         Netif Expire
default            kcs.local          UGSc            en0
localhost          localhost          UH              lo0
2001:470:d:c77::   link#4             UC              en0
2001:470:d:c77:211 0:11:24:6f:9:5e    UHLW            en0
2001:470:d:c77:21e 0:1e:52:f0:5e:a2   UHLW            en0
2001:470:d:c77:d69 d4:9a:20:c1:aa:98  UHL             lo0
fd00:6587:52d7::   fd00:6587:52d7:42: UGCS          utun0
fd00:6587:52d7:42: fd00:6587:52d7:42: UGHW          utun0
fd00:6587:52d7:42: link#9             UHL             lo0
fd84:bec3:f7d5:e76 link#1             UHL             lo0
fe80::%lo0         localhost          Uc              lo0
localhost          link#1             UHL             lo0
fe80::%en0         link#4             UC              en0
playme.local       0:11:24:6f:9:5e    UHLW            en0
kcs.local          0:1e:52:f0:5e:a2   UHLW            en0
kens-imac.local    d4:9a:20:c1:aa:98  UHL             lo0
fe80::%utun0       fe80::d69a:20ff:fe Uc            utun0
fe80::d69a:20ff:fe link#9             UHL             lo0
ff01::             localhost          Um              lo0
ff02::             localhost          UmC             lo0
ff02::             link#4             UmC             en0
ff02::             fe80::d69a:20ff:fe UmC           utun0
Kens-iMac:~ ken$

is there something basic that i'm doing wrong ?
tia
ken
Logged

kriteknetworks

  • Sr. Member
  • ****
  • Posts: 260
    • aRDy Music
Re: v6 on extreme with os/x clients behind it can't ping
« Reply #1 on: December 25, 2010, 02:42:23 PM »

Forwarding enabled? (No I dont know how, if possible, to set that)
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2706
Re: v6 on extreme with os/x clients behind it can't ping
« Reply #2 on: December 26, 2010, 07:46:15 AM »

I assume it used to work before the upgrade?

Only thing that caught my eye was the strange default route you listed, but if that's how it was before, I don't know what else to think
Logged

kencrozier

  • Newbie
  • *
  • Posts: 4
Re: v6 on extreme with os/x clients behind it can't ping
« Reply #3 on: December 26, 2010, 08:34:32 AM »

no it did not work before the upgrade, as there was a problem with the previous firmware with dynamic addresses ......
What is the funny default route ? what should it be ?
thanks
ken
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2706
Re: v6 on extreme with os/x clients behind it can't ping
« Reply #4 on: December 27, 2010, 05:06:13 AM »

Well, this is what the routing table looks like from one of the working mac's at my company

Code: [Select]
netstat -nr
Routing tables

--snip--

Internet6:
Destination                             Gateway                         Flags         Netif Expire
default                                 fe80::21d:a2ff:feaf:2ffc%en0    UGSc            en0
::1                                     ::1                             UH              lo0
2001:470:c27d:f000::/64                 link#5                          UC              en0
2001:470:c27d:f000:225:4bff:feb8:a360   0:25:4b:b8:a3:60                UHL             lo0
fe80::%lo0/64                           fe80::1%lo0                     Uc              lo0
fe80::1%lo0                             link#1                          UHL             lo0
fe80::%en0/64                           link#5                          UC              en0
fe80::21d:a2ff:feaf:2ffc%en0            0:1d:a2:af:2f:fc                UHLW            en0
fe80::225:4bff:feb8:a360%en0            0:25:4b:b8:a3:60                UHL             lo0
ff01::/32                               ::1                             Um              lo0
ff02::/32                               ::1                             UmC             lo0
ff02::/32                               link#5                          UmC             en0
ff02::fb                                link#5                          UHmLW           en0

Logged

kencrozier

  • Newbie
  • *
  • Posts: 4
Re: v6 on extreme with os/x clients behind it can't ping
« Reply #5 on: December 27, 2010, 11:37:53 AM »

well after getting my eyes tested I noticed that /64 was 2001:470:d ..... and not 2001:470:c .... as i had it
have changed it but still have the same issues ?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2706
Re: v6 on extreme with os/x clients behind it can't ping
« Reply #6 on: December 27, 2010, 11:42:55 AM »

Is there a console on the airport extreme that you can use to test with ping and whatnot?

How is your AE doling out addresses?  Like I mentioned, your default route does not look the route I posted
Logged

kencrozier

  • Newbie
  • *
  • Posts: 4
Re: v6 on extreme with os/x clients behind it can't ping
« Reply #7 on: December 27, 2010, 12:56:57 PM »

No there is not a utility to ping from the AES, the address's it is handing out are good and i can ping the local interface on v6
Logged