On 9/13/2025 22:39, Chris Ross wrote:
Internet6:
Destination Gateway Flags
Netif Expire
::/96 link#3 URS
lo0
default fe80::3e8a:b0ff:fe3e:4dce%vlan0 UG
vlan0
::1 link#3 UHS
lo0
::ffff:0.0.0.0/96 link#3 URS
lo0
But, as noted earlier, that gateway has no MAC, because I’m never getting the
response to the NS.
% ndp -an | grep 'fe80::3e8a:b0ff:fe3e:4dce'
fe80::3e8a:b0ff:fe3e:4dce%vlan0 (incomplete) vlan0 expired I
My dhcpcd.conf that filtered w.r.t. internal networks, and many comments
removed, are:
----------
duid
vendorclassid
option classless_static_routes
option rapid_commit
require dhcp_server_identifier
slaac private
debug
noipv6rs
noipv4
noipv4ll
allowinterfaces vlan0
interface vlan0
ipv6only
# In theory one can get an address with IA_NA, but Verion FiOS doesn't
# provide an address like that. Try ipv6rs
ipv6rs
#ia_na 0
ipv6ra_autoconf
# Request a /56, then from that allocate the following subnets as noted
# 12 14 17 A4 DD 72 0F 66
ia_pd 0/::/56 int1/18 int2/20 int3/23 int4/164 int5/221 int6/114 int7/15
int8/102
-----------
“intN” replacements and different IPv6 subnets, but the above is what I have in
effect.
Thanks. Apologies to anyone who isn’t deeply involved for the long message.
:-)
- Chris
That gateway isn't by any chance running out of RAM such as on nanobsd (e.g. /var is volatile) is it?
If so the duid is non-fixed and some ISPs will have a hiss-fit in that they "marry" the MAC on your end to the MAC on the ONT along with the duid and use that internally. If the duid changes but the MAC does not it will not arp and you're hosed as their end has no internal map back to your gateway thus you don't get the advertisements (and in some cases no delegation either!) and it doesn't come up.
I also have "noarp" in my config which otherwise made the ISP's gear upset. In addition I have made sure the duid doesn't change (try "duid ll" which will generate one that won't so long as the interface it is applied to doesn't) and/or move /var/db/dhcpcd to something that can be sync'd (e.g. symlink it to /usr/local/etc/db/dhcpcd and then after the first boot sync that) so the duid file gets restored on a restart.
I ran into this with my fiber here; the former cable company did not care if all this was volatile on a restart however the fiber firm did it was a load of fun to get someone on the phone who actually could figure out *why* their system got mad and wouldn't reconnect. In my case their end would return an IPv4 address and function but would not come back up on IPv6 unless they cleared their internal tables manually.
My gateway is running 14.3:FreeBSD 14.3-STABLE #0 stable/14-n271456-70068b3030f9-dirty: Mon May 12 18:53:58 EDT 2025 k...@newfs.denninger.net:/work/OBJ/Crochet-work-AMD14/usr/src.14-STABLE/amd64.amd64/sys/GENERIC
The "dirty" is because I also patched rtadvd so it honors the vltime and pltime parameters on interfaces (which it does NOT "as shipped"; I have reported this as a bug with a brief patch that fixes it, but it hasn't been picked up or merged.)
-- Karl Denninger k...@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/
smime.p7s
Description: S/MIME Cryptographic Signature
