| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
| |
As forwarding policies are not available on all systems (OS X), using the
forward policy to attach the route is a bad pick. Using input policies allows
OS X to install routes.
|
|
|
|
|
| |
It seems that we don't get address notifications if the interface is down
on OS X.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This lets the kernel backend decide what to do with it, and in fact all kernel
interfaces already handle this correctly.
|
|
|
|
|
| |
It seems that the order of binding sockets of different address families to the
same dynamic port must be v6-before-v4 on Linux, but v4-before-v6 on OS X.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The compiler spits no warning, but the wrong symbol is used when calling
semaphore_create() from strongSwan. Override the name with a #define to force
the use of our semaphore_create().
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The value is set only if it is not configured in strongswan.conf or has
not been set() otherwise.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Controller functions are thread cancellation points, so register a cancellation
handler cleaning up job data.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|