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

Re: Configuración secundaria para el adaptador de red (dhcp+estático)



El Tue, 05 Oct 2010 11:00:57 +0000, Camaleón escribió:

> El Tue, 05 Oct 2010 11:35:22 +0200, jmramirez escribió:
> 
> (...)
> Cuando termine el día (ahora no
> puedo), apagaré el servidor que lleva el DHCP a ver qué hace la VM.
> Espero que funcione, ya os comento.

Pues no, no ha funcionado :-(

Al apagar el servidor que proporciona DHCP, la VM pierde la conexión. En 
el syslog aparece registrado el intento:

***
Oct  6 07:17:02 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Oct  6 07:17:15 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Oct  6 07:17:23 debian dhclient: No DHCPOFFERS received.
Oct  6 07:17:23 debian dhclient: No working leases in persistent database - sleeping.
Oct  6 07:24:29 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Oct  6 07:24:37 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Oct  6 07:24:53 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Oct  6 07:25:07 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
Oct  6 07:25:28 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Oct  6 07:25:30 debian dhclient: No DHCPOFFERS received.
Oct  6 07:25:30 debian dhclient: No working leases in persistent database - sleeping.
***

Cuando inicio el servidor que lleva DHCP, vuelve a retomar la conexión:

***
Oct  6 07:28:39 debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Oct  6 07:28:39 debian dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  6 07:28:39 debian dhclient: DHCPACK from 172.16.0.11
Oct  6 07:28:39 debian avahi-autoipd(eth0)[9070]: Got SIGTERM, quitting.
Oct  6 07:28:39 debian avahi-autoipd(eth0)[9070]: Callout STOP, address 169.254.9.65 on interface eth0
Oct  6 07:28:40 debian dhclient: bound to 172.16.0.163 -- renewal in 226 seconds.
Oct  6 07:30:01 debian /USR/SBIN/CRON[9850]: (root) CMD (test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null)
Oct  6 07:30:02 debian anacron[9872]: Anacron 2.3 started on 2010-10-06
Oct  6 07:30:02 debian anacron[9872]: Will run job `cron.daily' in 5 min.
Oct  6 07:30:02 debian anacron[9872]: Jobs will be executed sequentially
Oct  6 07:32:26 debian dhclient: DHCPREQUEST on eth0 to 172.16.0.11 port 67
Oct  6 07:32:26 debian dhclient: DHCPACK from 172.16.0.11
Oct  6 07:32:26 debian dhclient: bound to 172.16.0.163 -- renewal in 250 seconds.
Oct  6 07:35:02 debian anacron[9872]: Job `cron.daily' started
Oct  6 07:35:02 debian anacron[9914]: Updated timestamp for job `cron.daily' to 2010-10-06
Oct  6 07:36:36 debian dhclient: DHCPREQUEST on eth0 to 172.16.0.11 port 67
Oct  6 07:36:36 debian dhclient: DHCPACK from 172.16.0.11
Oct  6 07:36:36 debian dhclient: bound to 172.16.0.163 -- renewal in 259 seconds.
Oct  6 07:40:55 debian dhclient: DHCPREQUEST on eth0 to 172.16.0.11 port 67
Oct  6 07:40:55 debian dhclient: DHCPACK from 172.16.0.11
Oct  6 07:40:55 debian dhclient: bound to 172.16.0.163 -- renewal in 272 seconds.
***

¿A alguien se le ocurre qué puede estar mal? En la sección de "lease" 
he puesto:

***
lease {
  interface "eth0";
  fixed-address 172.16.0.66;
  option subnet-mask 255.255.255.0;
  option routers 172.16.0.1;
  option domain-name-servers 80.58.0.33;
}
***

Y he activado el modo de depurado de dhclient, pero el registro que 
genera en /tmp me indica que efectivamente, no está tomando ningún valor
de los que le he dicho :-?

Saludos,

-- 
Camaleón


Reply to: