diff options
author | smos <seth.mos@dds.nl> | 2011-02-11 08:22:11 +0100 |
---|---|---|
committer | smos <seth.mos@dds.nl> | 2011-02-11 08:25:17 +0100 |
commit | d03994109f46f2b664b0dc6d933b7dadf27b9e60 (patch) | |
tree | 7ba8f0e77eab546f714c210800e95a31c36fb64a /etc/inc/vpn.inc | |
parent | 554d3bc22d54076a437bc9e71bcfd8036ebe7d38 (diff) | |
download | pfsense-d03994109f46f2b664b0dc6d933b7dadf27b9e60.zip pfsense-d03994109f46f2b664b0dc6d933b7dadf27b9e60.tar.gz |
Do not resolve the dyndns hostnames during boot. With many tunnels that have a hostname this can
cause huge boot issues if the DNS server is slow or not responding at all. By skipping those but
adding them to the DNS watchlist it should reload these later. This should allow the box to start
up and forward packets.
Diffstat (limited to 'etc/inc/vpn.inc')
-rw-r--r-- | etc/inc/vpn.inc | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/etc/inc/vpn.inc b/etc/inc/vpn.inc index caf8006..8fb2a99 100644 --- a/etc/inc/vpn.inc +++ b/etc/inc/vpn.inc @@ -1677,8 +1677,12 @@ function reload_tunnel_spd_policy($phase1, $phase2, $old_phase1, $old_phase2) { /* see if this tunnel has a hostname for the remote-gateway, and if so, * try to resolve it now and add it to the list for filterdns */ if (!is_ipaddr($phase1['remote-gateway'])) { - $rgip = resolve_retry($phase1['remote-gateway']); - add_hostname_to_watch($phase1['remote-gateway']); + if(! $g['booting']) { + $rgip = resolve_retry($phase1['remote-gateway']); + add_hostname_to_watch($phase1['remote-gateway']); + } else { + add_hostname_to_watch($phase1['remote-gateway']); + } if (!$rgip) { log_error("Could not determine VPN endpoint for '{$phase1['descr']}'"); return false; |