Bug #12072
closed
FQDN L2TP server address is only resolved at boot
100%
Description
Hello!
Im using "russian vpn" scheme to connect with ISP - WAN interface with DHCP (actually internal ISP network) + L2TP interface to ISP server (as real WAN). If im using FQDN as L2TP server name - it couldn't be resolved during boot up, so i have start this interface manually. Even if i put static DNS entry for this server name to DNS resolver - its still couldn`t be resolver during boot. If i use ip as server address - everything is ok and L2TP interface going up automatically during boot.
Could someone fix this problem, because ISP balancing load between L2tp servers and returns different ip for same FQDN..
Updated by Viktor Gurov over 3 years ago
we need to restart the L2TP/PPTP interfaces that use WAN as parent on /etc/rc.newwanip event
like GRE/GIF: https://github.com/pfsense/pfsense/blob/master/src/etc/rc.newwanip#L125-L126
Updated by Viktor Gurov over 3 years ago
Updated by Jim Pingle over 3 years ago
- Subject changed from PFSense 2.4.5-p1 L2TP server ip resolve from FQDN during boot issue to FQDN L2TP server address is only resolved at boot
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
- Target version set to 2.6.0
- Plus Target Version set to 21.09
Updated by Viktor Gurov over 3 years ago
works as expected as reported on the forum:
https://forum.netgate.com/topic/164614/pfsense-2-4-5-p1-l2tp-server-ip-resolve-from-fqdn-during-boot-issue/5
Updated by Renato Botelho over 3 years ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
Updated by Viktor Gurov over 3 years ago
- % Done changed from 0 to 100
Applied in changeset ce04d03ff8c74e50585522dcd7b0deed46138be9.
Updated by Jim Pingle about 3 years ago
- Plus Target Version changed from 21.09 to 22.01
Updated by Jim Pingle almost 3 years ago
- Status changed from Feedback to Resolved