| Summary: | Start script at connection activation / deactivation | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | tnemeth |
| Component: | Networking in general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
tnemeth
2024-05-22 11:56:04 UTC
Any progress on the idea presented here ? This is out of scope. If anyone wanted to do such a thing they can write some small script in any language to also talk to NetworkManager without needing any infrastructure on the KDE side. (In reply to David Edmundson from comment #2) > This is out of scope. If anyone wanted to do such a thing they can write > some small script in any language to also talk to NetworkManager without > needing any infrastructure on the KDE side. Thanks for your reply :) I would have imagined an entry in the KDE network configuration window that lets a user specify a script to be started at connection and/or disconnection so that no lowlevel integration would be needed. One can also use /etc/network/if-[pre|post]-[up|down].d/ but I think that solution depends too much on the distro used. Bulk transfer as requested in T17796 |