Project

General

Profile

Actions

Regression #14616

closed

dpinger does not start after renewing DHCP

Added by Maternal Pause over 1 year ago. Updated about 1 year ago.

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

100%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.x
Affected Architecture:
All

Description

Default install on 2.7

WAN is on VLAN 201 of vtnet0 (vtnet0.201) vtnet0 is not assigned.
LAN on vtnet1

Create a gateway group. WAN DHCP already present, add any other gateway for testing. I used LAN. WAN DCHP is Tier 1, LAN is Tier 2

Interfaces release DHCP on vtnet0.201
default route goest to vtnet1

Interface renew DHCP on vtnet0.201
gateway is created and green
no default route.

In 2.6 this issue could be mitigated by setup_gateways_monitor(); exec

In 2.7 the route won't come back until rebooting, or manually 'route del default' followed by setup_gateways_monitor(); exec.

I've been trying to figure this out for weeks. This bug really spells it all out, I just tried in a factory install to highlight the issue: https://redmine.pfsense.org/issues/14171

This is occurring in a Proxmox 8 VM with virtio interfaces. I was going to see if the issue relates to a VLAN on WAN, but I've run out of time.


Related issues

Related to Bug #12920: Gateway behavior differs when the gateway does not exist in the configurationResolvedMarcos M

Actions
Related to Regression #11570: Gateway monitoring services is not always restarted on interface events, which may prevent a WAN from recovering back to an online stateClosed

Actions
Actions

Also available in: Atom PDF