Bug #12196
closed
IPsec settings fail to apply when a remote gateway is set to an FQDN and there are no DNS servers available
Added by Viktor Gurov over 4 years ago.
Updated over 4 years ago.
Plus Target Version:
22.01
Description
How to reproduce:
1) Disable DNS servers or configure non-existent DNS servers on the System / General Setup page;
2) Configure IPsec PH1 with example.com remote gateway;
3) Press apply.
Result:
504 Gateway Time-out error
resolve_retry() - setting `$retries = 10` can improve FQDN resolution time:
# trying to resolve "example.com" when DNS server is no available:
# time php -f resolve50retries.php
0.176u 0.047s 0:18.14 1.1% 4588+402k 91+0io 0pf+0w
# time php -f resolve10retries.php
0.136u 0.045s 0:03.36 5.0% 3968+364k 51+0io 0pf+0w
- Related to Bug #12026: Applying IPsec settings for many tunnels is slow or times out added
- Status changed from New to Pull Request Review
- Target version set to 2.6.0
- Plus Target Version set to 21.09
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:5ed5f14d7c4e53c3f713c0842553916c1d145542.
- Assignee set to Viktor Gurov
- Subject changed from Gateway Timeout error if DNS server is not available and remote gateway = FQDN to IPsec settings fail to apply when a remote gateway is set to an FQDN and there are no DNS servers available
Updating subject for release notes.
- Status changed from Feedback to Resolved
Tested on the:
2.6.0-DEVELOPMENT (amd64)
built on Sat Sep 11 01:10:13 EDT 2021
FreeBSD 12.2-STABLE
It applies the changes correctly with an FQDN as a remote gateway even without a working DNS setup on the firewall.
Ticket Resolved.
- Plus Target Version changed from 21.09 to 22.01
Also available in: Atom
PDF