SG-4860 Can't find interface after reboot

aholmes5

I recently upgraded from 2.4.5p1 to 21.02p1 on my SG-4860. The configuration is unable to find my netgraph bridge for the WAN connection and runs the interface assignment option where I can select ngeth0 for the WAN and everything works. I have to do this every reboot. Appreciate any help

Initializing.................... done.
Starting device manager (devd)...done.
Loading configuration......done.
ngeth0: link state changed to UP
igb2: permanently promiscuous mode enabled
igb1: permanently promiscuous mode enabled
Updating configuration...done.
Warning: Configuration references interfaces that do not exist: ngeth0

Network interface mismatch -- Running interface assignment option.

Valid interfaces are:

igb0    00:08:a2:0f:df:db (down) Intel(R) PRO/1000 PCI-Express Network Driver
igb1    00:08:a2:0f:df:dc (down) Intel(R) PRO/1000 PCI-Express Network Driver
igb2    00:08:a2:0f:df:d7 (down) Intel(R) PRO/1000 PCI-Express Network Driver
igb3    00:08:a2:0f:df:d8 (down) Intel(R) PRO/1000 PCI-Express Network Driver
igb4    00:08:a2:0f:df:d9 (down) Intel(R) PRO/1000 PCI-Express Network Driver
igb5    00:08:a2:0f:df:da (down) Intel(R) PRO/1000 PCI-Express Network Driver
ngeth0  dc:7f:a4:a4:19:10   (up) 

Do VLANs need to be set up first?
If VLANs will not be used, or only for optional interfaces, it is typical to
say no here and use the webConfigurator to configure VLANs later, if required.

Should VLANs be set up now [y|n]? igb2: link state changed to UP
igb1: link state changed to UP
igb0: link state changed to UP


If the names of the interfaces are not known, auto-detection can
be used instead. To use auto-detection, please disconnect all
interfaces before pressing 'a' to begin the process.

Enter the WAN interface name or 'a' for auto-detection 
(igb0 igb1 igb2 igb3 igb4 igb5 ngeth0 or a): ngeth0

Enter the LAN interface name or 'a' for auto-detection 
NOTE: this enables full Firewalling/NAT mode.
(igb0 igb1 igb2 igb3 igb4 igb5 a or nothing if finished): igb0

Optional interface 1 description found: OPT1
Enter the Optional 1 interface name or 'a' for auto-detection
(igb1 igb2 igb3 igb4 igb5 a or nothing if finished): igb2

Optional interface 2 description found: OPT2
Enter the Optional 2 interface name or 'a' for auto-detection
(igb1 igb3 igb4 igb5 a or nothing if finished): igb3

Optional interface 3 description found: OPT3
Enter the Optional 3 interface name or 'a' for auto-detection
(igb1 igb4 igb5 a or nothing if finished): igb4

Optional interface 4 description found: OPT4
Enter the Optional 4 interface name or 'a' for auto-detection
(igb1 igb5 a or nothing if finished): igb5

Enter the Optional 5 interface name or 'a' for auto-detection
(igb1 a or nothing if finished): 

The interfaces will be assigned as follows:

WAN  -> ngeth0
LAN  -> igb0
OPT1 -> igb2
OPT2 -> igb3
OPT3 -> igb4
OPT4 -> igb5

Do you want to proceed [y|n]? y

Writing configuration.....................................................................................................done.
One moment while the settings are reloading... done!
..Configuring looplo0: link state changed to UP
back interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring IPsec VTI interfaces...done.
Configuring WAN interface...done.
Configuring LAN interface...igb0: link state changed to DOWN
done.
bridge0: Ethernet address: 58:9c:fc:XX:XX:XX
igb0: promiscuous mode enabled
bridge0: link state changed to UP
Checking config backups consistency...done.
Setting up extended sysctls...done.
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Setting timezone...done.
2021-03-06T06:53:59.807445-06:00 router.XXXXXX.XXX php-fpm 351 - - /rc.newwanip: rc.newwanip: Info: starting on ngeth0.

2021-03-06T06:53:59.808827-06:00 router.XXXXXX.XXX php-fpm 351 - - /rc.newwanip: rc.newwanip: on (IP address: 69.XXX.XXX.XXX) (interface: WAN[wan]) (real interface: ngeth0).

stephenw10

Hmm, it must adding that slightly later in in the process.

As a temporary workaround you could try adding ngeth to the list of interfaces not to check:
https://github.com/pfsense/pfsense/blob/RELENG_2_5_0/src/etc/inc/util.inc#L2385

Steve

aholmes5

@stephenw10 Thanks, this workaround did the trick. It takes about 45s for the WAN interface to come up but it eventually does and is assigned to ngeth0.

stephenw10

Good to hear. Odd it's required. I know some others are using pfatt in 2.5/21.02.

Steve