Bug #6282
closed
APU, ALIX default interface assignments changed from 2.2.6 to 2.3
0%
Description
Default port assignments for PC Engines platforms prior to 2.3 were always:
ALIX: WAN=vr0, LAN=vr1
APU: WAN=re0, LAN=re1 [,OPT1=re2]
As a result of this change, if a device already in service is reset to factory defaults and then configured through the webgui, config will not work until interfaces are reassigned via the console, which had never been required previously.
File: /etc/inc/config.console.inc
Updated by Phillip Davis over 8 years ago
My Alix cases have OPT1 - WAN - LAN printed on them, left to right, which is vr2 - vr1 - vr0
My APU cases have the same labels, and the devices become OPT1 = re0, WAN = re1, LAN = re2
In 2.1.* the default config matched the above printing on the Alix cases:
https://github.com/pfsense/pfsense/blob/RELENG_2_1/conf.default/config.xml
In 2.2.* (before the change to em in the default config), it was also WAN=vr1 LAN=vr0
https://github.com/pfsense/pfsense/commit/e2accfacc5efa1eba26f330c736e07ada7c5752d
The WAN port has always been in the middle, vr1, re1.
The current code in 2.3.* function check_for_alternate_interfaces() does the same allocation of default device names to WAN and LAN:
https://github.com/pfsense/pfsense/blob/master/src/etc/inc/config.console.inc#L594
I don't see what the problem is, but am happy to be shown where the above has gone wrong.
Updated by Chris Buechler over 8 years ago
- Status changed from New to Not a Bug
not true, they're same as they always were. 1 was always the WAN. The APU never factory reset to assigned interfaces at all, as pre-2.3 it would use the default config's setting only. em in 2.2.x, vr in 2.1.x and earlier. Phil linked the 2.2 and 2.1, here's 2.0.
https://github.com/pfsense/pfsense/blob/RELENG_2_0/conf.default/config.xml
and 1.2.
https://github.com/pfsense/pfsense/blob/RELENG_1_2/conf.default/config.xml