tcpdrop(8) for DragonFly

Matthew Dillon dillon at
Sun Nov 14 11:55:14 PST 2004

:Matthew Dillon said:
:>     It sounds like the sysctl should have two options, but at least for
:>     any initial implementation it should use shutdown rather then drop.
:>     There are plenty of ways to deal with TIME_WAIT that would not impose
:>     much additional overhead verses a drop.
:Would you prefer this option to be set by the caller of the sysctl, or
:should a new sysctl be added (something like "net.inet.tcp.drop_action"),
:which would cause soshutdown() or soabort() depending on it's value?

    I think two separate sysctl's.  I didn't review the code well enough to
    know how the sysctl mechanism is supposed to work, but on the face of it
    it seems that simply having two sysctl's, one whos action is to drop
    and one whos action is to shutdown, would be the easiest mod.

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Submit mailing list