Project

General

Profile

Actions

Bug #3132

open

Gateway events for IPv6 affect IPv4 services and vice versa

Added by Jim Pingle almost 11 years ago. Updated 14 minutes ago.

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

10%

Estimated time:
Plus Target Version:
24.08
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 versaResolvedViktor Gurov

Actions
Actions #1

Updated by Jim Thompson almost 10 years ago

  • Assignee set to Ermal Luçi
Actions #2

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 #3

Updated by Renato Botelho over 9 years ago

  • Target version changed from 2.2 to 2.3
Actions #4

Updated by Jim Thompson over 8 years ago

  • Target version changed from 2.3 to Future
Actions #5

Updated by Jim Thompson about 8 years ago

  • Assignee changed from Ermal Luçi to Anonymous

Ermal -> Steve Beaver

Actions #6

Updated by Jim Thompson about 8 years ago

  • Target version changed from Future to 2.4.0
Actions #7

Updated by Jim Pingle almost 7 years ago

  • Target version changed from 2.4.0 to 2.4.1
Actions #8

Updated by Jim Pingle over 6 years ago

  • Target version changed from 2.4.1 to 2.4.2
Actions #9

Updated by Jim Pingle over 6 years ago

  • Target version changed from 2.4.2 to 2.4.3
Actions #10

Updated by Jim Pingle over 6 years ago

  • Target version changed from 2.4.3 to 2.4.4
Actions #11

Updated by Anonymous almost 6 years ago

  • Target version changed from 2.4.4 to Future
Actions #12

Updated by Jim Pingle almost 5 years ago

  • Category changed from Gateways to Gateway Monitoring
Actions #13

Updated by Viktor Gurov almost 3 years ago

Actions #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 #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
Actions #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 #17

Updated by Viktor Gurov about 2 years ago

OpenVPN redmine issue: #13061

Actions #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 #19

Updated by Jim Pingle about 2 years ago

  • Plus Target Version changed from 22.05 to 22.09
Actions #20

Updated by Jim Pingle almost 2 years ago

  • Plus Target Version changed from 22.09 to 22.11
Actions #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 #22

Updated by Jim Pingle over 1 year ago

  • Plus Target Version changed from 22.11 to 23.01
Actions #23

Updated by Jim Pingle over 1 year ago

  • Assignee deleted (Viktor Gurov)
Actions #24

Updated by Jim Pingle over 1 year ago

  • Start date deleted (08/06/2013)
  • Plus Target Version changed from 23.01 to 23.05

Moving ahead again, too many other more important things and this requires working on each affected service separately.

Actions #25

Updated by Jim Pingle about 1 year ago

  • Plus Target Version changed from 23.05 to 23.09

Doesn't look likely that we'll have time to finish this for 23.05. Moving forward to the next release target.

Actions #26

Updated by Jim Pingle 12 months ago

  • Target version changed from 2.7.0 to CE-Next
Actions #27

Updated by Jim Pingle 9 months ago

  • Plus Target Version changed from 23.09 to 24.01
Actions #28

Updated by Jim Pingle 8 months ago

  • Plus Target Version changed from 24.01 to 24.03
Actions #29

Updated by Jim Pingle 3 months ago

  • Plus Target Version changed from 24.03 to 24.07
Actions #30

Updated by Jim Pingle 14 minutes ago

  • Plus Target Version changed from 24.07 to 24.08
Actions

Also available in: Atom PDF