diff options
author | Tobias Brunner <tobias@strongswan.org> | 2012-05-15 16:59:00 +0200 |
---|---|---|
committer | Tobias Brunner <tobias@strongswan.org> | 2012-06-11 17:33:32 +0200 |
commit | fff4b74db26968bac72ade4bd6c702be7b51ec7a (patch) | |
tree | f101045942fa34c0c93e9b828def87778feacb11 /src/libfreeswan/rangetosubnet.3 | |
parent | 4a54860986e34f46183eebe60d7af767de7ddf25 (diff) | |
download | strongswan-fff4b74db26968bac72ade4bd6c702be7b51ec7a.tar.bz2 strongswan-fff4b74db26968bac72ade4bd6c702be7b51ec7a.tar.xz |
Bye bye Pluto!
Charon will take over IKEv1 duties from here. This also removes
libfreeswan and whack.
Diffstat (limited to 'src/libfreeswan/rangetosubnet.3')
-rw-r--r-- | src/libfreeswan/rangetosubnet.3 | 58 |
1 files changed, 0 insertions, 58 deletions
diff --git a/src/libfreeswan/rangetosubnet.3 b/src/libfreeswan/rangetosubnet.3 deleted file mode 100644 index 100b42bd9..000000000 --- a/src/libfreeswan/rangetosubnet.3 +++ /dev/null @@ -1,58 +0,0 @@ -.TH IPSEC_RANGETOSUBNET 3 "8 Sept 2000" -.SH NAME -ipsec rangetosubnet \- convert address range to subnet -.SH SYNOPSIS -.B "#include <freeswan.h>" -.sp -.B "const char *rangetosubnet(const ip_address *start," -.ti +1c -.B "const ip_address *stop, ip_subnet *dst);" -.SH DESCRIPTION -.I Rangetosubnet -accepts two IP addresses which define an address range, -from -.I start -to -.I stop -inclusive, -and converts this to a subnet if possible. -The addresses must both be IPv4 or both be IPv6, -and the address family of the resulting subnet is the same. -.PP -.I Rangetosubnet -returns NULL for success and -a pointer to a string-literal error message for failure; -see DIAGNOSTICS. -.SH SEE ALSO -ipsec_initsubnet(3), ipsec_ttosubnet(3) -.SH DIAGNOSTICS -Fatal errors in -.I rangetosubnet -are: -mixed address families; -unknown address family; -.I start -and -.I stop -do not define a subnet. -.SH HISTORY -Written for the FreeS/WAN project by Henry Spencer. -.SH BUGS -The restriction of error reports to literal strings -(so that callers don't need to worry about freeing them or copying them) -does limit the precision of error reporting. -.PP -The error-reporting convention lends itself -to slightly obscure code, -because many readers will not think of NULL as signifying success. -A good way to make it clearer is to write something like: -.PP -.RS -.nf -.B "const char *error;" -.sp -.B "error = rangetosubnet( /* ... */ );" -.B "if (error != NULL) {" -.B " /* something went wrong */" -.fi -.RE |