tormozillo

A solution might be done from server side. I found this bash-script on Archlinux wiki, after run once ipv6 works at least 12 hours now: #!/usr/bin/bash declare -a l_ifs readarray l_ifs < <(/sbin/ip -6 -j address | jq -r '.[] | .ifname ') for l_if in ${l_ifs[@]} ; do echo $l_if declare -a l_addrs readarray l_addrs < <(/sbin/ip -6 -j address show dev "$l_if" | \ jq -r '.[0].addr_info[].local') for l_addr in ${l_addrs[@]} ; do echo $l_addr ping -c 4 -6 -I "$l_addr" ff02::1%"$l_if" done done

I discovered ipv6 static command works for a short time after pinging this ipv6 address from Keenetic web-console. It's clear that neighbor discovery has broken in 4.0.1 ip -6 neigh on local computers reports with both global 2a03:: and local fe80:: ipv6 address of my web-server, so the problem not in the server side.

Hi, I had a static ipv6 route with this setting: ipv6 static tcp PPPoE0 [mac] 443 It works nice! My server serves HTTPS website on ipv6 only address and accessible from everywhere. But after I added the same for ipv4: ip static tcp PPPoE0 443 [mac] !https ...something goes wrong, internet port scanners report my server has open 443 port on ipv4 only, not ipv6. KN-1611, OS version 4.0.1