W dniu 2010-11-29 21:37, Marc-Andre Alpers pisze:
Hello!
Have nobody a solution or idea wat is wrong with my server?
Hello,
I think this is the same bug : http://bugs.gentoo.org/326209 . I have
got very similar problem.
Regars
___
questions mailing
horhe,
I can't speak to the versions used by other repackagers, but the current
ntp-dev version interprets a nonzero broadest delay option as defeating
the calibration volley for all broadcast and multicast clients. This is
why it replaced the novolley option of the broadcast client command.
Es schrieb horhe:
Hello,
I think this is the same bug : http://bugs.gentoo.org/326209 . I have
got very similar problem.
Thanks. This was the point. My Linux Kernel is grsec enabled by default.
When i load a non grsec Kernel, then ntp works fine on ipv6.
MfG Marc-Andre Alpers
Marc-Andre Alpers wrote:
Es schrieb horhe:
I think this is the same bug : http://bugs.gentoo.org/326209
I have got very similar problem.
Thanks. This was the point. My Linux Kernel is grsec
enabled by default.
When i load a non grsec Kernel, then ntp works fine on ipv6.
A quick google
Hello!
Have nobody a solution or idea wat is wrong with my server?
This works:
r34210:/home/marc-andre# ntpq -p -4 127.0.0.1
remote refid st t when poll reach delay offset jitter
==
Steve Kostecke wrote:
Is the ipv6 module loaded?
IPv6 is build into the kernel.
Do any of your network interfaces hae IPv6 addresses?
Yes, i can tracert IPv6 hosts.
traceroute to www.heise.de (2a02:2e0:3fe:100::7), 30 hops max, 40 byte packets
1 2001:41d0:2:1aff:ff:ff:ff:ff 7.345 ms * *
2
On 2010-11-14, Marc-Andre Alpers m-a.alp...@web.de wrote:
Hal Murray wrote:
First, I'd check the simpler solution of does the version of ntpd he
is running support IPv6. What does netstat -ul say?
I have the same problem on my dedicated server. NTPd with IPv4 works
fine but IPv6 not.
Hal Murray wrote:
First, I'd check the simpler solution of does the version of ntpd he
is running support IPv6. What does netstat -ul say?
I have the same problem on my dedicated server. NTPd with IPv4 works fine
but IPv6 not.
Netstat shows:
udp0 0 *:ntp *:*
In article ibdgsl$40...@news.eternal-september.org,
David Woolley da...@ex.djwhome.demon.invalid writes:
joan lee wrote:
Wireshark runs on PC1 shows NTP client messages from 2002::c0a9:0102
+ are received properly, but instead of replying with NTP server messages,
+ PC1 is sending ICMPV6
I have two linux PCs, both running fedora 11 with NTP ver. 4.2.4p7.
PC1 has 192.168.1.1 and 2002::c0a9:0101 addresses
PC2 has 192.168.1.2 and 2002::c0a9:0102 addresses
ntpd is running on PC1.
on PC2 ntpdate 192.168.1.1 returned good timing from PC1
But ntpdate 2002::c0a9:0101 did not work
joan lee wrote:
Wireshark runs on PC1 shows NTP client messages from 2002::c0a9:0102
+ are received properly, but instead of replying with NTP server messages,
+ PC1 is sending ICMPV6 unreachable (administratively prohibited) messages.
Could anybody gives me some hint on why NTPD ignores the
11 matches
Mail list logo
