Project

General

Profile

Actions

Bug #15589

closed

Saving an IPv6 gateway overrides the IPv4 gateway

Added by R W 5 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Routing
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
24.11
Release Notes:
Default
Affected Version:
2.7.2
Affected Architecture:

Description

When adding IPv6 to our network, we discovered that when you add a Static IPv6 address (coming from None) on the Interfaces -> WAN page and add a static IPv6 Gateway...it resets the "Default gateway IPv4" setting under System -> Routing -> Default Gateway to "Automatic" and pulls the default IPv4 route from our network and disabled all IPv4 Internet access...

Under no circumstances, should manipulating IPv6 settings affect IPv4 route settings. This bug caused a lot of unnecessary downtime for us while setting up IPv6.

Actions #1

Updated by R W 5 months ago

Forgot to add that after adding the IPv6 gateway, the Default column was suddenly blank for our IPv4 gateway with our ISP. Before we added IPv6, that gateway was specified as "Default (IPv4)". Manually specifying the default gateways for both IPv4 and IPv6 seems to be an effective workaround for this bug in our case.

Actions #2

Updated by Danilo Zrenjanin 5 months ago

Tested against:

24.03-RELEASE (amd64)
built on Mon May 13 12:17:00 UTC 2024
FreeBSD 15.0-CURRENT

Adding a static IPv6 IP and gateway on the WAN interface causes the system default gateway to revert to 'Automatic'.

The system loses the default route as a consequence.

Actions #3

Updated by Danilo Zrenjanin 5 months ago

  • Status changed from New to Confirmed
Actions #4

Updated by Christopher Cope 5 months ago

  • File status_output-sg-jfk1-2.gz added
  • File status_output-sg-jfk1-1.gz added
  • File textdump.tar.1.gz added
  • File textdump.tar.0.gz added
  • Private changed from No to Yes
Actions #5

Updated by Christopher Cope 5 months ago

  • File deleted (status_output-sg-jfk1-1.gz)
  • File deleted (status_output-sg-jfk1-2.gz)
  • File deleted (textdump.tar.0.gz)
  • File deleted (textdump.tar.1.gz)
Actions #6

Updated by Christopher Cope 5 months ago

  • File textdump.tar.1.gz added
  • File textdump.tar.0.gz added
  • File status_output-sg-jfk1-2.gz added
  • File status_output-sg-jfk1-1.gz added
Actions #7

Updated by Christopher Cope 5 months ago

  • Private changed from Yes to No
Actions #8

Updated by Christopher Cope 5 months ago

  • File deleted (textdump.tar.1.gz)
  • File deleted (textdump.tar.0.gz)
  • File deleted (status_output-sg-jfk1-2.gz)
  • File deleted (status_output-sg-jfk1-1.gz)
Actions #9

Updated by dylan mendez 4 months ago

Tested against pfSense Plus 24.08.a.20240702.0600. Added an IPv6 Static IP with IPv6 gateway on the primary WAN. It was "None" before, and the IPv4 Default Gateway remained the same (Tested with Gateway Group and Single Gateway). Unable to replicate.

Actions #10

Updated by Marcos M 4 months ago

  • Status changed from Confirmed to Feedback
  • Priority changed from High to Normal
Actions #11

Updated by R W 4 months ago

What does the feedback status indicate?

Actions #12

Updated by Marcos M 4 months ago

  • Affected Architecture deleted (i386)

Given that testing indicates this is resolved in the development snapshots, the issue is considered resolved unless it can be reproduced in recent dev snapshots.

Actions #13

Updated by Danilo Zrenjanin 4 months ago

I still can reproduce it on:

24.08-DEVELOPMENT (amd64)
built on Sat Jul 13 0:50:00 UTC 2024
FreeBSD 15.0-CURRENT

Please check.

Actions #14

Updated by Marcos M 4 months ago

  • Subject changed from Adding a Static IPv6 Gateway resets the IPv4 default gateway and removes the IPv4 default route and breaks Internet access to Saving an IPv6 gateway overrides the IPv4 gateway
  • Status changed from Feedback to Confirmed
  • Assignee set to Marcos M
  • Target version set to 2.8.0
  • Plus Target Version set to 24.08
Actions #15

Updated by Marcos M 4 months ago

  • Status changed from Confirmed to In Progress
Actions #16

Updated by Marcos M 4 months ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100
Actions #17

Updated by Danilo Zrenjanin 4 months ago

The patch fixes it.

This ticket can be resolved.

Actions #18

Updated by Jim Pingle 4 months ago

  • Status changed from Feedback to Resolved
Actions #19

Updated by Jim Pingle about 1 month ago

  • Plus Target Version changed from 24.08 to 24.11
Actions

Also available in: Atom PDF