Maurice Walker

I did some tests with 23.1.a_20 and it (mostly) works! Biggest issue I've encountered so far: rtsold seems to invoke `rtsold_resolvconf.sh` every time it encounters an RA with RDNSS /...

Alright, so I'll make no further changes to rtsold_resolvconf.sh for the time being and look forward to rc.newwanip(v6) improvements. :-) Interesting read on the mailing list. I kind of get...

More experiments to check for side effects with existing DHCPv6 setups. The upstream router in these tests advertises DNS servers and search domains via DHCPv6 and RAs, but different ones....

There are _nameserverv6 and _searchdomainv6 files from DHCPv6 and SLAAC: ``` # ls -l /tmp/hn1* -rw-r----- 1 root wheel 42 Aug 22 22:50 /tmp/hn1:slaac_nameserverv6 -rw-r----- 1 root wheel 25 Aug...

Okay, I've (kind of) found the root cause of the resolv.conf issue. Something doesn't like that the domains in the searchdomainv6 file end with a `.` (unlike in slaac_searchdomainv6).

@fichtner, I applied `opnsense-patch d9609ec 6043b5b` on top of 23.1.a_59 on a VM with a SLAAC WAN interface. When the first (solicited) RA is received, the interface autoconfigures its address...

@fichtner You nailed it! It works when setting `net.inet6.ip6.dad_count=0`. How to solve this properly? Might be best to wait until DAD is completed.

@fichtner I don't think #5946 is caused by a tentative interface address. The main issue there is that the _routerv6 file doesn't get created, which should happen before rc.newwanipv6 is...

@fichtner Ah, interesting. Assume a static RetransTimer of 1000 ms, use the actually configured number of Neighbor Solicitations and add 1 second just to make sure. Seems pragmatic. I'll test...

@fichtner You're right, I forgot about `opnsense-code`. Now on 23.1.a_101 and 7627802 did the trick! We're getting there. :-) One more slight issue: `/usr/local/etc/rc.newwanipv6: The command '/sbin/route add -host -'inet6'...