nm applet disable

http://support.qacafe.com/knowledge-base/how-do-i-prevent-network-manager-from-controlling-an-interface/

Network Manager is a service for Linux which manages various networking interfaces, including physical such as Ethernet and wireless, and virtual such as VPN and other tunnels. Network Manager can be configured to control some or all of a system’s interfaces.

While Network Manager is an excellent service for managing the daily requirements of a user’s computer, its effects are typically non-optimal for a testing environment. Because of the extra variables it introduces into the state of a test machine’s networking configuration, it can be especially difficult to integrate with CDRouter, which also controls network interfaces. Due to this conflict, the start procedure will generate an error if Network Manager is controlling any interfaces used for testing. In this case you have three options:

  • Tell Network Manager to stop controlling the interfaces used by the test configuration
  • Stop the Network Manager process
  • Remove the Network Manager software from the system

Before you begin, please be aware that your LAN interface may require manual configuration should you decide to remove Network Manager from your system. If you do not have Internet access from another system, you may wish to learn how this process works before completing the removal process. This article discusses how to manually configure network interfaces under several Operating Systems.

Tell Network Manager to stop controlling the interfaces used by the test configuration

Network Manager has a command line tool that can be used to see which interfaces it is controlling. Pull up a terminal window and type the following command:

$ nmcli dev status

This displays a table that lists all network interfaces along with their STATE. If Network Manager is not controlling an interface, its STATE will be listed as unmanaged. Any other value indicates the interface is under Network Manager control.

Network Manager settings are controlled by a configuration file: /etc/NetworkManager/nm-system-settings.conf (NM 0.7 and 0.8.0) or /etc/NetworkManager/NetworkManager.conf (NM 0.8.1 and later). We will use this file to tell Network Manager to stop controlling a particular interface, but how this is done depends on which linux operating system is running.

CentOS, Fedora, Red Hat

With these linux distributions, the preferred way to tell Network Manager to stop controlling an interface is by editing the individual ifcfg-* files. First, make sure the Network Manager configuration file has the following lines.

[main]
plugins=ifcfg-rh

This plugin tells Network Manager to look at the Red Hat ifcfg-* files. Now for each interface you’d like Network Manager to ignore, edit the individual /etc/sysconfig/network-scripts/ifcfg-* interface files, adding the following lines:

NM_CONTROLLED=no
HWADDR=00:11:22:33:44:55

Of course, set the HWADDR value to be the actual MAC address of this interface. Often this line is already present.

Ubuntu, Debian

With these linux distributions, one way to tell Network Manager to stop controlling a particular interface is by telling Network Manager to ignore ALL interfaces listed in the /etc/network/interfaces file. This is done by adding the following lines to the Network Manager configuration file:

[main]
plugins=ifupdown

[ifupdown]
managed=false

Since this will only affect interfaces listed in the /etc/network/interfaces file, any interface not listed there will remain under Network Manager control.

Alternate KEYFILE method

Regardless of which linux distribution is running, an alternate method can be used to tell Network Manager to stop controlling an interface. This is done by adding the following lines to the Network Manager configuration file:

[main]
plugins=keyfile

[keyfile]
unmanaged-devices=mac:00:11:22:33:44:55;mac:66:77:88:99:00:aa

List the MAC address of each interface you want Network Manager to ignore, separated with a semicolon. Make sure that MAC addresses listed here are LOWER CASE.

Stop the Network Manager process

If Network Manager is not needed during testing, it can be shut off completely. The stop/start command is a little different depending on the linux distribution used:

CentOS, Fedora, Red Hat
$ service NetworkManager stop
$ service NetworkManager start
Ubuntu, Debian
$ sudo service network-manager stop
$ sudo service network-manager start

Remove the Network Manager software from the system

If Network Manager will not be needed at all, it can be removed from the system completely. Again, this procedure is a bit different depending on the linux distribution used:

CentOS, Fedora, Red Hat
$ yum remove NetworkManager
Ubuntu, Debian
$ sudo apt-get remove network-manager
时间: 2024-08-10 15:10:54

nm applet disable的相关文章

redis error It was not possible to connect to the redis server(s); to create a disconnected multiplexer, disable AbortOnConnectFail. SocketFailure on PING

应用redis出现如下错误 It was not possible to connect to the redis server(s); to create a disconnected multiplexer, disable AbortOnConnectFail. SocketFailure on PING 参考stack overflow上文章 http://stackoverflow.com/questions/30895507/it-was-not-possible-to-connec

disable NetworkManager and boot on static ip configuration using /etc/network/interfaces

1.stop and disable NetworkManager sudo systemctl stop NetworkManager sudo systemctl disable NetworkManager 2.drop status of NetworkManger sudo mv /var/lib/NetworkManager/NetworkManager.state /var/lib/NetworkManager/NetworkManager.state.bak 3.edit int

Disable Maven Nature

1.Disable Maven Nature myeclipse更新maven的时候,手抖了一下,点上了Disable Maven Nature,然后工程右键菜单中的Maven栏就不见了! 其实这是把maven工程转换成了一般工程,再转回来就好了. maven工程转为一般工程: 工程右键--->Maven--->Disable Maven Nature转为一般工程. 一般工程转为maven工程: 工程右键--->Configure--->Convert to Maven Proje

html input readonly 和 disable的区别

Readonly和Disabled它们都能够做到使用户不能够更改表单域中的内容.但是它们之间有着微小的差别,总结如下: Readonly只针对input(text / password)和textarea有效,而disabled对于所有的表单元素都有效,但是表单元素在使用了disabled后,当我们将表单以POST或GET的方式提交的话,这个元素的值不会被传递出去,而readonly会将该值传递出去(readonly接受值更改可以回传,disable接受改但不回传数据). 一般比较常用的情况是:

《java小应用程序(Applet)和java应用程序(Application)分别编写的简单计算器》

Application和Java Applet的区别.Java语言是一种半编译半解释的语言.Java的用户程序分为两类:Java Application和Java Applet.这两类程序在组成结构和执行机制上都有一定的差异,主要体现在以下几方面:(1)运行方式不同.Java Application是完整的程序,可以独立运行:Java Applet程序不能单独运行, 它必须嵌入到用HTML语言编写的Web页面中,通过与Java兼容的浏览器来控制执行.(2)运行工具不同.Java Applicat

error C4996: 'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation

遇到这个问题,请打开项目的Properties(属性)------->Configuration Properties(配置属性)------>C/C++ ------>Preprocessor(预处理器)------->Preprocessor Difinitions (预处理器定义)   添加   _CRT_SECURE_NO_WARNINGS     之后点击OK.最后   应用------>确定. error C4996: 'fopen': This function

通过JavaScript和Applet获取客户端硬盘号

仅通过JS实现,适用于IE10+浏览器 <script> function getSerialNumber() { var retVal = ""; var locator = new ActiveXObject ("WbemScripting.SWbemLocator"); var service = locator.ConnectServer("."); var properties = service.ExecQuery(&qu

atitit. applet 浏览器插件 控件 的环境,开发,提示总结o9o

atitit. applet 浏览器插件 控件 的环境,开发,提示总结o9o 1. 建立applet:: 1 2. Applet 码 1 3. Applet (awt)跟japplet (swing)的区别.. 1 4. Html 码 1 5. Applet部署:::class 跟个jar 到个weebroot 2 5.1. 导入在的jar ,也放得个weebroot 哈,,,多个jar 逗号分割 2 6. 安全机制排除 D:\jdk1.7.0_01\jre\lib\security\java.

atitit. 浏览器插件 控件 applet 的部署,签名总结 浏览器 插件 控件 的签名安全机制o9o

atitit. 浏览器插件 控件   applet 的部署,签名总结 浏览器 插件 控件 的签名安全机制o9o 1. 服务器部署签名 1 2. 签名流程::生成密钥..导出cert正书,签名 1 3. jarsigner 错误: java.lang.IllegalArgumentException: MALFORMED 1 4. Jar的包装and签名的流程原理 2 5. 参考 2 1. 服务器部署签名 applet 的本地调试,可以使用调整java.policy的解决...虽然中间也能正式版使