Actions
Bug #11430
openPHP console spam after Assigning Interfaces
Start date:
02/17/2021
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:
amd64
Description
After (re)assigning the interfaces at the console following a mismatch the WAN interface triggers a number or scripts. Some of which now send output to the console:
Network interface mismatch -- Running interface assignment option. alc0: link state changed to DOWN mlx4_en: mlxen0: Fail to add unicast address mlx4_en: mlxen1: Fail to add unicast address Valid interfaces are: alc0 6c:f0:49:cb:40:7a (down) Atheros AR8131 PCIe Gigabit Ethernet mlxen0 00:02:c9:09:89:c0 (down) mlxen1 00:02:c9:09:89:c1 (down) 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]? alc0: 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 (alc0 mlxen0 mlxen1 or a): Enter the LAN interface name or 'a' for auto-detection NOTE: this enables full Firewalling/NAT mode. (mlxen0 mlxen1 a or nothing if finished): The interfaces will be assigned as follows: WAN -> alc0 Do you want to proceed [y|n]? Writing configuration...done. One moment while the settings are reloading... done! ..Configuring loopback interface... lo0: link state changed to UP 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...2021-02-17T13:23:03.854355+00:00 php-fpm 343 - - /rc.newwanip: rc.newwanip: Info: starting on alc0. 2021-02-17T13:23:03.854808+00:00 php-fpm 343 - - /rc.newwanip: rc.newwanip: on (IP address: 172.21.16.238) (interface: WAN[wan]) (real interface: alc0). 2021-02-17T13:23:03.876487+00:00 php-fpm 343 - - /rc.newwanip: Accept router advertisements on interface alc0 2021-02-17T13:23:03.881110+00:00 php-fpm 343 - - /rc.newwanip: Starting rtsold process done. Checking config backups consistency...done. Setting up extended sysctls...done. Setting timezone...done. Configuring loopback interface...done. Starting syslog...done. Starting Secure Shell Services...done. Setting up interfaces microcode...done. Starting PC/SC Smart Card Services...done. Configuring loopback 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.
That did not happen in 2.4.X. It doesn't appear to cause a problem but is ugly/confusing.
In addition you can see it loops back around configuring all the inetrface types twice for some reason.
Tested in 2.5-rel and 21.02-rel. This also affected earlier RC snapshots.
Updated by Viktor Gurov about 3 years ago
mute_kernel_msg()
/unmute_kernel_msg()
can be used to avoid these messages
Actions