Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | unity: Do not bump TS to 0.0.0.0/0 as initiator when no Split-Include received | Martin Willi | 2014-08-25 | 1 | -1/+21 |
| | | | | | | | When having the unity plugin enabled and both peers send the Unity Vendor ID, we proposed 0.0.0.0/0 as traffic selector, even if no Split-Include has been received on the SA. This can break compatibility with some responders, as they don't narrow the TS themselves, but expect the configured TS. | ||||
* | unity: Handle narrowing according to roles in the IKE_SA | Tobias Brunner | 2014-08-25 | 1 | -16/+33 |
| | | | | | | Since the narrow hook types reflect the roles in the Quick Mode exchange the plugin behaved incorrectly if the server initiated the CHILD_SA rekeying. | ||||
* | unity: Change local TS to 0.0.0.0/0 as responder | Tobias Brunner | 2014-01-23 | 1 | -4/+7 |
| | | | | | Cisco clients and Shrew expect a remote TS of 0.0.0.0/0 if Unity is used, otherwise Quick Mode fails. | ||||
* | unity: Replicate default behavior if no UNITY_SPLIT_INCLUDE attributes were ↵ | Tobias Brunner | 2013-07-17 | 1 | -11/+32 |
| | | | | received | ||||
* | As Unity responder, don't change the proposed TS at all, racoon doesn't like ↵ | Martin Willi | 2012-09-18 | 1 | -7/+4 |
| | | | | that | ||||
* | As initiator, narrow received Unity attributes to configured TS | Martin Willi | 2012-09-18 | 1 | -4/+11 |
| | |||||
* | When using Unity, bump up remote TS as initiator to 0.0.0.0/0, too | Martin Willi | 2012-09-18 | 1 | -5/+8 |
| | |||||
* | Enable Cisco Unity only if Unity vendor id received | Martin Willi | 2012-09-18 | 1 | -1/+2 |
| | |||||
* | Exchange 0.0.0.0/0 traffic selectors with Unity, narrowing after exchange | Martin Willi | 2012-09-18 | 1 | -22/+87 |
| | |||||
* | Check if subset calculation actually yields a TS in Unity narrowing | Martin Willi | 2012-09-18 | 1 | -1/+5 |
| | |||||
* | Add Cisco Unity client support for Split-Include and Local-LAN | Martin Willi | 2012-09-18 | 1 | -0/+94 |