Project

General

Profile

Bug #8882

Interface assignments lost on reboot

Added by Jaime Geiger almost 2 years ago. Updated 11 months ago.

Status:
Incomplete
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
09/10/2018
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.3_1
Affected Architecture:
amd64

Description

I'm running pfsense in AWS and I'm trying to route out of xn1 (second interface) instead of xn0 (using it as a sync interface).
LAN is xn0, WAN is xn1 in the interface assignment page.
Both interface assignments (LAN and WAN) get set to xn0 after a reboot, which causes everything to break.

This should not happen. If I set xn0 to WAN and xn1 to LAN then it does not lose the configuration on reboot.
Is WAN required to be the first interface (xn0)?

Let me know if you need other details.

History

#1 Updated by Jim Pingle 11 months ago

  • Status changed from New to Incomplete

There is not enough information here for a valid bug report, and this site is not for support or diagnostic discussion.

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

See Reporting Issues with pfSense Software for more information.

Also available in: Atom PDF