Revision d0399410
Added by Seth Mos over 14 years ago
| etc/inc/vpn.inc | ||
|---|---|---|
| 1677 | 1677 |
/* see if this tunnel has a hostname for the remote-gateway, and if so, |
| 1678 | 1678 |
* try to resolve it now and add it to the list for filterdns */ |
| 1679 | 1679 |
if (!is_ipaddr($phase1['remote-gateway'])) {
|
| 1680 |
$rgip = resolve_retry($phase1['remote-gateway']); |
|
| 1681 |
add_hostname_to_watch($phase1['remote-gateway']); |
|
| 1680 |
if(! $g['booting']) {
|
|
| 1681 |
$rgip = resolve_retry($phase1['remote-gateway']); |
|
| 1682 |
add_hostname_to_watch($phase1['remote-gateway']); |
|
| 1683 |
} else {
|
|
| 1684 |
add_hostname_to_watch($phase1['remote-gateway']); |
|
| 1685 |
} |
|
| 1682 | 1686 |
if (!$rgip) {
|
| 1683 | 1687 |
log_error("Could not determine VPN endpoint for '{$phase1['descr']}'");
|
| 1684 | 1688 |
return false; |
Also available in: Unified diff
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.