| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
The write_lock call fails with EDEADLK and unlocks in the
next recursion level.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Initialization is now static.
|
| |
|
|
|
|
|
| |
Due to the new lifetime limits in- and outbound SAs may expire
individually.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also adjusted the jitter calculation, so it works for values > RAND_MAX.
|
| |
|
|
|
|
| |
calculations
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The default lifetime of 30 seconds is too short, as a tunnel
setup may need several minutes if we have high packet loss. Instead
of increasing the value, we disable lifetimes completely, as we handle
the removal of such SAs from userland just fine.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
enums mutex/condvar/rwlock_type_t.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
lifetime when installing the policy.
|
| |
|
| |
|
|
|
|
|
| |
This helps in cases where a policy is assigned to more than one SA. That
is, SAs now should have different usetimes even if they use the same policy.
|
| |
|
| |
|