I've been doing some house keeping with my server recently. I didn't want to get into it while it was working well tbh. I've been using macvlan/bridging for as long as I can remember. I never had the crashing issue people reported but I did have some strange issues with network dropping out if I started to download through a VPN... might be a completely separate issue but just kind of assumed it was related. It never bothered me as it would return after 5 or 10 mins and everything would work as normal. So I had the FCP alert ignored. 

 

In the last few days I started to try address this alert. I followed the recommended settings from the docs. Firstly, as I have ubiquiti networking gear I tried to disable bridging and keep macvlan. FCP would continue to give me the alert saying that macvlan/bridging was active. I then went through each container to make sure they weren't set to bridging assuming that was causing it... still the alert from FCP. I then changed to ipvlan and turned back on bridging and still FCP persists in giving the alert. I will say that all containers have run perfectly in each setting. 

 

On a side note I have spotted in the network settings I noticed that the MAC address doesn't populate. Again this might have nothing to do with my issue. I'm on 6.12.8 but this issue has persisted since 6.12.6. Any help would be appreciated. 

server-diagnostics-20240216-1628.zip

Did you reboot after the change?

Yea I did. I just rebooted again there now just to double check and still showing the error. 

Suggest reposting in the FCP plugin support thread, it may not be detecting the config correctly.

will do. Any idea why the MAC address isnt populating on the network settings? I assume this is just a completely different issue and not related? 

Not really, that should be unrelated, you can try renaming /boot/config/network.cfg and network-rules.cfg and reboot, note that settings will go back to default DHCP.