August 1, 20232 yr Actually 4 network interfaces working, but now it only display eth0. Diagnostic files attached for reference. aio-diagnostics-20230801-1534.zip
August 1, 20232 yr Author 8 hours ago, JorgeB said: Try renaming /boot/config/network.cfg and reboot. regenerating network.cfg did help, but when I finish reconfiguring network interfaces, the interfaces disappear again except eth0. It looks like kind of bug. Diagnostic file was updated as attached. aio-diagnostics-20230802-0036.zip
August 1, 20232 yr Author and I rename network.cfg and reconfigure network for several times, all ended with same issue.
August 1, 20232 yr Community Expert Does it disappear as soon as you make a change? If it's a bug it may be a specific setting that it's making it go away, see if you can find it.
August 3, 20232 yr Author Solution On 8/2/2023 at 12:53 AM, JorgeB said: Does it disappear as soon as you make a change? If it's a bug it may be a specific setting that it's making it go away, see if you can find it. after trouble shooting, it is confirmed this issue is due to same IPv6 subnet in same ethernet interfaces (eth0, eth1, eth2) and docker bridge turned on. When finish the network setting, same IPv6 subnet in different interfaces just fine, no disorder happen. Then once I turned docker on with bridge enabled in these interfaces. The network setting page just run into chaos. So the final solution is reconfigure the network according to JorgeB's suggestion and avoid same IPv6 subnet in different interfaces if they are used for docker bridge network. Quote Try renaming /boot/config/network.cfg and reboot. Edited August 3, 20232 yr by Albert Wu
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.