Project

General

Profile

Actions

Bug #12764

open

VTI gateway status is pending after assigning the VTI interface

Added by Viktor Gurov about 2 years ago. Updated 30 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Gateway Monitoring
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:

Description

How to reproduce:
1) Configure IPsec VTI
2) Assign the VTI interface
3) Check the Status / Gateways page - it shows "Pending" for _VTIV4 gateway
4) Workaround: reboot the appliance or click "save" and "apply" on the System / Routing / Gateways page

Actions #1

Updated by Azamat Khakimyanov over 1 year ago

Tested on latest 23.01-DEV (built on Mon Dec 05 06:05:03 UTC 2022)

This issue hasn't been resolved yet. When new Routed IPsec tunnel is created and IPsec VTi assigned, gateway status is Pending.
Restarting dpinger fixes this issue.

Actions #2

Updated by Azamat Khakimyanov over 1 year ago

I found it on my VM which had Gateway monitoring disabled so dpinger was not active (Status/Services). So when I added Routed IPsec and assigned IPsec VTi, dpinger remained inactive. Looks like assigning IPsec VTi/adding IPsec VTi gateway is not activating dpinger.

Actions #3

Updated by Jim Pingle 12 months ago

  • Category changed from Gateways to Gateway Monitoring
Actions #4

Updated by Kris Phillips 30 days ago

I can confirm this behavior. You can also simply restart the dpinger service to "kick" it out of this state.

VTI tunnels are not the only thing that can cause this.

Releasing and renewing an interface with DHCPv6 will also cause the IPv6 gateway of that interface to go Pending until you restart dpinger.
OpenVPN servers and clients that are added as interfaces will also get into this state

Actions

Also available in: Atom PDF