1. 11 10月, 2007 2 次提交
    • D
      [IPV4]: Add ICMPMsgStats MIB (RFC 4293) · 96793b48
      David L Stevens 提交于
      Background: RFC 4293 deprecates existing individual, named ICMP
      type counters to be replaced with the ICMPMsgStatsTable. This table
      includes entries for both IPv4 and IPv6, and requires counting of all
      ICMP types, whether or not the machine implements the type.
      
      These patches "remove" (but not really) the existing counters, and
      replace them with the ICMPMsgStats tables for v4 and v6.
      It includes the named counters in the /proc places they were, but gets the
      values for them from the new tables. It also counts packets generated
      from raw socket output (e.g., OutEchoes, MLD queries, RA's from
      radvd, etc).
      
      Changes:
      1) create icmpmsg_statistics mib
      2) create icmpv6msg_statistics mib
      3) modify existing counters to use these
      4) modify /proc/net/snmp to add "IcmpMsg" with all ICMP types
              listed by number for easy SNMP parsing
      5) modify /proc/net/snmp printing for "Icmp" to get the named data
              from new counters.
      Signed-off-by: NDavid L Stevens <dlstevens@us.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      96793b48
    • E
      [NET]: Make the device list and device lookups per namespace. · 881d966b
      Eric W. Biederman 提交于
      This patch makes most of the generic device layer network
      namespace safe.  This patch makes dev_base_head a
      network namespace variable, and then it picks up
      a few associated variables.  The functions:
      dev_getbyhwaddr
      dev_getfirsthwbytype
      dev_get_by_flags
      dev_get_by_name
      __dev_get_by_name
      dev_get_by_index
      __dev_get_by_index
      dev_ioctl
      dev_ethtool
      dev_load
      wireless_process_ioctl
      
      were modified to take a network namespace argument, and
      deal with it.
      
      vlan_ioctl_set and brioctl_set were modified so their
      hooks will receive a network namespace argument.
      
      So basically anthing in the core of the network stack that was
      affected to by the change of dev_base was modified to handle
      multiple network namespaces.  The rest of the network stack was
      simply modified to explicitly use &init_net the initial network
      namespace.  This can be fixed when those components of the network
      stack are modified to handle multiple network namespaces.
      
      For now the ifindex generator is left global.
      
      Fundametally ifindex numbers are per namespace, or else
      we will have corner case problems with migration when
      we get that far.
      
      At the same time there are assumptions in the network stack
      that the ifindex of a network device won't change.  Making
      the ifindex number global seems a good compromise until
      the network stack can cope with ifindex changes when
      you change namespaces, and the like.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      881d966b
  2. 04 6月, 2007 1 次提交
  3. 20 5月, 2007 1 次提交
    • P
      [IPV4]: icmp: fix crash with sysctl_icmp_errors_use_inbound_ifaddr · d8cf2728
      Patrick McHardy 提交于
      When icmp_send is called on the local output path before the
      packet hits ip_output, skb->dev is not set, causing a crash
      when sysctl_icmp_errors_use_inbound_ifaddr is set. This can
      happen with the netfilter REJECT target or IPsec tunnels.
      
      Let routing decide the ICMP source address in that case, since the
      packet is locally generated there is no inbound interface and
      the sysctl should not apply.
      
      The option actually seems to be unfixable broken, on the path
      after ip_output() skb->dev points to the outgoing device and
      we don't know the incoming device anymore, so its going to do
      the absolute wrong thing and pick the address of the outgoing
      interface. Add a comment about this.
      
      Reported by Curtis Doty <Curtis@GreenKey.net>.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d8cf2728
  4. 26 4月, 2007 4 次提交
  5. 11 2月, 2007 1 次提交
  6. 03 12月, 2006 2 次提交
  7. 29 9月, 2006 5 次提交
  8. 23 9月, 2006 3 次提交
  9. 01 7月, 2006 1 次提交
  10. 18 6月, 2006 1 次提交
  11. 11 4月, 2006 1 次提交
  12. 25 3月, 2006 1 次提交
    • I
      [IPV4]: Aggregate route entries with different TOS values · cef2685e
      Ilia Sotnikov 提交于
      When we get an ICMP need-to-frag message, the original TOS value in the
      ICMP payload cannot be used as a key to look up the routes to update.
      This is because the TOS field may have been modified by routers on the
      way.  Similarly, ip_rt_redirect should also ignore the TOS as the router
      that gave us the message may have modified the TOS value.
      
      The patch achieves this objective by aggregating entries with different
      TOS values (but are otherwise identical) into the same bucket.  This
      makes it easy to update them at the same time when an ICMP message is
      received.
      
      In future we should use a twin-hashing scheme where teh aggregation
      occurs at the entry level.  That is, the TOS goes back into the hash
      for normal lookups while ICMP lookups will end up with a node that
      gives us a list that contains all other route entries that differ
      only by TOS.
      Signed-off-by: NIlia Sotnikov <hostcc@gmail.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      cef2685e
  13. 14 2月, 2006 1 次提交
  14. 05 2月, 2006 1 次提交
  15. 03 2月, 2006 1 次提交
  16. 10 1月, 2006 1 次提交
  17. 04 1月, 2006 1 次提交
  18. 30 11月, 2005 1 次提交
  19. 11 11月, 2005 1 次提交
    • H
      [NET]: Detect hardware rx checksum faults correctly · fb286bb2
      Herbert Xu 提交于
      Here is the patch that introduces the generic skb_checksum_complete
      which also checks for hardware RX checksum faults.  If that happens,
      it'll call netdev_rx_csum_fault which currently prints out a stack
      trace with the device name.  In future it can turn off RX checksum.
      
      I've converted every spot under net/ that does RX checksum checks to
      use skb_checksum_complete or __skb_checksum_complete with the
      exceptions of:
      
      * Those places where checksums are done bit by bit.  These will call
      netdev_rx_csum_fault directly.
      
      * The following have not been completely checked/converted:
      
      ipmr
      ip_vs
      netfilter
      dccp
      
      This patch is based on patches and suggestions from Stephen Hemminger
      and David S. Miller.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fb286bb2
  20. 26 10月, 2005 1 次提交
  21. 04 10月, 2005 1 次提交
  22. 30 8月, 2005 2 次提交
  23. 19 8月, 2005 1 次提交
  24. 09 8月, 2005 1 次提交
  25. 09 7月, 2005 1 次提交
  26. 14 6月, 2005 1 次提交
    • J
      [IPV4]: Sysctl configurable icmp error source address. · 1c2fb7f9
      J. Simonetti 提交于
      This patch alows you to change the source address of icmp error
      messages. It applies cleanly to 2.6.11.11 and retains the default
      behaviour.
      
      In the old (default) behaviour icmp error messages are sent with the ip
      of the exiting interface.
      
      The new behaviour (when the sysctl variable is toggled on), it will send
      the message with the ip of the interface that received the packet that
      caused the icmp error. This is the behaviour network administrators will
      expect from a router. It makes debugging complicated network layouts
      much easier. Also, all 'vendor routers' I know of have the later
      behaviour.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1c2fb7f9
  27. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4