Date: Sat, 8 Oct 2011 12:25:35 +0200 From: Vlad Galu <dudu@dudu.ro> To: "Li, Qing" <qing.li@bluecoat.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, "liv3d@multiplay.co.uk" <liv3d@multiplay.co.uk>, Steven Hartland <killing@multiplay.co.uk> Subject: Re: serious packet routing issue causing ntpd high load? Message-ID: <CA%2BFTnKMVy_XoUE9-cJrLgx-NSLNAjysztDUPnEVx48ceeZH%2B9g@mail.gmail.com> In-Reply-To: <B143A8975061C446AD5E29742C53172313BC17@PWSVL-EXCMBX-01.internal.cacheflow.com> References: <2740DA0E7C0F495BA00E6D4BC0FE8F37@multiplay.co.uk> <B143A8975061C446AD5E29742C53172313BC17@PWSVL-EXCMBX-01.internal.cacheflow.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 6, 2011 at 1:32 AM, Li, Qing <qing.li@bluecoat.com> wrote: [...] I'm seeing this as well. It's very easy to reproduce: 1. Start listening for routing messages on a non-default FIB, e.g. setfib 2 route monitor 2. Add any static route within that FIB. 3. The machine I run the test on is a heavy DNS client, it generates a few dozen requests per second. The monitor process starts getting RTM_MISS messages for each outgoing DNS request (the dst sockaddr is the same as my first resolv.conf entry, seq is always 0). -- Good, fast & cheap. Pick any two.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BFTnKMVy_XoUE9-cJrLgx-NSLNAjysztDUPnEVx48ceeZH%2B9g>