Project

General

Profile

Actions

Bug #13974

closed

No network connectivity after 23.01 upgrade, 23.01 fresh image installation and configuration restoration

Added by YP Lo about 1 year ago. Updated about 1 year ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Backup / Restore
Target version:
-
Start date:
Due date:
% Done:

0%

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

Description

When PFSense is upgraded / re-imaged to 23.01 and configuration file restored, some interfaces that are un-assigned or not availabe (i.e. OpenVPN/WG due to missing packages on image installation) seems to be automatically assigned to the first network port (i.e. ix0). This resulted in multiple interfaces assigned to the same network port and may be causing network connectivity issues (i.e. pfSense-upgrade not able to establish connection, thus preventing further restoration from taking place).

The interface should be disabled if the corresponding network port is not available, and not assigned to the first network port of the system.

Actions #1

Updated by Jim Pingle about 1 year ago

  • Project changed from pfSense Plus to pfSense
  • Category changed from Backup / Restore to Backup / Restore
  • Status changed from New to Rejected
  • Affected Plus Version deleted (23.01)

There isn't enough information here to say there is a bug. Interfaces such as OpenVPN get dummy entries that are allowed to bypass assignment tests and don't behave the way you describe. We have seen some reports of similar issues that were the result of a misconfiguration (such as incorrectly assigning the tailscale interface).

This site is not for support or diagnostic discussion to dig into your configuration to find out why that might have happened in your specific case, however.

For assistance in solving problems, please post on the Netgate Forum .

See Reporting Issues with pfSense Software for more information.

Actions

Also available in: Atom PDF