Re: IPv6 networking stops on FreeBSD some time after boot
Date: Sat, 26 Sep 2026 12:45:32 UTC
On Wed, 23 Sep 2026, Farooq Karimi Zadeh wrote: > working some time after boot(10-20 minutes). That's the usual timeout window. Had this once on Google WiFi when we were their for the GSoC meeting; took them ages with their vendor to figure it out. FreeBSD notices this as we do not update neighbour "alive" timeouts with successful packets (can be expensive). > The IPv6 gateway from the provider is fe80::1. This is "netstat -rn6": .. > ifconfig_vtnet0_ipv6="inet6Â XXXX:XXX:X:XXX::1/64" > ipv6_defaultrouter="fe80::1%vtnet0" Given this is all static makes it easier. > "ping6 example.com" works for few minutes after a boot. > > > Any hint appreciated. And let me know if more information is needed. You can try a simple thing: run a ping6 -n fe80::1%vtnet0 and a ping6 -n <second hop IPv6 address> which you can get from a traceroute6 -n -f 2 -m 2 www.freebsd.org (or if that is all * try 3 instead of 2 and so on until something replies) along with whatever you want. Run it after boot in a tmux or something in parallel and see what happens. "example.com" is good as a 3rd target but not really a good target to test connectivity in general; you want local things to see if your connectivity works or if you are debugging the internet. Once things start failing see which works which doesn't and let us know. If you want run a tcpdump -ln -s0 -e -vvv -i vtnet0 -w /tmp/icmp6.pcap icmp6 along so you can load it in wireshar later, filter out the echo packets and see at the timestamp when things started to fail what other possible local ICMP6 traffic happened (just in case it is a local problem). /bz -- For there shall arise false Christs, and false prophets, and shall shew great signs and wonders; insomuch that, if it were possible, they shall deceive the very elect. Behold, I have told you before. [Mat. 24:24-25]