[BUG] IPv6: 6rd support breaks after an IPv4 change

---

FURRYe38 wrote:

I'll pass this on to NG.

KevinLiT 

---

Excellent, thank you so much!

In case that helps anyone, I wrote this ugly bash script (works on Linux) to detect when the Orbi needs to be rebooted. Should work with CenturyLink, but may not work elsewhere as the length of the 6rd prefix may vary depending on the ISP (/24 on CenturyLink). Just need to change/shift the sed regexp to adapt.

#!/bin/bash

ip4=$(curl -4 -s ipinfo.io | jq -er .ip)

ip6=$(sipcalc $(ip route get ::1234 | sed 's/.*src \([^ ]*\).*/\1/') | grep -F Expanded | cut -d '-' -f 2 | tr -d ' ')
ip6to4=$(echo $ip6 | sed 's/....:..\(..\):\(..\)\(..\):\(..\)..:....:....:....:..../printf "$((0x\1)).$((0x\2)).$((0x\3)).$((0x\4))"/' | bash -s)

echo "IPv4: $ip4"
echo "IPv4 from 6rd: $ip6to4"

if [[ "$ip4" != "$ip6to4" ]]; then
    echo "Reboot the Orbi" >&2
    exit 1
fi

FURRYe38 KevinLiT  did you end up talking to NG about this?

On my side, I ended up managing to open a support case without a support contract, but I don't think this is going anywhere. I've been asked to beta-test new firmware multiple times since March, but by now I think they're just asking me to beta-test every new iteration of firmware regardless of whether it is meant to address the issue or not. As far as I can tell, Netgear is ignoring the issue. New firmware versions don't make any difference with regard to 6rd behavior.

I don't know how many layers of communication there are between the support person and the firmware development people, but there's clearly a lot of information that's getting lost in the process. 4 months after opening the case, I am not very confident the issue is actually getting looked at.