https://bugs.kde.org/show_bug.cgi?id=497644
--- Comment #1 from Diego Ercolani <diego.ercol...@gmail.com> ---
I resolved partially. There is a parameter for the master interface:
connection.autoconnect-slaves that if it's set to "1" brigs up slave interfaces
before the Master interface.
The problem is that in the applet gui (plasma6) all these parameters aren't
visible so it is supposed that all the configuration will be processed by the
applet. (plasma6-nm-6.1.2-1.1.x86_64)
Reconnecting Bridge Interfaces:
The issue with the bridges not reconnecting properly is likely due to the slave
interfaces being brought down when the master is disconnected and not being
brought up automatically. This can be resolved by ensuring that the slave
interfaces are configured to autoconnect and are properly linked to their
master interfaces.
Ensure that connection.autoconnect-slaves is set to 1 for your bridge
interfaces:
nmcli connection modify Bridge0 connection.autoconnect-slaves 1
nmcli connection modify Bridge9 connection.autoconnect-slaves 1
Additionally, you can use dispatcher scripts to manage the state of your
interfaces. NetworkManager dispatcher scripts are executed in response to
network events such as interfaces being brought up or down. Here’s an example
of a dispatcher script that ensures the slave interfaces are brought up when
their master bridge interface is activated:
Create a script in /etc/NetworkManager/dispatcher.d/:
sh
sudo nano /etc/NetworkManager/dispatcher.d/bridge-up
Add the following content to the script:
#!/bin/bash
interface=$1
action=$2
if [[ "$interface" == "br0" && "$action" == "up" ]]; then
nmcli connection up br0-interface
elif [[ "$interface" == "br9" && "$action" == "up" ]]; then
nmcli connection up br9-interface
fi
Make the script executable:
sudo chmod +x /etc/NetworkManager/dispatcher.d/bridge-up
--
You are receiving this mail because:
You are watching all bug changes.
