1. 11 7月, 2007 6 次提交
  2. 24 6月, 2007 1 次提交
  3. 19 6月, 2007 1 次提交
    • N
      [IPVS]: Fix state variable on failure to start ipvs threads · cc0191ae
      Neil Horman 提交于
      ip_vs currently fails to reset its ip_vs_sync_state variable if the
      sync thread fails to start properly.  The result is that the kernel
      will report a running daemon when their actuall is none.
      
      If you issue the following commands:
      
      1. ipvsadm --start-daemon master --mcast-interface bla
      2. ipvsadm -L --daemon
      3. ipvsadm --stop-daemon master
      
      Assuming that bla is not an actual interface, step 2 should return no
      data, but instead returns:
      
      $ ipvsadm -L --daemon
      master sync daemon (mcast=bla, syncid=0)
      Signed-off-by: NNeil Horman <nhorman@tuxdriver.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      cc0191ae
  4. 16 6月, 2007 2 次提交
  5. 15 6月, 2007 1 次提交
  6. 13 6月, 2007 3 次提交
  7. 09 6月, 2007 3 次提交
  8. 08 6月, 2007 11 次提交
  9. 04 6月, 2007 4 次提交
  10. 31 5月, 2007 5 次提交
  11. 25 5月, 2007 3 次提交
    • D
      [XFRM]: Allow packet drops during larval state resolution. · 14e50e57
      David S. Miller 提交于
      The current IPSEC rule resolution behavior we have does not work for a
      lot of people, even though technically it's an improvement from the
      -EAGAIN buisness we had before.
      
      Right now we'll block until the key manager resolves the route.  That
      works for simple cases, but many folks would rather packets get
      silently dropped until the key manager resolves the IPSEC rules.
      
      We can't tell these folks to "set the socket non-blocking" because
      they don't have control over the non-block setting of things like the
      sockets used to resolve DNS deep inside of the resolver libraries in
      libc.
      
      With that in mind I coded up the patch below with some help from
      Herbert Xu which provides packet-drop behavior during larval state
      resolution, controllable via sysctl and off by default.
      
      This lays the framework to either:
      
      1) Make this default at some point or...
      
      2) Move this logic into xfrm{4,6}_policy.c and implement the
         ARP-like resolution queue we've all been dreaming of.
         The idea would be to queue packets to the policy, then
         once the larval state is resolved by the key manager we
         re-resolve the route and push the packets out.  The
         packets would timeout if the rule didn't get resolved
         in a certain amount of time.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      14e50e57
    • J
    • P
      [NETFILTER]: nf_conntrack_ftp: fix newline sequence number calculation · 25b86e05
      Patrick McHardy 提交于
      When the packet size is changed by the FTP NAT helper, the connection
      tracking helper adjusts the sequence number of the newline character
      by the size difference. This is wrong because NAT sequence number
      adjustment happens after helpers are called, so the unadjusted number
      is compared to the already adjusted one.
      
      Based on report by YU, Haitao <yuhaitao@tsinghua.org.cn>
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      25b86e05