Unbound ipv6 problems anyone?

[bimmerdriver]

I did a couple more packet captures with wireshark, two reboots from the 2.3.4 system and two from the 2.4 beta system.

The 2.3.4 system took 2.34 seconds and 1.36 seconds. The 2.4 beta system took 4.84 seconds both times.

Both systems have identical WAN ipv6 settings. It's interesting to notice that pfsense 2.3.4 appears to send the RS after sending the second dhcp request before the reply is received, rather than apparently waiting for the reply as pfsense 2.4 beta does. I have never noticed this behaviour before. It could be a coincidence.

You can see that the link-local address of the edge router is the same in both cases, so any difference is from pfsense, not the edge router.


[Guest]

When I get some time to play I'll put something together for you. Don't know when that will be as real work is exceptionally busy at the moment.

[Guest]

I've issued a PR for this.

[bimmerdriver]

I installed the PR and I'm happy to confirm that it works perfectly.

So you can see it in action, here are some log messages:

Aug 11 10:23:32	php-cgi		rc.bootup: sync unbound done.
Aug 11 10:23:31	php-cgi		rc.bootup: dhcp6 init complete. Continuing
Aug 11 10:23:30	php-fpm	291	/rc.newwanipv6: Removing static route for monitor fe80::ea4:2ff:fe29:5001 and adding a new route through fe80::ea4:2ff:fe29:5001%hn1
Aug 11 10:23:30	php-fpm	291	/rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::ea4:2ff:fe29:5001%hn1
Aug 11 10:23:30	php-fpm	291	/rc.newwanipv6: ROUTING: setting default route to *.*.116.1
Aug 11 10:23:30	php-fpm	291	/rc.newwanipv6: rc.newwanipv6: on (IP address: fe80::215:5dff:fe5c:e21d%hn1) (interface: wan) (real interface: hn1).
Aug 11 10:23:30	php-fpm	291	/rc.newwanipv6: rc.newwanipv6: Info: starting on hn1.
Aug 11 10:23:30	php-cgi		rc.bootup: Unbound start waiting on dhcp6c.
Aug 11 10:23:29	rtsold		Received RA specifying route fe80::ea4:2ff:fe29:5001 for interface wan(hn1)
Aug 11 10:23:29	php-cgi		rc.bootup: Unbound start waiting on dhcp6c.
Aug 11 10:23:28	php-cgi		rc.bootup: Unbound start waiting on dhcp6c.
Aug 11 10:23:27	php-cgi		rc.bootup: Unbound start waiting on dhcp6c.
Aug 11 10:23:33	php-cgi		rc.bootup: Unbound start waiting on dhcp6c.
Aug 11 10:23:32	php-cgi		rc.bootup: Unbound start waiting on dhcp6c.
Aug 11 10:23:31	php-cgi		rc.bootup: Unbound start waiting on dhcp6c.
Aug 11 10:23:31	php-cgi		rc.bootup: ROUTING: setting default route to 154.20.116.1
Aug 11 10:23:30	php-cgi		rc.bootup: Resyncing OpenVPN instances.
Aug 11 10:23:30	kernel		hn0: link state changed to UP
Aug 11 10:23:30	check_reload_status		Linkup starting hn0
Aug 11 10:23:30	php-cgi		rc.bootup: Starting dhcp6 client for interface wan hn1 in DHCP6 without RA mode
Aug 11 10:23:28	php-fpm	291	/rc.newwanip: rc.newwanip: on (IP address: *.*.118.8) (interface: WAN[wan]) (real interface: hn1).
Aug 11 10:23:28	php-fpm	291	/rc.newwanip: rc.newwanip: Info: starting on hn1.
Aug 11 10:23:27	php-cgi		rc.bootup: Accept router advertisements on interface hn1
Aug 11 10:23:27	php-cgi		rc.bootup: calling interface_dhcpv6_configure.
Aug 11 10:23:27	check_reload_status		rc.newwanip starting hn1

Thank you very much for fixing this problem.

[Guest]

Apart from the weird time stamps.  8)

[bimmerdriver]

@marjohn56:

Apart from the weird time stamps.  8)

I never noticed that. I guess that's a bug in the log.

[Guest]

@marjohn56:

Apart from the weird time stamps.  8)

You've cracked time travel as well  :-)

[chrcoluk]

Just to be sure I did test this and seems to not break anything on uk sky connections.  So good from my end.

[w0w]

bimmerdriver, is it possible that you have trouble with hardware clock?  ???

[bimmerdriver]

@nivek1612:

@marjohn56:

Apart from the weird time stamps.  8)

You've cracked time travel as well  :-)

I rebooted and took another look at the logs. I guess the time travel was a once-only event. Strange.

[w0w]

Maybe NTP daemon syncs sometimes in the same time unbound starts?

[Guest]

I think the time traveller idea is more fun. 8)