Ubuntu
conky package

How to RE-ESTABLISH the Internet Connection disturbed due to setting of Netwoprking?

Asked by Navin Talati

Sir,

I need your help as I have lost my internet connectivity of the system. It happened due to a part of installation process of "zoneminder" instruction as per the link :

http://www.zoneminder.com/wiki/index.php/Ubu...

According to this instruction, I was trying to set static IP address and used the following commands:

sudo su

nano /etc/network/interfaces

Then I made following changes as per that literature:

auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1 68.87.75.194

There is a note in that:

"Note: for Ubuntu 12.04 the resolv.conf is dynamically assigned. The "dns-servers" entry in the interfaces file will set the DNS Multiple DNS server entries can be used."

Then I applied the following stuffs to save the changes and exit:

Ctrl+o Enter to save
CTRL+x to exit

Then Rebooted the system.

After this, when I tried to connect the net through Firefox, it was seen that the "eth0" connection was lost. I used "Network Tools" to check the status. It shows THREE network devices as:

Loopback Interface (lo)
Ethernet Interface (eth0)
Ethernet Interface (eth1)

out of these (lo) was found activated and remaining TWO (eth0) and (eth1) were inactive.

Through "Network" application, there is a massage that "System network services are not compatible with this version"
As per the guide (Ubuntu Desktop Guide), I applied "nm-applet" stuff to the terminal,the OUTPUT is as under:

-------------------------------------------------------------------------------------------------------------------------------
navin@navin:~$ nm-applet

** (nm-applet:4203): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
** Message: applet now removed from the notification area

** (nm-applet:4203): WARNING **: Failed to register as an agent: (2) The name org.freedesktop.NetworkManager was not provided by any .service files

** (nm-applet:4203): WARNING **: Could not find ShellVersion property on org.gnome.Shell after 5 tries

------------------------------------------------------------------------------------------------------------------------------------

As this thing seems quite TECHNICAL in nature I am unable to properly understand the significance and could not REVERT my system's status at the ORIGINAL.

I NEED TYOUR HELP in the following matter:

(1).How can I bring my system to the original status?

(2). How to REVERT / CANCELL the effect of information incorporated/saved as:

auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1 68.87.75.194

(3). Which commands are required to nullify the above effect so that I can connect to the INTERNET.

Please URGENTLY reply to re-set me from the above disturbance and OBLIGE

Navin Talati / 14-9-2013

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu conky Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Thomas Krüger (thkrueger) said : 		#1

If you setup your network interface manually in /etc/network/interfaces Network Manager will not handle them anymore.
You should revert the file back to it's original state, which is just:

auto lo
iface lo inet loopback

Then Network Manager should take the control again. You can set a fixed IP in the setting there.

Revision history for this message
Navin Talati (n-m-talati) said : 		#2

SIR,
Thanks for the valuable suggestion.

As per your instruction, I applied the suff "sudo su" to become root and then applied "nano /etc/network/interfaces" to open the interfaces file. I wrote following TWO lines as suggested by you:

auto lo
iface lo inet loopback

in that file, but some how it did not give the desirable result. Then I referred some other literature on the web for Network & Auto eth0 Configuration from:

(1).Ubuntu Documentation>Ubuntu 10.04>Ubuntu Server Guide>Networking>Network Configuration.
(2).askubuntu.com/questions/31023/how-to-configure-eth0-manually
(3).ubuntuforums.org/showthread.php?t=1957680

According to that I tried to enter:

auto eth0
iface eth0 inet dhcp

That too did not work.

Then after I opened the file "interfaces" through /etc/network/interfaces from the /. Here in this file I found the content (which was created through my initial changes as per the original question)saved as under:

eth0 inet static
 address 192.168.1.10
 netmask 255.255.255.0
 gateway 192.168.1.1
 dns-nameserver 192.168.1.1 68.87.75.194

which was not working and also it disturbed my net connection. Still this file exist in /etc/network
Through the course of the whole process I also lost the desktop loading and tty1 was opening every time. through this vertual terminal I again entered as root and applied your suggested stuff "auto lo" and"iface lo inet loopback" and could save the changes.

To my great surprise, the system booted normally and Intewrnet started.

Thanks a lot for the help.

Now, I need your little further help in this matter.

As I said earlier, that due to the course of efforts above in the directory /etc/network some additional files have been created/saved in addition to "interfaces". These are as under:

interfaces.save
interfaces.save.1
interfaces.save.2
interfaces.save.3

Are these required files?
These are not getting deleted. How to remove them?

Please give me a commandline to remove them .
Thanking you in anticipation.
Navin Talati / 16-09-2013

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Can you ping 8.8.8.8 with your configuration? Why are you using the interfaces file then launching nm-applet? It makes no sense at all.

Revision history for this message
Navin Talati (n-m-talati) said : 		#4

Sir,

(1).
I applied "nm-applet" as per the guide (Ubuntu Desktop Guide) stuff to the terminal,the OUTPUT is given earlier in initial question content. Actually I do not understand the meaning and purpose of this commansd, but I simply applied because it was in the UDG (guide) as I had hope of getting my problem resolved.
May I know the purpose, meaning, and when to apply "nm-applet" stuff?

(2).
Through Terminal I applied "ping 8.8.8.8" and the output continued as under:
navin@navin:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=48 time=107 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=48 time=114 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=48 time=106 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=48 time=103 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=48 time=107 ms
64 bytes from 8.8.8.8: icmp_req=6 ttl=48 time=106 ms
64 bytes from 8.8.8.8: icmp_req=7 ttl=48 time=104 ms
64 bytes from 8.8.8.8: icmp_req=8 ttl=48 time=105 ms

Through Network Tools it was applied for 5 requests. In that also data are almost same
as above.
Round Trip Time Statics :----> Minimum: 83.00 ms
                                                       Average: 89.43 ms
                                                     Maximum: 105.00 ms
Transmission Statistics : ------> Packets Transmitted: 5
                                                         Packets Received : 5
                                                         Successful packets : 100%
Above both the results are matching.

As mentioned in # 2, can I now remove the additional FOUR files created/saved in addition to "interfaces". which are as under:
interfaces.save
interfaces.save.1
interfaces.save.2
interfaces.save.3
If not useful please give me a commandline to remove them .

Navin Talati / 16-09-2013

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

You can remove the old interfaces files. If you run:

echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf > /dev/null

Then try the web. Does it work ok?

If so, we can make it stick.

Can you help with this problem?

Provide an answer of your own, or ask Navin Talati for more information if necessary.

To post a message you must log in.