WAN IPs not being cached causing unnecessary "rc.start_packages: Restarting/Starting all packages"
First bug report so please excuse administrative mistakes.
Affected version is actually 2.1.3 (maybe others)
There are actually two bugs, causing the /var/db/wan_cacheip and /var/db/wan_cacheipv6 files to not be generated.
The first is a typo in /etc/rc.newwanip:
[2.1.3-RELEASE][root@pfsense]/etc: diff rc.newwanip.pfsense rc.newwanip 191c191 < if (is_ipaddr($curnwanip)) --- > if (is_ipaddr($curwanip))
and the second is an invalid initial IPv6 IP address causing the is_ipaddrv6 function to return false:
[2.1.3-RELEASE][root@pfsense]/etc: diff rc.newwanipv6.pfsense rc.newwanipv6 114c114 < $oldipv6 = ""; --- > $oldipv6 = "::";
Note that the above IPv6 'fix' causes the following in /var/log/system.log:
May 20 22:21:20 pfsense php: rc.newwanipv6: The command '/sbin/ifconfig pppoe0 inet6 :: delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
Fixes #3669 Handle properly recording of the ipv6 interface new ip and do not issues commands that cannot succeed.
#2 Updated by jeroen van breedam over 4 years ago
Would it be possible to set target version to 2.1.x ?
I've been struggling with the same thing (altough i thought it was a new feature) and had to set the gw monitoring to 3000ms to avoid a frequent restart of openvpn (i max out the upload speed of my vpn's a lot).
It would be nice to see a quick 2.1.4 release.
If that is impossible, a forum post with a link to an easy to implement patch by using the "system patches" package would also be a great help
#3 Updated by Renato Botelho over 4 years ago
You can always use gitsync to sync your installation with latest changes made on branch, in this case RELENG_2_1.
#6 Updated by David Burns almost 4 years ago
Whilst this ticket has been marked resolved, the second part of the fix relating to /etc/rc.newwanipv6 has never been applied to 2.1 or 2.2.
The supplied fix to rc.newwanipv6 certainly seems to work ... but is there another issue identified by Ermal (or others) which has prevented the fix from being integrated?
Would be great if this fix could make it into 2.2.1