pfSense

Doing my best to describe this perceived bug in 2.3. Running on an SG-2440. I have 2 WAN interfaces, both of them DHCP assigned. One has native IPv6 (Time Warner Cable / igb2) and the other does not (Verizon FIOS / igb1). LAN is igb0. When a hotplug event occurs or a DHCP renew etc - basically anything that normally triggers a refresh of the IPs and filter rules, my logs get flooded with spam similar to:

php-fpm /rc.filter_configure_sync: The command '/sbin/route change -inet6 default fe80::217:10ff:fe88:498d' returned exit code '1',
the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable
change net default: gateway fe80::217:10ff:fe88:498d fib 0: Network is unreachable'

php-fpm /rc.newwanip: The command '/sbin/route change -inet6 default fe80::217:10ff:fe88:498d' returned exit code '1',
the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable
change net default: gateway fe80::217:10ff:fe88:498d fib 0: Network is unreachable'

I have seen these messages come through attached to rc.dyndns.update, rc.newwanip and rc.filter_configure_sync and perhaps other functions.

What I found is that the /sbin/route command that is being executed by those functions apparently needs an additional parameter- the physical interface tagged to the end of the command for it to work. E.g.

/sbin/route change -inet6 default fe80::217:10ff:fe88:498d

does not work and results in an error, but

/sbin/route change -inet6 default fe80::217:10ff:fe88:498d%igb2

works as expected. So it seems that the '%' and whatever follows it is very important and is being omitted by the default routines.

Below is a screenshot...