| Summary: | Show all interfaces that NetworkManager is aware of | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Diego Ercolani <diego.ercolani> |
| Component: | Networks widget | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | fabian, nate |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Diego Ercolani
2024-12-18 09:54:30 UTC
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
Can you clarify what the issue is in plasma-nm code? Hello, it passed some time since I firstly reported the "issue", the problem is that in the nm-applet isn't possibile to control all the NetworkManager parameters (obviously I'm talking about the version is distributed with openSuSE -that's why I reported them-): eg. in the applet version of networkmanager client I cannot control the slave devices (it doesn't appear any device br0-interface, br9-interface, vlan9) nmcli connection modify Bridge0 connection.autoconnect-slaves 1 nmcli connection modify Bridge9 connection.autoconnect-slaves 1 So the problem is that you have to use the command line to do certain tasks? Don't mind, yes, some configurations are reachable with the interface others only with direct interaction with NetworkManager, the point is that with the interface the user should at least be aware of all the interfaces implemented by Networkmanager, to be aware of them. So we are talking more about better usability than necessity. But I have no responsibility in the design of the applications, I just try to give my contribution. Bulk transfer as requested in T17796 |