Bug 511145

Summary: Add support in the GUI for multiple wired connection
Product: [Applications] systemsettings Reporter: federico
Component: kcm_networkmanagementAssignee: Plasma Bugs List <plasma-bugs-null>
Status: REPORTED ---    
Severity: wishlist CC: akselmo, jgrulich, kde, nate, nicolas.fella
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description federico 2025-10-26 10:33:47 UTC
Hello, I hope I'm reporting a bug to the correct component, if not, please move it where it is appropriate.

SUMMARY

STEPS TO REPRODUCE
1. Connect PC to network via cable
2. try to configure a second wired connection

OBSERVED RESULT

It is not possible to activate more than one wired connection at the same time

EXPECTED RESULT

It should be possible to activate more than one wired connection at the same time

SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.48+deb13-amd64 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION


My PC is connected to the network via cable, this is managed by KDE Plasma without issues.

I also have a reMarkable; a device that when connected to the PC, is recognized as an additional wired connection, and the device is reachable at a specific ip address.

The output of "ip a", after attaching the device is the following

----
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp57s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 80:fa:5b:69:6c:40 brd ff:ff:ff:ff:ff:ff
    altname enx80fa5b696c40
    inet 192.168.178.121/24 brd 192.168.178.255 scope global dynamic noprefixroute enp57s0f1
       valid_lft 845353sec preferred_lft 845353sec
    inet6 fe80::82fa:5bff:fe69:6c40/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp58s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ce:c4:fe:fd:52:76 brd ff:ff:ff:ff:ff:ff permaddr 3c:6a:a7:1b:d8:ca
    altname wlx3c6aa71bd8ca
6: enxf2868cb519fc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f2:86:8c:b5:19:fc brd ff:ff:ff:ff:ff:ff
----

If I connect to enxf2868cb519fc, my device, from the KDE Network settings, then the connection to enp57s0f1 is dropped.

Apparently it is not possible to activate both connections from KDE.

My current workaround is to open a console and execute "dhcpcd" as administrator, after a moment both connections are active, and also shown as such from the KDE Plasma settings.
Comment 1 Nate Graham 2025-10-27 21:17:09 UTC
> It is not possible to activate more than one wired connection at the same time
Can you describe specifically what's not working when you tried it, and how you reached this conclusion? Also CCing someone I know has this hardware.
Comment 2 federico 2025-10-28 05:35:07 UTC
> Can you describe specifically what's not working when you tried it, and how you reached this conclusion? Also CCing someone I know has this hardware.

I already wrote "If I connect to enxf2868cb519fc, my device, from the KDE Network settings, then the connection to enp57s0f1 is dropped."


what I meant is that, from the settings

 * when I activate the connection of enxf2868cb519fc, then the connection of enp57s0f1 is deactivated.
 * when I activate the connection of enp57s0f1, then the connection of  enxf2868cb519fc is deactivated.
Comment 3 Nicolas Fella 2025-10-28 17:13:20 UTC
Does the same happen when you connect on the commandline using "nmcli connection up <name>"?
Comment 4 federico 2025-10-28 20:32:38 UTC
I do not know what the correct name is,  "nmcli connection up enx6692f1a7e0e0" outputs "Error: unknown connection 'enx6692f1a7e0e0'" and "nmcli connection show" prints

____
NAME                     UUID                                  TYPE       DEVICE         
Wired connection 1       6013a7e2-8e42-4922-94b0-a6ca1f608acc  ethernet   enp57s0f1      
lo                       30d2b6a0-78e2-4228-b7a5-4468058c9ee2  loopback   lo             
____

and some saved wireless connections

If I execute nmcli without further parameters, the device appears as
____
enx6692f1a7e0e0: disconnected
        "IBM RNDIS/Ethernet Gadget"
        1 connection available
        ethernet (cdc_ether), 66:92:F1:A7:E0:E0, hw, mtu 1500
____

output of "nmcli device show"

____
GENERAL.DEVICE:                         enx6692f1a7e0e0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         66:92:F1:A7:E0:E0
GENERAL.MTU:                            1500
GENERAL.STATE:                          30 (disconnected)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on
IP4.GATEWAY:                            --
IP6.GATEWAY:                            --
____

and also "nmcli connection up 'IBM RNDIS/Ethernet Gadget'" fails with unknown connection


In case it helps, the last outputs of dmesg:


____
[   45.633851] usb 1-4: new high-speed USB device number 10 using xhci_hcd
[   45.774014] usb 1-4: New USB device found, idVendor=04b3, idProduct=4010, bcdDevice= 5.04
[   45.774036] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   45.774046] usb 1-4: Product: RNDIS/Ethernet Gadget
[   45.774053] usb 1-4: Manufacturer: Linux 5.4.70-v1.3.4-rm10x with 2184000.usb
[   45.920260] cdc_ether 1-4:1.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-4, CDC Ethernet Device, 66:92:f1:a7:e0:e0
[   45.920486] usbcore: registered new interface driver cdc_ether
[   45.956879] cdc_ether 1-4:1.0 enx6692f1a7e0e0: renamed from usb0
[   47.214062] usb 1-3.1: reset high-speed USB device number 4 using xhci_hcd
____
Comment 5 Bug Janitor Service 2025-11-12 03:47:48 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 6 federico 2025-11-12 06:18:11 UTC
Hello, what additional information should I provide?
Comment 7 Akseli Lahtinen 2025-11-12 08:35:11 UTC
setting back to reported