Hello.
I am wondering if the problem is just that the script
/etc/dhcp3/dhclient-enter-hooks.d/ntp is in the wrong
place. It should really be in the dhclient-exit-hooks.d
directory so that the script is run after dhcp has
completed initialization of the network instead of before.
Making this
Bon soir,
Arne Nordmark wrote:
} I ran into this problem with eth1, my WLAN card. I found that
} by moving the script from /etc/dhcp3/dhclient-enter-hooks.d to
} /etc/dhcp3/dhclient-exit-hooks.d it is now executed at the
} correct phase, after the interface has been given addresses.
}
I wrote:
I ran into this problem with eth1, my WLAN card. I found that
by moving the script from /etc/dhcp3/dhclient-enter-hooks.d to
/etc/dhcp3/dhclient-exit-hooks.d it is now executed at the
correct phase, after the interface has been given addresses.
Except ... scripts from that location
Hello,
I ran into this problem with eth1, my WLAN card. I found that
by moving the script from /etc/dhcp3/dhclient-enter-hooks.d to
/etc/dhcp3/dhclient-exit-hooks.d it is now executed at the
correct phase, after the interface has been given addresses.
It would also be nice, if there was a way to
I wrote:
I ran into this problem with eth1, my WLAN card. I found that
by moving the script from /etc/dhcp3/dhclient-enter-hooks.d to
/etc/dhcp3/dhclient-exit-hooks.d it is now executed at the
correct phase, after the interface has been given addresses.
Except ... scripts from that location
I ran into the same problem. Here some more information.
On startup (boot process) of my Debian/Etch dhcp/ntp clients, the hook
/etc/dhcp3/dhclient-enter-hooks.d/ntp
gets called, (re)starting ntpd at a point in time (DHCP BOUND), when the
network is not configured yet. Some seconds later the
Erik Thiele wrote:
the problem now is that the dhclient sets networking parameters after
ntpd has already started. dhclient won't restart ntpd because
configuration hasn't changed.
So what is the actual problem? ntp.conf.dhcp is not created, or it
doesn't contain the right information, or
Am Dienstag, 10. April 2007 22:27 schrieben Sie:
Erik Thiele wrote:
the problem now is that the dhclient sets networking parameters after
ntpd has already started. dhclient won't restart ntpd because
configuration hasn't changed.
So what is the actual problem? ntp.conf.dhcp is not
Package: ntp
Version: 4.2.2.p4+dfsg-1
my ethernet is configured via dhcp:
goofy:/etc# cat network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
i added
request ntp-servers;
to /etc/dhcp3/dhclient.conf
so that ntpd.conf.dhcp gets created. see bug #407667.
the problem
9 matches
Mail list logo
