diff options
author | Martin Willi <martin@strongswan.org> | 2006-05-10 07:32:34 +0000 |
---|---|---|
committer | Martin Willi <martin@strongswan.org> | 2006-05-10 07:32:34 +0000 |
commit | bc4a07a0adc9e31af75576477fbed488c31edaa4 (patch) | |
tree | 82a8ba5612c448b8db585b437fbbe38ef243a0ba /linux/lib/libfreeswan/rangetosubnet.3 | |
parent | 37a2b616e28649b6db7c87e96b375ba1176b52cc (diff) | |
download | strongswan-bc4a07a0adc9e31af75576477fbed488c31edaa4.tar.bz2 strongswan-bc4a07a0adc9e31af75576477fbed488c31edaa4.tar.xz |
- started to rebuild source layout
Diffstat (limited to 'linux/lib/libfreeswan/rangetosubnet.3')
-rw-r--r-- | linux/lib/libfreeswan/rangetosubnet.3 | 59 |
1 files changed, 0 insertions, 59 deletions
diff --git a/linux/lib/libfreeswan/rangetosubnet.3 b/linux/lib/libfreeswan/rangetosubnet.3 deleted file mode 100644 index 7d707545e..000000000 --- a/linux/lib/libfreeswan/rangetosubnet.3 +++ /dev/null @@ -1,59 +0,0 @@ -.TH IPSEC_RANGETOSUBNET 3 "8 Sept 2000" -.\" RCSID $Id: rangetosubnet.3,v 1.1 2004/03/15 20:35:26 as Exp $ -.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 |