El nombre de host local cambia cada pocos segundos cuando NO está conectado a una red

2

Cuando vuelvo a encender mi computadora portátil, pero antes de conectarme a una red, recibo mensajes similares a los siguientes:

This computer's local hostname
"sojourner-896.local" is already in use on
this network. The name has been changed
to "sojourner-972.local"

Si no me conecto a una red y no hago clic en el botón "Aceptar", los nombres de host se incrementan. Si me conecto a una red (ya sea por cable o inalámbrica), los nombres dejan de incrementarse.

Restablezco el nombre de host en el panel de preferencias "Compartir" cuando los nombres de host se ubican en el rango de 5,000 a 6,000 (cada 2-3 días).

¿Alguna idea de qué podría estar causando esto?

    
pregunta David M. Syzdek 12.08.2014 - 18:33

2 respuestas

1

Busqué en los registros a través de la aplicación de la consola y descubrí que los siguientes registros se generan cada vez que me desconecto de una red:

8/29/14 10:07:59.087 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7647.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:07:59.087 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7647.local. Addr 127.0.0.1
8/29/14 10:07:59.087 PM mDNSResponder[414]: Local Hostname sojourner-7647.local already in use; will try sojourner-7743.local instead
8/29/14 10:08:00.923 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7647.local" to "sojourner-7743.local"
8/29/14 10:08:00.944 PM configd[26]: setting hostname to "sojourner-7743.local"
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7743.local. Addr 127.0.0.1
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.146 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7743.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.456 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.457 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7743.local. Addr 127.0.0.1
8/29/14 10:08:02.457 PM mDNSResponder[414]: Local Hostname sojourner-7743.local already in use; will try sojourner-7765.local instead
8/29/14 10:08:04.365 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7743.local" to "sojourner-7765.local"
8/29/14 10:08:04.375 PM configd[26]: setting hostname to "sojourner-7765.local"
8/29/14 10:08:04.633 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7743.local.
8/29/14 10:08:04.633 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7765.local.
8/29/14 10:08:04.734 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7743.local.
8/29/14 10:08:04.734 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7765.local.
8/29/14 10:08:05.839 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7765.local. Addr 127.0.0.1
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7765.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:06.141 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:06.141 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7765.local. Addr 127.0.0.1
8/29/14 10:08:06.141 PM mDNSResponder[414]: Local Hostname sojourner-7765.local already in use; will try sojourner-7802.local instead
8/29/14 10:08:08.006 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7765.local" to "sojourner-7802.local"
8/29/14 10:08:08.016 PM configd[26]: setting hostname to "sojourner-7802.local"
8/29/14 10:08:08.268 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7765.local.
8/29/14 10:08:08.268 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7802.local.
8/29/14 10:08:08.357 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7765.local.
8/29/14 10:08:08.357 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7802.local.
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7802.local. Addr 127.0.0.1
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7802.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.733 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.733 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7802.local. Addr 127.0.0.1
8/29/14 10:08:09.733 PM mDNSResponder[414]: Local Hostname sojourner-7802.local already in use; will try sojourner-7837.local instead
8/29/14 10:08:11.578 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7802.local" to "sojourner-7837.local"
8/29/14 10:08:11.588 PM configd[26]: setting hostname to "sojourner-7837.local"
8/29/14 10:08:11.815 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7802.local.
8/29/14 10:08:11.815 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7837.local.
8/29/14 10:08:11.915 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7802.local.
8/29/14 10:08:11.915 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7837.local.
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7837.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7837.local. Addr 127.0.0.1
8/29/14 10:08:12.786 PM mDNSResponder[414]: Excessive name conflicts (17) for sojourner-7837.local. (Addr); rate limiting in effect
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7837.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: Excessive name conflicts (18) for sojourner-7837.local. (AAAA); rate limiting in effect
8/29/14 10:08:14.193 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.194 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.497 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.497 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:16.212 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:19.916 PM digest-service[701]: digest-request: init return domain: SOJOURNER-7647 server: SOJOURNER-7837 indomain was: <NULL>
8/29/14 10:08:19.937 PM digest-service[701]: digest-request: init return domain: SOJOURNER-7837 server: SOJOURNER-7837 indomain was: <NULL>

Volví a habilitar la red alrededor del segundo 10:08:14.

El proceso real que cambió el nombre de host es configd . La página de manual de configd establece que

The configd daemon is responsible for many configuration aspects of the
local system. configd maintains data reflecting the desired and current
state of the system, provides notifications to applications when this data
changes, and hosts a number of configuration agents in the form of loadable
bundles.

y

At the present time, the majority of the configuration agents (or bundles)
hosted by configd are used to establish and maintain the network
configuration.

Las páginas man muestran los siguientes archivos relacionados:

 /Library/Preferences/SystemConfiguration/preferences.plist
 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
 /Library/Preferences/SystemConfiguration/VirtualNetworkInterfaces.plist

El archivo preferences.plist parece tener las preferencias de red especificadas por el panel de preferencias de Red en Preferencias del sistema. Hice una copia de seguridad, la eliminé, eliminé configd y realicé un reinicio de bajo nivel:

cd /Library/Preferences/SystemConfiguration/
cp preferences.plist ~/Desktop/preferences.plist
sudo rm -f preferences.plist
sudo killall configd
sudo killall configd
sudo reboot

Después de reiniciar el sistema, el sistema ya no cambia el nombre del host cada pocos segundos cuando NO está conectado a una red.

    
respondido por el David M. Syzdek 30.08.2014 - 08:31
0

A mi alrededor, encontré un hilo en el SuperUser que podría ser de ayuda.

enlace

Es muy extraño que esto suceda cuando NO estás conectado a una red, desearía tener una mejor respuesta.

Parece que recuerdo una preferencia enterrada en algún lugar de las Preferencias del sistema que permite a la Mac obtener un nombre de host dinámico del servidor DHCP, pero por mi vida no puedo encontrar la maldita configuración. Así que o me acuerdo mal o fue algo de una encarnación de un gatito anterior.

    
respondido por el Steve Chambers 13.08.2014 - 20:48

Lea otras preguntas en las etiquetas