Blocking port udp/tcp 1433/1434

Thu May 12 20:02:56 UTC 2005

On Thu, 12 May 2005 12:23:19 CDT, John Kristoff said:

> I think there always has been some justification.  Here is a very
> small sample of real traffic that I can assure is not Slammer traffic,
> but it is being filtered nonetheless (IP addresses removed):
> 
>   May 12 09:15:30.598 CDT[...] denied udp removed(53) -> removed(1434), 1 packet
>   May 12 09:26:30.210 CDT[...] denied tcp removed(80) -> removed(1434), 1 packet
>   May 12 09:32:23.122 CDT[...] denied tcp removed(80) -> removed(1434), 1 packet
>   May 12 09:42:38.558 CDT[...] denied udp removed(123) -> removed(123), 1 packet
>   May 12 10:12:50.422 CDT[...] denied udp removed(53) -> removed(1434), 1 packet

Looks like a good justification to *NOT* filter. Somebody nuked the reply
packets for 2 DNS lookups and 2 hits to web pages just because the user's
machine picked 1434 as the ephemeral port.  Oh, and one machine that
got slapped across the face for having the temerity to ask what time it was. ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20050512/c1843b09/attachment.sig>