Dnswatch seems has problem and killed racoon (snapshot Fri Jan 21 19:22:57 EST)
-
I've used ddns for remote site VPN. dnswatch seems has problem and killed racoon.
There is an observation that it's always beginning at the 3rd one to the end to have the same IP address resolved. And this IP changes each time I tried to restart racoon but the IP addresses are one of my remote sites.
One factor, is it because I resolve domain name abcd.com from my remote site gw20-abcd.com via VPN? But this didn't happen before.
I disabled the VPN of gw20-abcd.com (which is the remote site to resolve domain abcd.com) but still giving me the error and killed racoon.
-Raylund
Here is the logs:
Jan 22 19:49:14 pfsense php: /status_services.php: Forcefully reloading IPsec racoon daemon
Jan 22 19:49:17 pfsense php: /status_services.php: Error: Invalid certificate info for
Jan 22 19:49:19 pfsense dnswatch: hostname gw0-abcd.com ip changed to 96.48.224.184, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw10-abcd.com ip changed to 24.87.64.70, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw12-abcd.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw16-wxyz.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw21-abcd.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw20-abcd.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw22-abcd.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw55-abcd.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:19 pfsense dnswatch: hostname gw50-abcd.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:20 pfsense dnswatch: hostname gw51-abcd.com ip changed to 216.145.101.42, reloading ipsec tunnel.
Jan 22 19:49:20 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:21 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:21 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:22 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:22 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:22 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:23 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:23 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:23 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:23 pfsense php: : IPSEC: One or more IPSEC tunnel endpoints has changed IP. Refreshing.
Jan 22 19:49:26 pfsense check_reload_status: reloading filter
Jan 22 19:49:26 pfsense check_reload_status: reloading filter
Jan 22 19:49:27 pfsense check_reload_status: reloading filter
Jan 22 19:49:27 pfsense check_reload_status: reloading filter
Jan 22 19:49:27 pfsense check_reload_status: reloading filter
Jan 22 19:49:27 pfsense check_reload_status: reloading filter
Jan 22 19:49:27 pfsense check_reload_status: reloading filter
Jan 22 19:49:27 pfsense check_reload_status: reloading filter
Jan 22 19:49:28 pfsense check_reload_status: reloading filter
Jan 22 19:49:29 pfsense check_reload_status: reloading filter -
Can you try this on a more current snapshot? dnswatch was rebuilt at some point but I don't recall if that snapshot would have included the updated binary.
-
Please try tomorrows snapshots this issue is fixed there.
-
Thanks ermal. -Raylund