Project

General

Profile

Actions

Bug #12072

open

FQDN L2TP server address is only resolved at boot

Added by Alex BJ about 1 month ago. Updated about 1 month ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
L2TP
Target version:
Start date:
06/23/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
21.09
Release Notes:
Default
Affected Version:
2.4.5-p1
Affected Architecture:
amd64

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..

Actions #1

Updated by Viktor Gurov about 1 month 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

Actions #3

Updated by Jim Pingle about 1 month 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
Actions #5

Updated by Renato Botelho about 1 month ago

  • Status changed from Pull Request Review to Feedback

PR has been merged. Thanks!

Actions #6

Updated by Viktor Gurov about 1 month ago

  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF