opensuse
[Arriba] [Todas las Listas]

Re: [opensuse] Qué 127.0.1.1 malo?

To: opensuse@xxxxxxxxxxxx
Subject: Re: [opensuse] Qué 127.0.1.1 malo?
From: Anton Aylward <opensuse@xxxxxxxxxxxxxxxx>
Date: Tue, 03 Apr 2012 13:18:03 -0400
Delivered-to: opensuse@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 03 Apr 2012 13:19:44 -0400
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=antonaylward.com; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s= antonaylward.com; bh=ZFVbgxSljCVILs88+V8sSvyQ+NE=; b=lFjG+RceE41 r/mWJqYAqlhyntuKJXM8uMRX93I/+rGi52RCjtpc/a37X6XjFIs9xi7cxO4FEGeK lvg4DadhMswfamn+v4YqEeYaDOn62yEyE1psBrzkOvSLPcMLNiL4PUfbLc+s2z6K kXt3qGtCrnUE0ARWUCNxc75EeDJl2k7s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=antonaylward.com; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s= antonaylward.com; b=Gjz6VsM4+BJdwFb4KOL75tCO+KsfCYLpD0Wx1s+Ul8Yw oAcfbGuQVvHA9/lorowdcAmsKunm++HZ0oYpdxNS09D7cRZsEoj5P/5BRjaFMY3X SoA9irb2laipEetyUf731SUb0uhgZGMH8E0xoZYrkp1DJo7C0p87kumyNxABMtE=
Envelope-to: traductor@xxxxxxxxxxx
In-reply-to: <4F7B2101.4050101@steve-ss.com>
List-archive: <http://lists.opensuse.org/opensuse/>
List-help: <mailto:opensuse+help@opensuse.org>
List-owner: <mailto:opensuse+owner@opensuse.org>
List-post: <mailto:opensuse@opensuse.org>
List-subscribe: <mailto:opensuse+subscribe@opensuse.org>
List-unsubscribe: <mailto:opensuse+unsubscribe@opensuse.org>
Mailing-list: contact opensuse+help@xxxxxxxxxxxx; run by mlmmj
Organization: SI
References: <4F749D25.7080107@steve-ss.com> <4F75950D.6020203@steve-ss.com> <4F75A8A8.9030102@antonaylward.com> <4F75CE13.6050706@telefonica.net> <4F75EA66.20304@antonaylward.com> <4F76095B.1080801@steve-ss.com> <4F7631DF.1000603@antonaylward.com> <4F76AF84.1050805@steve-ss.com> <4F76FA67.4090507@antonaylward.com> <4F772477.3080002@steve-ss.com> <4F7737F2.5000903@antonaylward.com> <4F7744CF.9030204@steve-ss.com> <4F775380.8040606@antonaylward.com> <4F77FE5C.90401@steve-ss.com> <4F782BB3.6070809@telefonica.net> <4F784FB1.1030403@steve-ss.com> <alpine.LNX.2.00.1204012233580.7695@Telcontar.valinor> <4F78C05D.5030102@steve-ss.com> <4F78CE47.5030401@antonaylward.com> <4F795F9F.4060005@steve-ss.com> <4F796EE3.1030301@telefonica.net> <4F799B9F.7040200@antonaylward.com> <4F79D32B.8080802@steve-ss.com> <4F79EE41.8000901@antonaylward.com> <4F7A98C8.8020705@steve-ss.com> <4F7AF025.9030405@antonaylward.com> <4F7B1F44.4060803@steve-ss.com> <4F7B2101.4050101@steve-ss.com>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20120209 Firefox/10.0.1 Thunderbird/10.0.1
*Lynn Dijo el siguiendo en 04/03/2012 12:10 PM:

> De:
> *https://listas.*samba.*org/*archive/*samba/2012-abril/166830.*html
> 
> <Cita>
> si vuestro *DHCP el cliente es capaz de hacer
> *GSS-*TSIG actualiza contra ventanas,
> </cita>
> 
> Es nuestro *DHCP cliente capaz de hacer aquello?
> *L *x

Dejó tiene el lleno cita:

<citar>
Si vuestro *DHCP el cliente es capaz de hacer
*GSS-*TSIG actualiza contra ventanas, tendría que ser capaz de hacer igual
contra *Samba4. Si el *DHCP el cliente no puede actualizar, tendrás que imaginar
fuera de cómo para fijar el lado de cliente de cosas.
<Cita>

*Lynn, esto es todo bien documentado en las varias referencias he
proporcionado y puede ser probado con *nsupdate.

Inicio del interior fuera.

1. Puede tú *dynamically actualizar DNS con delantero y revés
   (a mano, *cli utilizando *nsupdate) ?

Si no, entonces tienes un problema con *DDNS contra LIGAR.
Descubrir lo que aquello es y fijarlo

2. Es el *crypto la llave compartida entre *DHCP y LIGAR?
   Esto tendría que ser la misma llave utilizada en (1)

3. Es *DHCP montado para utilizar *DDNS contra LIGAR para el pertinente *subnet?
   Otra vez, consultar el *URLs para parámetros a *DHCP que incluí en
   correos más tempranos

-- 
me pregunto por qué. Me pregunto por qué.
Me pregunto por qué me pregunto.
Me pregunto por qué me pregunto por qué
me pregunto por qué me pregunto!
    -- Richard *Feynman
-- 
A *unsubscribe, *e-correo: *opensuse+unsubscribe@xxxxxxxxxxxx
para contactar el dueño, *e-correo: *opensuse+owner@xxxxxxxxxxxx


Lynn said the following on 04/03/2012 12:10 PM:

> From:
> https://lists.samba.org/archive/samba/2012-April/166830.html
> 
> <quote>
> if your DHCP client is able to
> do GSS-TSIG updates against windows,
> </quote>
> 
> Is our DHCP client able to do that?
> L x

Let have the full quote:

<quote>
If your DHCP client is able to
do GSS-TSIG updates against windows, it should be able to do the same
against Samba4. If the DHCP client can't update, you'll have to figure
out how to fix the client side of things.
<quote>

Lynn, this is all well documented in the various references I have
provided and can be tested with nsupdate.

Start from the inside out.

1. Can you dynamically update DNS with forward and reverse
   (manually, cli using nsupdate) ?

If not, then you have a problem with DDNS against BIND.
Find out what that is and fix it

2. Is the crypto key shared between DHCP and BIND?
   This should be the same key used in (1)

3. Is DHCP set up to use DDNS against BIND for the relevant subnet?
   Again, consult the URLs for parameters to DHCP that I included in
   earlier mails

-- 
I wonder why. I wonder why.
I wonder why I wonder.
I wonder why I wonder why
I wonder why I wonder!
    -- Richard Feynman
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx


<Anterior por Tema] Tema Actual [Siguiente por Tema>