1. 14 Jun, 2008 1 commit
  2. 11 Jun, 2008 1 commit
  3. 04 Jun, 2008 3 commits
  4. 11 Apr, 2008 1 commit
    • Brian Haley's avatar
      [IPv6]: Change IPv6 unspecified destination address to ::1 for raw and un-connected sockets · 876c7f41
      Brian Haley authored
      This patch fixes a difference between IPv4 and IPv6 when sending packets
      to the unspecified address (either or ::) when using raw or
      un-connected UDP sockets.  There are two cases where IPv6 either fails
      to send anything, or sends with the destination address set to ::.  For
      --> ping -c1
      PING ( 56(84) bytes of data.
      64 bytes from icmp_seq=1 ttl=64 time=0.032 ms
      --> ping6 -c1 ::
      PING ::(::) 56 data bytes
      ping: sendmsg: Invalid argument
      Doing a sendto("") reveals:
      10:55:01.495090 IP localhost.32780 > localhost.7639: UDP, length 100
      Doing a sendto("::") reveals:
      10:56:13.262478 IP6 fe80::217:8ff:fe7d:4718.32779 > ::.7639: UDP, length 100
      If you issue a connect() first in the UDP case, it will be sent to ::1,
      similar to what happens with TCP.
      This restores the BSD-ism.
      Signed-off-by: default avatarBrian Haley <brian.haley@hp.com>
      Signed-off-by: default avatarYOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
  5. 28 Mar, 2008 4 commits
  6. 25 Mar, 2008 3 commits
  7. 24 Mar, 2008 1 commit
  8. 22 Mar, 2008 1 commit
  9. 21 Mar, 2008 1 commit
  10. 07 Mar, 2008 1 commit
  11. 06 Mar, 2008 1 commit
    • David S. Miller's avatar
      [UDP]: Revert udplite and code split. · db8dac20
      David S. Miller authored
      This reverts commit db1ed684 ("[IPV6]
      UDP: Rename IPv6 UDP files."), commit
      8be8af8f ("[IPV4] UDP: Move
      IPv4-specific bits to other file.") and commit
       ("[UDP]: Allow users to
      configure UDP-Lite.").
      First, udplite is of such small cost, and it is a core protocol just
      like TCP and normal UDP are.
      We spent enormous amounts of effort to make udplite share as much code
      with core UDP as possible.  All of that work is less valuable if we're
      just going to slap a config option on udplite support.
      It is also causing build failures, as reported on linux-next, showing
      that the changeset was not tested very well.  In fact, this is the
      second build failure resulting from the udplite change.
      Finally, the config options provided was a bool, instead of a modular
      option.  Meaning the udplite code does not even get build tested
      by allmodconfig builds, and furthermore the user is not presented
      with a reasonable modular build option which is particularly needed
      by distribution vendors.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  12. 03 Mar, 2008 2 commits
  13. 31 Jan, 2008 1 commit
  14. 28 Jan, 2008 11 commits
  15. 07 Nov, 2007 2 commits
  16. 15 Oct, 2007 1 commit
  17. 10 Oct, 2007 1 commit
  18. 14 Sep, 2007 1 commit
  19. 07 Jun, 2007 1 commit
  20. 24 May, 2007 1 commit
    • David S. Miller's avatar
      [XFRM]: Allow packet drops during larval state resolution. · 14e50e57
      David S. Miller authored
      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
      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: default avatarDavid S. Miller <davem@davemloft.net>
  21. 11 May, 2007 1 commit