1. 06 3月, 2010 3 次提交
  2. 04 3月, 2010 1 次提交
    • T
      gre: fix hard header destination address checking · 6d55cb91
      Timo Teräs 提交于
      ipgre_header() can be called with zero daddr when the gre device is
      configured as multipoint tunnel and still has the NOARP flag set (which is
      typically cleared by the userspace arp daemon).  If the NOARP packets are
      not dropped, ipgre_tunnel_xmit() will take rt->rt_gateway (= NBMA IP) and
      use that for route look up (and may lead to bogus xfrm acquires).
      
      The multicast address check is removed as sending to multicast group should
      be ok.  In fact, if gre device has a multicast address as destination
      ipgre_header is always called with multicast address.
      Signed-off-by: NTimo Teras <timo.teras@iki.fi>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6d55cb91
  3. 03 3月, 2010 1 次提交
  4. 27 2月, 2010 1 次提交
  5. 25 2月, 2010 6 次提交
  6. 23 2月, 2010 1 次提交
  7. 20 2月, 2010 1 次提交
    • E
      net: Fix sysctl restarts... · 88af182e
      Eric W. Biederman 提交于
      Yuck.  It turns out that when we restart sysctls we were restarting
      with the values already changed.  Which unfortunately meant that
      the second time through we thought there was no change and skipped
      all kinds of work, despite the fact that there was indeed a change.
      
      I have fixed this the simplest way possible by restoring the changed
      values when we restart the sysctl write.
      
      One of my coworkers spotted this bug when after disabling forwarding
      on an interface pings were still forwarded.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      88af182e
  8. 19 2月, 2010 4 次提交
  9. 18 2月, 2010 1 次提交
  10. 17 2月, 2010 6 次提交
  11. 16 2月, 2010 2 次提交
  12. 15 2月, 2010 3 次提交
  13. 13 2月, 2010 2 次提交
  14. 12 2月, 2010 1 次提交
  15. 11 2月, 2010 7 次提交