Bug #3132: Gateway events for IPv6 affect IPv4 services and vice versa - pfSense - pfSense bugtracker

Custom queries

2.4.5-p1 - Resolved/Closed
2.5.0 - Resolved/Closed
2.5.1 - Resolved/Closed
2.5.2 - Resolved/Closed
2.6.0 - Resolved/Closed
2.7.0 - Resolved/Closed
2.7.1 - All Open Issues
2.7.1 - Resolved/Closed
2.7.2 - Resolved/Closed
2.8.0 - All Open Bugs
2.8.0 - All Open Features
2.8.0 - All Open Issues
2.8.0 - All Open Regressions
2.8.0 - Feedback
2.8.0 - Needs Attention
2.8.0 - New/Confirmed
2.8.0 - Pull Requests
2.8.0 - Regressions affecting 2.7.0
2.8.0 - Resolved/Closed
21.02.2/2.5.1 - Resolved/Closed
21.05 Plus - All Closed Issues
21.05.1 Plus Target - All Closed Issues
21.05.1 Target - All Closed Issues
22.01 Plus - All Closed Issues
22.01 Target - All Closed Issues
22.05 Plus - All Closed Issues
22.05 Target - All Closed Issues
23.01 Plus - All Closed Issues
23.01 Target - All Closed Issues
23.05 Plus - All Closed Issues
23.05 Target - All Closed Issues
23.05.1 Plus - All Closed Issues
23.05.1 Target - All Closed Issues
23.09 Plus - All Closed Issues
23.09 Target - All Closed Issues
23.09.1 Plus - All Closed Issues
23.09.1 Plus - All Open Issues
23.09.1 Target - All Closed Issues
23.09.1 Target - All Open Issues
24.03 Plus - All Closed Issues
24.03 Plus - All Open Issues
24.03 Plus - Feedback Issues
24.03 Plus - Needs Attention/Work
24.03 Plus - New/Confirmed/In Progress Issues
24.03 Plus - Pull Request Review
24.03 Plus - Waiting on Merge
24.03 Target - All Closed Issues
24.03 Target - All Open Issues
All Open Issues assigned to Me
All Open Pull Requests
Any Target - All Open Regressions
Any Target - Feedback Issues
CE-Next - All Closed Issues (Move to specific target)
CE-Next - All Open Issues
CE-Next - Feedback (Likely needs target changed)
New Issues by Category - Future Target
New Issues by Category - No Target
New Issues by Category - No Target+Future
No Target - All Open Issues (Base Only)
No Target - New Issues (Base Only)
No Target - New Issues (Base and Packages)
Release Notes - Plus Target Version (DO NOT EDIT)
Release Notes - Target Version (DO NOT EDIT)

Actions

Copy link

Bug #3132

open

Gateway events for IPv6 affect IPv4 services and vice versa

Added by Jim Pingle over 10 years ago. Updated about 2 months ago.

Status:

In Progress

Priority:

Normal

Assignee:

Category:

Gateway Monitoring

Target version:

CE-Next

Start date:

Due date:

% Done:

10%

Estimated time:

Plus Target Version:

24.07

Release Notes:

Default

Affected Version:

All

Affected Architecture:

Description

When a gateway of a specific type has an event, all services on the interface are restarted, rather than just those relevant to the type of gateway that had an event.

For example, if you have dual stack IPv4 and IPv6, and separate OpenVPN servers on IPv4 and IPv6, then the IPv6 gateway going down will restart both, not just the IPv6 instance. This is unnecessarily disruptive to the services that did not have an outage.

Ideally, a service should only be restarted if it is dual stack or if it's using the same IP type as the gateway that had an outage.

Related issues

Related to Bug #13061: Gateway events for IPv6 affect IPv4 OpenVPN instances and vice versa

Resolved

Viktor Gurov

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Jim Thompson almost 10 years ago

Assignee set to Ermal Luçi

Actions

Copy link

Updated by Ermal Luçi over 9 years ago

This will not be possible to be fixed in 2.2
Many things need to change for this to happen.

Actions

Copy link

Updated by Renato Botelho over 9 years ago

Target version changed from 2.2 to 2.3

Actions

Copy link

Updated by Jim Thompson over 8 years ago

Target version changed from 2.3 to Future

Actions

Copy link

Updated by Jim Thompson about 8 years ago

Assignee changed from Ermal Luçi to Anonymous

Ermal -> Steve Beaver

Actions

Copy link

Updated by Jim Thompson about 8 years ago

Target version changed from Future to 2.4.0

Actions

Copy link

Updated by Jim Pingle almost 7 years ago

Target version changed from 2.4.0 to 2.4.1

Actions

Copy link

Updated by Jim Pingle over 6 years ago

Target version changed from 2.4.1 to 2.4.2

Actions

Copy link

Updated by Jim Pingle over 6 years ago

Target version changed from 2.4.2 to 2.4.3

Actions

Copy link

#10

Updated by Jim Pingle over 6 years ago

Target version changed from 2.4.3 to 2.4.4

Actions

Copy link

#11

Updated by Anonymous almost 6 years ago

Target version changed from 2.4.4 to Future

Actions

Copy link

#12

Updated by Jim Pingle over 4 years ago

Category changed from Gateways to Gateway Monitoring

Actions

Copy link

#13

Updated by Viktor Gurov almost 3 years ago

see #11864#note-3

Actions

Copy link

#14

Updated by Viktor Gurov about 2 years ago

Assignee set to Viktor Gurov

IPsec service fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/718

it's better to have a separate commits for each service.

Actions

Copy link

#15

Updated by Viktor Gurov about 2 years ago

Status changed from New to Feedback
Target version changed from Future to 2.7.0
% Done changed from 0 to 10
Plus Target Version set to 22.05
Affected Version changed from 2.1 to All

Merged:
https://github.com/pfsense/pfsense/commit/7c97240f1a37b06ba13b31c372c8aec29d6449b7

Actions

Copy link

#16

Updated by Jim Pingle about 2 years ago

Status changed from Feedback to In Progress

I wouldn't mark the whole issue Feedback as it's only partially implemented. Would be better to make a separate Redmine for each service instead, with fixes going on each one as it happens referring back here.

Actions

Copy link

#17

Updated by Viktor Gurov about 2 years ago

OpenVPN redmine issue: #13061

Actions

Copy link

#18

Updated by Viktor Gurov about 2 years ago

Related to Bug #13061: Gateway events for IPv6 affect IPv4 OpenVPN instances and vice versa added

Actions

Copy link

#19

Updated by Jim Pingle almost 2 years ago

Plus Target Version changed from 22.05 to 22.09

Actions

Copy link

#20

Updated by Jim Pingle almost 2 years ago

Plus Target Version changed from 22.09 to 22.11

Actions

Copy link

#21

Updated by Phil Lee over 1 year ago

Possible also related to this issue I found https://redmine.pfsense.org/issues/13552 where IPv4 signpost files in the /tmp folder get deleted regardless if the network causing that call is IPv6. In addition IPv6 signpost files never get deleted on a linkdown for IPv6.

Actions

Copy link

#22