Nest WiFi and IPv6

[Sicario]

Weird, mine says the same. From that I’d assume you dont have ipv6, which is even more confusing! 

Yeah I really didn’t believe it but just wanted to prove It to the support guy so he escalates it properly. 

Although I think the issue is incoming tags, for eg VoIP/TV. The modem I have uses a separate tel port, and I ran the wan connection through an unmanaged switch that strips tags but still no joy. 

[Dooley_do]

You are right, i am able to flip the IPv6 toggle but it doesn't actually work...

[Sicario]

Ah sorry, was confused with you and @Coco85 - would be good to see what a working one looks like. 

Im pretty sure the support line can manage the connection remotely, as they knew I had a DHCP reservation. Wouldn’t be surprised if they had made some changes to the config that you can see in the diag report but can’t touch. 

[Coco85]

The only config I can see relating to IPv6 in my diagnostics file is below.  All other reference is routes etc.

Working IPv6 Prefix
ipv6 {
config {
source: IPV6_CONFIG_SOURCE_USER
enable: true
allow_on_ap: true
}
flags {
ipv6_feature_over_pppoe: true
}
}

ipv6_state {
non_temporary_address_received: false
prefix_delegation_received: true
allow_on_ap: true
ap_status: AP_IPV6_STATUS_TEST_SUCCESS
}
ipv6_config {
enabled: true
prefix: "2a00:xxxx:xxxx:xxxx::"
prefix_length: 56
source: "user"
mode: "prod"

persistent_reachability_check {
reachability_state: IPV6_REACHABILITY_STATE_OK
reboot_count: 0
}
persistent_ap_status: AP_IPV6_STATUS_TEST_SUCCESS

-----------------------------------------------------------------------------------

No IPv6 allocation

ipv6 {
config {
source: IPV6_CONFIG_SOURCE_USER
enable: true
allow_on_ap: false
}
flags {
ipv6_feature_over_pppoe: true
}
}

ipv6_state {
non_temporary_address_received: false
prefix_delegation_received: false
allow_on_ap: false
ap_status: AP_IPV6_STATUS_TEST_FAILED_V4_AFFECTED
}
ipv6_config {
enabled: true
prefix: ""
prefix_length: 0
source: "user"
mode: "prod"

persistent_reachability_check {
reachability_state: IPV6_REACHABILITY_STATE_REBOOT
reboot_count: 1
}
persistent_ap_status: AP_IPV6_STATUS_TEST_FAILED_V4_AFFECTED

[Coco85]

Out of interest - do you have a "experiment_config_version" above the ipv6 config?  If so, what version is presented?
Mine has changes since the last time I ran the diagnostics - about 1 month ago

[Dooley_do]

166

[Coco85]

@Dooley_do  - same here.  Was 159 back in May

[Sicario]

Also 166. FW version is 12371.71.11 

  ipv6_state {
    non_temporary_address_received: false
    prefix_delegation_received: false
    allow_on_ap: false
    ap_status: AP_IPV6_STATUS_TEST_FAILED_NO_IAPD

 
Here's the rest of my IPv6 info:

ipv6_config {
    enabled: true
    prefix: ""
    prefix_length: 0
    source: "user"
    mode: "prod"

  persistent_reachability_check {
    reachability_state: IPV6_REACHABILITY_STATE_RETRY_LONG
    reboot_count: 0
  }
  persistent_ap_status: AP_IPV6_STATUS_TEST_FAILED_NO_IAPD

experiment_config_version: "166"
ipv6 {
  config {
    source: IPV6_CONFIG_SOURCE_USER
    enable: true
    allow_on_ap: false
  }
  flags {
    ipv6_feature_over_pppoe: true
  }

Wonder if they've just toggled the allow on AP flag to true on their backend. I also see from the processes that the IPv6 daemon is running and set to retry, so it's definitely actively looking to connect. No issues from my HH being able to pull it.

[Coco85]

Hi @Sicario - I've edited my earlier post with all relevant IPv6 output

[Sicario]

Thanks! Will pass that on to Google. 

Heres hoping this update will improve things.