[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Network problem



On Sat, 07 May 2011 16:49:07 +0100, AG wrote:

> On 07/05/11 16:39, Camaleón wrote:

(...)

>> Let's see... on a running system, once you edit the "/etc/network/
>> interfaces" file you also have to:
>>
>> 1/ Restart the network service: /etc/init.d/networking restart 
>> 2/ Up the network interface: ifup eth0 
>> 3/ Check that all is fine: /sbin/ifconfig
>>
>> (this is not needed after you restart the machine)
>>
>> Try it and send the results. The rest of the files look normal so let's
>> focus on this.
> 
> Here are the results of those three commands:
> 
> $ sudo /etc/init.d/networking restart 
> sudo: unable to resolve host
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

(...)

Once you resolve the networking problem, you should look from where is 
coming that "sudo" error... Is it happening for any "sudo" command you 
type? :-?

> $ /sbin/ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:90:47:05:a3:07
>            inet addr:192.168.1.40  Bcast:192.168.1.255 
>            Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64
>            Scope:Link UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:10700 errors:0 dropped:0 overruns:0 frame:0 TX
>            packets:10113 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:8424815 (8.0 MiB)  TX bytes:1223781 (1.1 MiB)
>            Interrupt:18 Base address:0xec00

(...)

Hey, that seems to be the right one :-)

> The IP address is now consistent.
> 
> Now is this likely to hold when I reboot so that I can access the Net?

(...)

Sure, and if not something is very badly broken. Restart the machine to 
be sure and if the IP address changes again, review your syslog.
 
Greetings,

-- 
Camaleón


Reply to: