From Newsgroup: news.groups.proposals
On 25.10.2025 11:36 Uhr noel wrote:
On Fri, 24 Oct 2025 04:26:52 -0400, Marco Moock wrote:
On 24.10.2025 04:20 Uhr noel wrote:
Is it any wonder he's picking on technical groups when he doesnt
know the simplest of things, like configuring ntp, I refer to his
question in comp.protocols.time.ntp 2 days ago, I didnt repond
because I was too busy laughing since I no longer take that person
as serious and suspect marco is unsurprisingly being deceitful and
aiming at nuking that group as well.
Please reread my post there and reread the documentation of IBM.
Then you might see why I asked that question.
TLDR: IPv6 networks are usually specified with the /<netbits amount> notation. The mask notation is very, very uncommon and is not
documented in the IBM documentation.
That's why I asked.
Is asking questions about non-documented configuration options now
making me look stupid?
undocumented? so your ntp/ntp.conf man pages dont exist huh
On the AIX system I was working on, the manpages are not installed. As
this is not "my" system, I cannot just install stuff.
The IBM online documentation is an HTML copy of the manpages.
let me see, who "mandates" /net-bits...
It is the most common notation for IPv6 networks.
I was talking about a network and not a single address.
ntp i:p:v:6 optional i:p:v:6/96 nope
The documentation doesn't show that notation.
As to stupidity, no, not bothering to reading a man file when you
dont know it is just lazy,
Common, didn't I let you know that I read it?
Have a look at my first post, I even linked it, so you can confirm that
the IBM documentation (which looks like a slightly modified version of
https://www.ntp.org/documentation/4.2.8-series/ntp.conf/) doesn't
explain the mask option for IPv6.
The ntp.org stuff is better, as it explicitly says that the
default option is to set all bits.
The IBM documentation says it defaults to 255.255.255.255, which only
makes sense for IPv4.
but you run ipv6 on debian and (or did)
slackware, so you would know how to configure ntp already,
I was never in need to use the restrict option there.
On Debian, I don't even use ntpd, as the system comes with timesyncd by default, which fits my need to sync the RTC with a remote server.
especially since you went to great pains to tell us in slackware that
you dont run ipv4.
I do have some systems that don't have IPv4 connectivity, mostly test
systems.
Is there any problem with that?
I noticed you failed to address the other comments, in particular
from Kev, but I guess it doesnt suite you, you'd rather try bury it
in noise.
I now replied to that.
--
kind regards
Marco
Send spam to
1761384991muell@stinkedores.dorfdsl.de
--- Synchronet 3.21a-Linux NewsLink 1.2