Re: [Ntp] Fw: NTS Hackathon coordination

Miroslav Lichvar <mlichvar@redhat.com> Fri, 29 March 2019 09:14 UTC

Return-Path: <mlichvar@redhat.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7A3120261 for <ntp@ietfa.amsl.com>; Fri, 29 Mar 2019 02:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kv-zRsrvAywy for <ntp@ietfa.amsl.com>; Fri, 29 Mar 2019 02:14:54 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9633112023E for <ntp@ietf.org>; Fri, 29 Mar 2019 02:14:54 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 49DDF3082E4F; Fri, 29 Mar 2019 09:14:53 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 89BCF5C226; Fri, 29 Mar 2019 09:14:52 +0000 (UTC)
Date: Fri, 29 Mar 2019 10:14:50 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: "Gary E. Miller" <gem@rellim.com>
Cc: ntp@ietf.org
Message-ID: <20190329091450.GA7264@localhost>
References: <20190328143019.503451aa@spidey.rellim.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20190328143019.503451aa@spidey.rellim.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Fri, 29 Mar 2019 09:14:53 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ZqLXPXgodJGdU862wwsq_LfYhEY>
Subject: Re: [Ntp] Fw: NTS Hackathon coordination
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2019 09:14:57 -0000

On Thu, Mar 28, 2019 at 02:30:19PM -0700, Gary E. Miller wrote:
> Yo All!
> 
> Anyone else seeing issues with nts-test.strangled.net:443 ?
> 
> 3 NTPsec servers, running the same code, only on gets NTPD from
> nts-test.  See below.

Hm, it looks like a bug in the firewall configuration. It was
disabling connection tracking for packets using port 123 (as is
normally needed on a public server), but that included also responses
from the NTS server, which is running in a container with a private
address, so the responses had a wrong source address.

It should be fixed now.

I still see some clients sending requests with increasing size up to
540 bytes, so I'm not sure if they don't like the shorter responses or
they are getting lost somewhere.

-- 
Miroslav Lichvar