Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CSTP: Always set Legacy IP netmask to 0.0.0.0 unless split-includes r…
…eceived As described in the previous patch, we think that Cisco servers expect us to set a default Legacy IP route if no split-includes are sent. However, Cisco servers may also send another "main" Legacy IP route via X-CSTP-Netmask. As already done for GP, oNCP, and Pulse, we should shunt that other route to a split-include (unless it's a /32 route, effectively a no-op). Once this is merged, we'll be able to remove from vpnc-script the following Cisco-specific assumption: that a lack of split-includes means we must set a default Legacy IP route. Signed-off-by: Daniel Lenski <dlenski@gmail.com>
- Loading branch information
Showing
1 changed file
with
23 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters