Tom---
Level 1 (0 points)

Q: No IPv6 after wake from sleep

Hello,

 

     When my MB pro wakes from sleep there is no IPv6 connectivity. In order to restore IPv6 I need to stop/start the Thunderbolt Ethernet adapter (make service inactive/make service active) or reboot.

 

     Details on my configuration:

 

  •      OS X 10.9.2
  •      Thunderbolt Ethernet Adapter used for network connectivity (Wi-Fi OFF)
  •      Native IPv6 network (not tunneled)
  •      IPv6 and v4 manual config (no DHCP or SLAAC)
  •      Dual stack TCP/IP configuration
  •      IPv4 works
  •      IPv6 works until MB goes into sleep mode

 

ifconfig

en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

          options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>

          ether a8:20:xx:xx:xx:xx

          inet6 fe80::aa20:xxxx:xxxx:xxxx%en2 prefixlen 64 scopeid 0x4

          inet6 2001:xxxx:xxxx:1::2 prefixlen 64

          inet 8.x.x.2 netmask 0xffffffc0 broadcast 8.x.x.63

          nd6 options=1<PERFORMNUD>

          media: autoselect (100baseTX <full-duplex,flow-control>)

          status: active

 

^---- Looks good (to me).

 

netstat -nr -f inet6

Internet6:

Destination                             Gateway                         Flags         Netif Expire

default                                 2001:xxxx:xxxx:1::1             UGc             en2

::1                                     ::1                             UHL             lo0

2001:xxxx:xxxx:1::2                     a8:20:xx:xx:xx                  UHL             lo0

fe80::%lo0/64                           fe80::1%lo0                     UcI             lo0

 

^---  This looks good too (to me).

 

Ping my Thunderbolt Ethernet Adapter

PING6(56=40+8+8 bytes) 2001:xxxx:xxxx:1::2 --> 2001:xxxx:xxxx:1::2

16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=0 hlim=64 time=0.129 ms

16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=1 hlim=64 time=0.233 ms

16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=2 hlim=64 time=0.225 ms

16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=3 hlim=64 time=0.227 ms

 

^--- Yay!

 

Ping the default route

PING6(56=40+8+8 bytes) 2001:xxxx:xxxx:1::2 --> 2001:xxxx:xxxx:1::1

ping6: sendmsg: No route to host

ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1

ping6: sendmsg: No route to host

ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1

ping6: sendmsg: No route to host

ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1


^--- Boo

 

This causes problems for IPv4 as well because apps like Firefox and Safari try using the IPv6 DNS servers and give up before falling back to the IPv4 servers.  So this problem breaks more than IPv6.

 

Is this a bug or do I have something misconfigured?

 

Thanks.

 

                               --Tom

Mac Pro, OS X Mavericks (10.9.2)

Posted on Apr 17, 2014 7:02 AM

Close
Tom---

Q: No IPv6 after wake from sleep

  • All replies
  • Helpful answers

  • by rudi van Drunen,

    rudi van Drunen rudi van Drunen Jul 8, 2014 12:43 PM in response to Tom---
    Level 1 (20 points)
    Jul 8, 2014 12:43 PM in response to Tom---

    I see this (sort of) behaviour as well. When I look into the tcp/ip tab of the network (system prefs) I see

    fe80::1:1 as router, that is why v6 stops working. After turning v6 off and on again the correct router IP appears.

     

    NB. this is on wifi

     

    Rudi

  • by chrisk-de,

    chrisk-de chrisk-de Jul 3, 2016 5:21 AM in response to rudi van Drunen
    Level 1 (8 points)
    Mac OS X
    Jul 3, 2016 5:21 AM in response to rudi van Drunen

    I am still seeing the exact same issue with El Capitan.

    Having a link-local address as the default gateway is not an issue.

    I can also easily ping my default gateway during times of no network connectivity right after wakeup from sleep

     

    $  ping6 google.de

    PING6(56=40+8+8 bytes) 2003:de:4bc9:dc00:199a:edff:5214:e01 --> 2a00:1450:4001:816::2003^C

    --- google.de ping6 statistics ---

    7 packets transmitted, 0 packets received, 100.0% packet loss

     

    $ ifconfig en0

    en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

      ether 60:03:08:8d:ac:e2

      inet6 fe80::6203:8ff:fe8d:ace2%en0 prefixlen 64 scopeid 0x4

      inet 10.1.16.131 netmask 0xffffff00 broadcast 10.1.16.255

      inet6 2003:de:4bc9:dc00:6203:8ff:fe8d:ace2 prefixlen 64 autoconf

      inet6 2003:de:4bc9:dc00:199a:edff:5214:e01 prefixlen 64 autoconf temporary

     

    $ netstat -nrf inet6

    Routing tables

    Internet6:

    Destination                             Gateway                         Flags         Netif Expire

    default                                 fe80::3631:c4ff:fefd:da7%en0    UGc             en0

    [...]

     

    $ ping6 fe80::3631:c4ff:fefd:da7%en0

    PING6(56=40+8+8 bytes) fe80::6203:8ff:fe8d:ace2%en0 --> fe80::3631:c4ff:fefd:da7%en0

    16 bytes from fe80::3631:c4ff:fefd:da7%en0, icmp_seq=0 hlim=64 time=2.158 ms

    16 bytes from fe80::3631:c4ff:fefd:da7%en0, icmp_seq=1 hlim=64 time=1.937 ms

    ^C

    --- fe80::3631:c4ff:fefd:da7%en0 ping6 statistics ---

    2 packets transmitted, 2 packets received, 0.0% packet loss

    round-trip min/avg/max/std-dev = 1.937/2.047/2.158/0.110 ms

     

    Aand just a few seconds later it magically works again and my gateway and ipv6 address are still the same:

    $  ping6 google.de

    PING6(56=40+8+8 bytes) 2003:de:4bc9:dc00:199a:edff:5214:e01 --> 2a00:1450:4001:816::2003

    16 bytes from 2a00:1450:4001:816::2003, icmp_seq=0 hlim=57 time=13.160 ms

    16 bytes from 2a00:1450:4001:816::2003, icmp_seq=1 hlim=57 time=10.449 ms

    ^C

    --- google.de ping6 statistics ---

    2 packets transmitted, 2 packets received, 0.0% packet loss

    round-trip min/avg/max/std-dev = 10.449/11.805/13.160/1.355 ms

     

    It really is a shame that apple has not yet fixed this as more and more sites get ipv6 enabled, which leads to basically no connectivity for the first seconds/minutes after wakeup from sleep!

  • by Eric Root,

    Eric Root Eric Root Jul 3, 2016 8:56 AM in response to chrisk-de
    Level 9 (69,659 points)
    iTunes
    Jul 3, 2016 8:56 AM in response to chrisk-de

    Send Apple feedback. They won't answer, but at least will know there is a problem or a suggestion for improvement. If enough people send feedback, it may get the problem/suggested change solved sooner.

     

    Feedback