KNetworkManager: Difference between revisions
(Added visuals and links to project pages and screenshots) |
Thiagosueto (talk | contribs) (Propose deletion) |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{Proposed_deletion|reason=Unmaintained.}} | ||
{| | <languages /> | ||
|[[Image:Knetworkmanager2.png|thumb|265px]]|| '''Let KNetworkManager handle your open and encrypted connections.''' | |||
{|class="tablecenter vertical-centered" | |||
|[[Image:Knetworkmanager2.png|thumb|265px]]||<translate> <!--T:1--> | |||
'''Let KNetworkManager handle your open and encrypted connections.'''</translate> | |||
|} | |} | ||
KNetworkManager is a KDE client for the back end | <translate> | ||
<!--T:2--> | |||
'''KNetworkManager''' is a KDE client for the back end NetworkManager software. '''KNetworkManager''' communicates with NetworkManager via DBus (a type of message passing software). | |||
<!--T:3--> | |||
One typical usage is to connect to a wireless network with credentials known to the user. The user will setup a connection and '''KNetworkManager''' will store the settings wherever the user's configurations are stored. The configuration will include things like the name (''ESSID'') and passphrase used to associate with a particular wireless network. '''KNetworkManager''' can then use this information by packaging it into a DBus request to connect to a particular network. The Network Manager back end then does the low level operations required to actually setup the support software (e.g. pushing ESSID and key to '''wpa-supplicant''') and bring up the network device with the appropriate settings. | |||
<!--T:4--> | |||
Along with the advantage of allowing normal users to control the configuration the network it also allows one consistent interface for network configuration on KDE, and other desktops (e.g. GNOME) can use the network manager back end without each having to implement the logic to handle network configuration. | |||
<!--T:5--> | |||
:[http://old-en.opensuse.org/Projects/KNetworkManager The Project Page] gives an overview of features, some screenshots, and links to packages for several distros. | |||
<!--T:6--> | |||
:More [http://old-en.opensuse.org/Projects/KNetworkManager_Screenshots screenshots] show its use on different desktop environments. | |||
<!--T:7--> | |||
[[Category:Internet]] | |||
</translate> | |||
Latest revision as of 19:42, 25 February 2024
Proposed for Deletion
Please use the discussion section of this page to voice your opinion on this.Unmaintained.
 |
Let KNetworkManager handle your open and encrypted connections. |
KNetworkManager is a KDE client for the back end NetworkManager software. KNetworkManager communicates with NetworkManager via DBus (a type of message passing software).
One typical usage is to connect to a wireless network with credentials known to the user. The user will setup a connection and KNetworkManager will store the settings wherever the user's configurations are stored. The configuration will include things like the name (ESSID) and passphrase used to associate with a particular wireless network. KNetworkManager can then use this information by packaging it into a DBus request to connect to a particular network. The Network Manager back end then does the low level operations required to actually setup the support software (e.g. pushing ESSID and key to wpa-supplicant) and bring up the network device with the appropriate settings.
Along with the advantage of allowing normal users to control the configuration the network it also allows one consistent interface for network configuration on KDE, and other desktops (e.g. GNOME) can use the network manager back end without each having to implement the logic to handle network configuration.
- The Project Page gives an overview of features, some screenshots, and links to packages for several distros.
- More screenshots show its use on different desktop environments.