Subject: RE: [RFC PATCH] network: return errors if we know tcp_connect failed

From: "Hua Zhong" <[email-masked]>
Date: Thu, 11 Nov 2010 13:58:02 -0800

> Yes, I realize this is little different than if the
> SYN was dropped in the first network device, but it is different
> because we know what happened!  We know that connect() call failed
> and that there isn't anything coming back.

I would argue that -j DROP should behave exactly as the packet is dropped in the network, while -j REJECT should signal the failure to the application as soon as possible (which it doesn't seem to do).

It does not only make sense, but also is a highly useful testing technique that we use -j DROP in OUTPUT to emulate network losses and see how the application behaves.