Bug 948306

Description of problem:
I'm new to VPN and IPSec so I could be mistaken, but the strongswan package appears to operate as an alternative to ipsec-tools but maintains it's own filesystem names, e.g. "ipsec"=="strongswan".
The issue is with the default iptables up/down script invocation, which defaults to the command "ipsec _updown iptables" rather than "strongswan _updown iptables".

Version-Release number of selected component (if applicable):
strongswan-5.0.0-3.git20120619.fc18.x86_64

How reproducible:
Default configuration.

Steps to Reproduce:
1. Install strongswan as the sole VPN/IPSec.
2. Configure a VPN with leftfirewall=yes
3. "Up" the connection.
  
Actual results:
No firewall rules injected.

Expected results:
Firewall rules.

Additional info:
Can probably work around with explicit ipsec.conf setting 'leftupdown="strongswan _updown iptables"'.

Use "alternatives" to maintain symbolic links (/usr/sbin/strongswan --> ipsec)? Might make the documentation easier to navigate too. Could also handle /etc/strongswan/ipsec.d --> /etc/ipsec.d.

Modify the hard-coded default script definition in the source to use the value from 'configure'? - src/starter/confread.c, line 41:
+++
static const char firewall_defaults[] = "ipsec _updown iptables";
---