scripts/vyatta-vpn-op.pl                                         |  102 
++++++++--
 templates/clear/vpn/ipsec-peer/node.def                          |    1 
 templates/clear/vpn/ipsec-peer/node.tag/node.def                 |    6 
 templates/clear/vpn/ipsec-peer/node.tag/tunnel/node.def          |    1 
 templates/clear/vpn/ipsec-peer/node.tag/tunnel/node.tag/node.def |   10 
 templates/clear/vpn/ipsec-process/node.def                       |    2 
 templates/show/vpn/debug/detail/node.def                         |    2 
 templates/show/vpn/debug/node.def                                |    2 
 8 files changed, 109 insertions(+), 17 deletions(-)

New commits:
commit 92a42fb741210a774309ceb8da438e005d80421f
Author: Mohit Mehta <[email protected]>
Date:   Fri Oct 9 16:59:53 2009 -0700

    * Fix Bug 4017 Add the ability to restart individual IPSec tunnels
      added new operational mode commands -
    
      clear vpn ipsec-peer peer <peer> # clear all tunnels for given peer
      clear vpn ipsec-peer peer <peer> tunnel <tunnel> # clear specific tunnel
    
      If peer is 0.0.0.0/any/@id then tunnel is brought down and loaded again
      but connection is not initiated as remote end could be multiple end-points
      The remote ends will bring up the tunnel when they get/detect tunnel down
    
    * don't call script with sudo from templates. use sudo in script where 
needed
    * script clean up

http://suva.vyatta.com/git/?p=vyatta-op-vpn.git;a=commitdiff;h=92a42fb741210a774309ceb8da438e005d80421f
_______________________________________________
svn mailing list
[email protected]
http://mailman.vyatta.com/mailman/listinfo/svn

Reply via email to