Bug #4866: L2TP server are restarted after adding/modifying L2TP users (mpd.secret) - pfSense - pfSense bugtracker

Actions

Copy link

Bug #4866

closed

L2TP server are restarted after adding/modifying L2TP users (mpd.secret)

Added by Taras Savchuk over 9 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

L2TP

Target version:

2.4.5-p1

Start date:

07/22/2015

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

All

Affected Architecture:

All

Description

Full daemon restart is useless since mpd reads mpd.secret on the fly (as I can uderstand from mpd4's code). One problem with this restart is that Quagga OSPF don't like to see mpd deleting ang creating L2TP interfaces. After mpd restart in Quagga status I can see both l2tpXXX anf ngXX interfaces. Quagga restart solves problem.

Quagga OSPF status after mpd restart (both l2tpXXX ang ngXXX interfaces):

l2tp0 is down
  ifindex 0, MTU 1500 bytes, BW 0 Kbit <POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST>
  OSPF not enabled on this interface

...

l2tp9 is down
  ifindex 0, MTU 1500 bytes, BW 0 Kbit <POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST>
  OSPF not enabled on this interface
...
ng0 is up
  ifindex 9, MTU 1500 bytes, BW 0 Kbit <UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST>
  Internet Address 192.168.221.1/32, Peer 192.168.221.128, Area 0.0.0.0
  MTU mismatch detection:enabled
  Router ID 10.10.15.250, Network Type BROADCAST, Cost: 10
  Transmit Delay is 1 sec, State Waiting, Priority 1
  No designated router on this network
  No backup designated router on this network
  Multicast group memberships: OSPFAllRouters
  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
    Hello due in 6.903s
  Neighbor Count is 0, Adjacent neighbor count is 0

...

ng9 is down
  ifindex 18, MTU 1500 bytes, BW 0 Kbit <POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST>
  OSPF not enabled on this interface