[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

UDP/123 policers & status

Subject: UDP/123 policers & status
From: saku at ytti.fi (Saku Ytti)
Date: Wed, 18 Mar 2020 18:10:47 +0200
In-reply-to: <CAD6AjGR42GC80iPQ4kKgyXOqGH2oN=Yshmg5yPYrL10qOVgaHg@mail.gmail.com>
References: <[email protected]> <[email protected]> <CAD6AjGRHDDG4k_xJmYEjc4abNNYn3UChcax8mTNd9RrK3pyy+A@mail.gmail.com> <[email protected]> <CAD4huA64OoFJry45YTb=H7fMZ7DAJQ7dSOihqYwOxESqWTTHGg@mail.gmail.com> <CAD6AjGR42GC80iPQ4kKgyXOqGH2oN=Yshmg5yPYrL10qOVgaHg@mail.gmail.com>

On Wed, 18 Mar 2020 at 18:05, Ca By <cb.list6 at gmail.com> wrote:

> Yeh, not changing ipv4 filters, Sorry pool. Burned once, twice shy.

On many edge routers from Juniper, Nokia and Cisco you can create
offset based bit-matches. I'm NTP illiterate, but isn't NTP mode in
fixed offset after UDP header? So it should be possible to do this in
hardware at linerate just the same as matching UDP port on typical
edge router.

-- 
  ++ytti

References:
- UDP/123 policers & status
  - From: jared at puck.nether.net (Jared Mauch)
- UDP/123 policers & status
  - From: Rich.Compton at charter.com (Compton, Rich A)
- UDP/123 policers & status
  - From: cb.list6 at gmail.com (Ca By)
- UDP/123 policers & status
  - From: mark.tinka at seacom.mu (Mark Tinka)
- UDP/123 policers & status
  - From: stevesommarsntp at gmail.com (Steven Sommars)
- UDP/123 policers & status
  - From: cb.list6 at gmail.com (Ca By)

Prev by Date: COVID-19 vs. our Networks
Next by Date: traffic sag last night (early this morning)
Previous by thread: UDP/123 policers & status
Next by thread: UDP/123 policers & status
Index(es):
- Date
- Thread