KNetworkManager/zh-cn: Difference between revisions

Revision as of 06:32, 23 November 2012

Other languages:

KNetworkManager 可以处理开放和加密的网络连接。

KNetworkManager 是 NetworkManager 的 KDE 客户端。KNetworkManager通过 DBus 与 NetworkManager 进行通讯。

一个典型使用情况是连接到知道密码的无线网络。用户设置一个连接，KNetworkManager 将会保存设置，设置包括名称(ESSID) 和连接密码。KNetworkManager将这些信息大包进DBus请求。Network Manager 后端会进行底层的操作，调用需要的程序(例如将 ESSID 和密码发给 wpa-supplicant)然后用合适的设置启动网络设备。

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.

@@ Line 7: / Line 7: @@
 '''KNetworkManager''' 是 NetworkManager 的 KDE 客户端。'''KNetworkManager'''通过 DBus 与 NetworkManager 进行通讯。
-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.
+一个典型使用情况是连接到知道密码的无线网络。用户设置一个连接，'''KNetworkManager''' 将会保存设置，设置包括名称(''ESSID'') 和连接密码。'''KNetworkManager'''将这些信息大包进DBus请求。Network Manager 后端会进行底层的操作，调用需要的程序(例如将 ESSID 和密码发给 '''wpa-supplicant''')然后用合适的设置启动网络设备。
 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.