[56025] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: [Re: [Re: M$SQL cleanup incentives]]

daemon@ATHENA.MIT.EDU (Bryan Bradsby)
Fri Feb 21 15:09:22 2003

Date: Fri, 21 Feb 2003 14:08:46 -0600 (CST)
From: Bryan Bradsby <Bryan.Bradsby@capnet.state.tx.us>
To: Joshua Smith <joshua.ej.smith@usa.net>
Cc: "Gary E. Miller" <gem@rellim.com>, <nanog@merit.edu>
In-Reply-To: <663HBuRtP5712S06.1045849515@cmsweb06.cms.usa.net>
Errors-To: owner-nanog-outgoing@merit.edu


> > udp/1434 is not a reserved port. [...] legit
> > traffic that picked a random port to use for an ad-hoc use.
>
> it isn't legit for what i have in my network though :-)


Really? So you're blocking udp/1434 both in and out?

Got any DNS servers on your network? Any of your desktop clients use DNS?

Recent versions of un*x BIND will pick a random port above 1024 for udp
conversations. It can and has picked 1434.

DNS clients will eventually timeout and fall back to another server, so
any problems would be transient, but the packets were legit, right?


-bryan bradsby
Texas State Government Net




home help back first fref pref prev next nref lref last post