Network Manager encountered a problem

1. When testing the WiFi driver on Fedora 6, it was found that the command line could quickly connect the STA to the AP, but there was no way to connect with the UI of network manager. At that time, the UI started with the following command Network-manager&, through DMESG view, should be connected later, do not know which process sent the disconnected command.

Search from the Internet a lot, said there is conflict, was going to follow this approach to solve the problem, but found that seems unworkable. The following command is used to start network Manager, and the connection is found to be successful.

Sudo/etc/init.d/network-manager stop

Sudo/etc/init.d/network-manager restart

It is not yet known why. There are also some bugs that have been found about network manager, which are summarized below for later resolution of the problem.

Bug1.

The original Linux has two sets of management network connection scheme:
1,/etc/network/interfaces (/etc/init.d/networking)
2, Network-manager
The two sets of programmes are conflicting and cannot coexist at the same time.
The first scenario applies to environments where there is no x, such as servers, or where there is no need to change the connection at all.
The second scheme is used in the environment with desktop, especially the notebook, moved to move, the network connection situation can change at any time.
－－－－－－－－－－－－－
The two of them, in order to avoid conflict and share configuration, have the following solution:
1, when Network-manager found that the/etc/network/interfaces was changed, then close themselves (shown as unmanaged), unless the managed set to true.
2. When the managed is set to true, the/etc/network/interfaces is not effective.
Then follow the instructions for the following actions:
In the terminal run sudo gedit/etc/networkmanager/nm-system-settings.conf, open the nm-system-settings.conf, put the inside of the managed set to true, namely: the last sentence " Managed=false "changed to" Managed=true ". Then restart the Network service with sudo/etc/init.d/networking Restart and find that the wired connection is not editable and the DSL cannot add the account number and password (I want to add my account number and password). Then run sudo gedit/etc/network/interfaces at the terminal and delete the following in the interfaces file:

Auto Dsl-provider
Iface Dsl-provider inet PPP
Pre-up/sbin/ifconfig eth0 Up # line maintained by pppoeconf
Provider Dsl-provider

Auto Eth0
Iface eth0 inet Manual

Keep only the contents of the file that begin with:

Auto Lo
Iface Lo inet Loopback, so you can edit the wired Internet information. Wired networks can be edited, but the content of the DSL can sometimes be edited and sometimes wrong. Surfing the Internet or not. What a rush. And then remove the DNS settings
sudo mv/etc/resolv.conf/etc/resolv.conf_backup is still useless.
It seems that the NetworkManager and PPPoE conflict bug is unable to ADSL dial-up failed to successfully surf the Internet. Thinking again and again, had to use the command sudo apt-get autoremove network-manager Delete NetworkManager, and then use the command sudo pppoeconf to enter the required content (including my telecommunications online account wzl.****** and password ********). When you are done, enter command sudo ifconfig eth0 up
, connect to the Internet, immediately successful. -----Lin Ming 2010.2.3 night 22:28.

Bug 2:

This is a bug in Gnome's network manager:
We know that there are three ways in which WEP encryption is an open system that is completely unencrypted, and there are two types of encryption, one in hexadecimal digits and one in ASCII, which can be either 64-bit or 128-bit. In Ubuntu, you can use the Iwconfig command to configure, the difference is the ASCII code configuration to add S: and the Open and encryption form of the distinction between the keyword restricted to distinguish. The key here is that every time a change is made to the wireless adapter in GNOME's network manager, his information about the configuration file is missing a keyword restricted!!! The bug has not been fixed yet. Even if it is simple to enable, disabling the wireless network card will write the error message back to the configuration file. So the crux of the problem is here, it would be good to do. Configure the wireless adapter settings, then enable, open a terminal, and enter the following command:
sudo gedit/etc/network/interfaces, add a "restricted" after the Wireless-key, save, and then reboot the system. Since the wireless card settings generally do not change, so it can be counted once and for all. Some people also specifically set the command line wireless network card, connected to the network as a script, automatically when the boot, do not need so trouble pull, as long as add a keyword to solve.

BUG3: windows switch to Ubuntu under network connectivity is not a problem

APR 9th, 2010

Vaguely always feel as if something want to write out but forgot, this is the last time to help colleagues installed Ubuntu encountered network connection can not be a problem.

The specific symptom is this, after the system is installed to enter X-windows, the default DHCP assigns IP, but obtains after a period of time to display the Red fork, obtains the failure. I thought that the company has always been the use of fixed IP to set their own manually, the routing of DHCP turned off. Then in the network Manger GUI manually set static IP, the network also shows the connection, but can not access the Internet. Does the route hang up. Ping under the gateway to see, Leng, incredibly can ' t find host. Restart after the toss again is still invalid, so suspected network card configuration or driver has problems, hurriedly Google.

Google out of the content of the same more, no less than the GUI below network Manager and network interface configuration file each way, there may be conflicts and so on. Then uninstall network Manger, manually configure network interface, still invalid. At this time to see this article inside a paragraph "is said to be windows will shut down when the network card is disabled, the next time the reboot will not enable the network card again." Installed Realtek 8139/810x or 8168/8111 XP network card driver will be like this. ”

I rub, not so clever let me encounter this small probability event. Hurriedly restart into win a look, sure enough is Realtek 8139 network card. Follow the instructions "Right click on My Computer – Properties – Hardware tab – Device Manager – Double-click the NIC under Network adapter Realtek rtl8139-Select the Advanced tab – Wake-on-lan after shutdown set to enable" And the world is back to normal.