Re: Rejecting udp

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

 



Skip Morrow, on Tuesday, Mar  4 2003 at 12:00, wrote:
> I am trying to remember my networking class (/me shakes the cobwebs out)
> 
> I think that the original question is a good question.  UDP packets
> (legitimately) arriving at my computer are not acknowledged.  That is, I
> don't tell the sender "Yeah, I got that packet.  Thanks."  Nor, do I tell
> the sender "Whoops.  I didn't quite get all of that last packet.  Could
> you send it again?" So, REJECTing a UDP packet doesn't make sense.  The
> sender isn't looking for any type of OK message or anything for that
> matter.  In fact, where would the REJECT message go?  Does the sender even
> have a listen port open?
> 
> But then again, I could be completely wrong.

Maybe. UDP connectionless means any protocol lying on top should
implement their own connection tracking mechanism if it wants one, tftp
is an example that comes to my mind (http://www.ietf.org/rfc/rfc1350.txt
if you are curious).

I don't knwon the SMB internals, but it's wise to reject a blocked port
from inside your lan instead of let any timeouts expire, as someone
noted.

	Manuel


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux