On 2015/12/01 15:05, Mark Felder wrote: > Notice how almost all of them are port 123 on both sides, but a few of > them are not. Why? The RFC says that NTP is supposed to be using port > 123 as both the source and destination port, but I clearly have > something happening on port 16205. Is something screwy with ntpd in > CURRENT?
NTP not using port 123 as the source port usually indicates that it is
behind a NAT gateway at the other end. It's harmless and fairly common.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
