1. 13 11月, 2010 1 次提交
  2. 01 10月, 2010 1 次提交
  3. 16 9月, 2010 1 次提交
  4. 17 2月, 2010 1 次提交
  5. 07 1月, 2010 1 次提交
    • J
      net: RFC3069, private VLAN proxy arp support · 65324144
      Jesper Dangaard Brouer 提交于
      This is to be used together with switch technologies, like RFC3069,
      that where the individual ports are not allowed to communicate with
      each other, but they are allowed to talk to the upstream router.  As
      described in RFC 3069, it is possible to allow these hosts to
      communicate through the upstream router by proxy_arp'ing.
      
      This patch basically allow proxy arp replies back to the same
      interface (from which the ARP request/solicitation was received).
      
      Tunable per device via proc "proxy_arp_pvlan":
        /proc/sys/net/ipv4/conf/*/proxy_arp_pvlan
      
      This switch technology is known by different vendor names:
       - In RFC 3069 it is called VLAN Aggregation.
       - Cisco and Allied Telesyn call it Private VLAN.
       - Hewlett-Packard call it Source-Port filtering or port-isolation.
       - Ericsson call it MAC-Forced Forwarding (RFC Draft).
      Signed-off-by: NJesper Dangaard Brouer <hawk@comx.dk>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      65324144
  6. 26 12月, 2009 1 次提交
    • J
      net: restore ip source validation · 28f6aeea
      Jamal Hadi Salim 提交于
      when using policy routing and the skb mark:
      there are cases where a back path validation requires us
      to use a different routing table for src ip validation than
      the one used for mapping ingress dst ip.
      One such a case is transparent proxying where we pretend to be
      the destination system and therefore the local table
      is used for incoming packets but possibly a main table would
      be used on outbound.
      Make the default behavior to allow the above and if users
      need to turn on the symmetry via sysctl src_valid_mark
      Signed-off-by: NJamal Hadi Salim <hadi@cyberus.ca>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      28f6aeea
  7. 04 12月, 2009 1 次提交
  8. 05 11月, 2009 1 次提交
  9. 28 7月, 2009 1 次提交
  10. 01 2月, 2009 1 次提交
  11. 08 10月, 2008 1 次提交
  12. 04 6月, 2008 1 次提交
  13. 26 3月, 2008 1 次提交
  14. 29 2月, 2008 1 次提交
  15. 01 2月, 2008 1 次提交
  16. 29 1月, 2008 6 次提交
  17. 23 6月, 2007 1 次提交
  18. 08 6月, 2007 3 次提交
    • H
      [IPV4]: Restore old behaviour of default config values · 71e27da9
      Herbert Xu 提交于
      Previously inet devices were only constructed when addresses are added
      (or rarely in ipmr).  Therefore the default config values they get are
      the ones at the time of these operations.
      
      Now that we're creating inet devices earlier, this changes the
      behaviour of default config values in an incompatible way (see bug
      #8519).
      
      This patch creates a compromise by setting the default values at the
      same point as before but only for those that have not been explicitly
      set by the user since the inet device's creation.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      71e27da9
    • H
      [IPV4]: Add default config support after inetdev_init · 31be3085
      Herbert Xu 提交于
      Previously once inetdev_init has been called on a device any changes
      made to ipv4_devconf_dflt would have no effect on that device's
      configuration.
      
      This creates a problem since we have moved the point where
      inetdev_init is called from when an address is added to where the
      device is registered.
      
      This patch is the first half of a set that tries to mimic the old
      behaviour while still calling inetdev_init.
      
      It propagates any changes to ipv4_devconf_dflt to those devices that
      have not had the corresponding attribute set.
      
      The next patch will forcibly set all values at the point where
      inetdev_init was previously called.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      31be3085
    • H
      [IPV4]: Convert IPv4 devconf to an array · 42f811b8
      Herbert Xu 提交于
      This patch converts the ipv4_devconf config members (everything except
      sysctl) to an array.  This allows easier manipulation which will be
      needed later on to provide better management of default config values.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      42f811b8
  19. 03 12月, 2006 1 次提交
  20. 29 9月, 2006 4 次提交
  21. 21 3月, 2006 1 次提交
  22. 04 10月, 2005 1 次提交
    • H
      [IPV4]: Replace __in_dev_get with __in_dev_get_rcu/rtnl · e5ed6399
      Herbert Xu 提交于
      The following patch renames __in_dev_get() to __in_dev_get_rtnl() and
      introduces __in_dev_get_rcu() to cover the second case.
      
      1) RCU with refcnt should use in_dev_get().
      2) RCU without refcnt should use __in_dev_get_rcu().
      3) All others must hold RTNL and use __in_dev_get_rtnl().
      
      There is one exception in net/ipv4/route.c which is in fact a pre-existing
      race condition.  I've marked it as such so that we remember to fix it.
      
      This patch is based on suggestions and prior work by Suzanne Wood and
      Paul McKenney.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e5ed6399
  23. 30 5月, 2005 1 次提交
  24. 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