Re: FIN_WAIT_2

From: Robert Gogolok (robertgogolok_at_web.de)
Date: 03/22/05

  • Next message: Chris Tusa at Linisys, LLC: "Re: PPP Lan Bridge" 
    Date: Tue, 22 Mar 2005 23:47:58 +0100
To: freebsd-net@freebsd.org

    http://lists.freebsd.org/mailman/htdig/freebsd-ipfw/2003-May/000204.html
    is the same problem or similar problem.
    Forgot to mention thge important fact I use ipfw, bad bad...

    With
    # sysctl net.inet.ip.fw.dyn_keepalive=0
    the FIN_WAIT_2 connections cleaned all up within a few minutes.

    Robert

    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Chris Tusa at Linisys, LLC: "Re: PPP Lan Bridge"

    Relevant Pages

    • Re: IPFW ignoring verbose_limit ?
      ... I've just discovered that IPFW was logging messages to ... I've tried to lower the limit to 5 but IPFW just kept logging away ... I think that the sysctl setting you're ... referring to only applies to repetitions of log output for each unique ...
      (comp.unix.bsd.freebsd.misc)
    • Re: RELENG_5 kernel b0rken with IPFIREWALL and without PFIL_HOOKS
      ... > ipfw be a module, ... it is failing because the net.inet.ip.fw.enable sysctl was removed. ... script needs to be updated to rely on one of the still existing sysctls. ... Professional Web Design ...
      (freebsd-current)
    • Re: Fw: FIN_WAIT_2
      ... It appears that inn certain conditions, when the net.inet.ip.fw.dyn_keepalive=1 (sysctl), remote clients or other ... and a new rule or dynamic rule is setup. ... I expect it virtually shut down dynamic rules too in ipfw, ...
      (freebsd-questions)
    • Re: RELENG_5 kernel b0rken with IPFIREWALL and without PFIL_HOOKS
      ... > Barney Wolff wrote: ... >> that ipfw be a module, ... > it is failing because the net.inet.ip.fw.enable sysctl was removed. ... > script needs to be updated to rely on one of the still existing sysctls. ...
      (freebsd-current)
    • Re: RELENG_5 kernel b0rken with IPFIREWALL and without PFIL_HOOKS
      ... > Barney Wolff wrote: ... >> that ipfw be a module, ... > it is failing because the net.inet.ip.fw.enable sysctl was removed. ... > script needs to be updated to rely on one of the still existing sysctls. ...
      (freebsd-current)