diff options
author | Jason McIntyre <jmc@cvs.openbsd.org> | 2006-06-15 08:55:40 +0000 |
---|---|---|
committer | Jason McIntyre <jmc@cvs.openbsd.org> | 2006-06-15 08:55:40 +0000 |
commit | 0178065b566194c67b19b4b3500bfd0ea1be975c (patch) | |
tree | 2ad4921e003a521978389dd05c8cb030bc670da5 /share/man | |
parent | a2a2ebc9164ca0c67f6a7fcca324af90bbbe02c2 (diff) |
- misplaced .El
- some wording fixes
Diffstat (limited to 'share/man')
-rw-r--r-- | share/man/man4/carp.4 | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/share/man/man4/carp.4 b/share/man/man4/carp.4 index af2ba573d18..489ead7a075 100644 --- a/share/man/man4/carp.4 +++ b/share/man/man4/carp.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: carp.4,v 1.22 2006/06/15 07:58:45 mcbride Exp $ +.\" $OpenBSD: carp.4,v 1.23 2006/06/15 08:55:39 jmc Exp $ .\" .\" Copyright (c) 2003, Ryan McBride. All rights reserved. .\" @@ -117,6 +117,7 @@ Disabled by default. .It net.inet.carp.arpbalance Balance local traffic using ARP. Disabled by default. +.El .Sh ARP LEVEL LOAD BALANCING .Nm has limited abilities for load balancing the incoming connections @@ -136,23 +137,22 @@ See the section for a practical example of load balancing. .Pp The ARP load balancing has some limitations. -First, ARP balancing only works on the local network segment. +Firstly, ARP balancing only works on the local network segment. It cannot balance traffic that crosses a router, because the router itself will always be balanced to the same virtual host. -Second, ARP load balancing can lead to asymmetric routing -of incoming and outgoing traffic, and thus combining it with +Secondly, ARP load balancing can lead to asymmetric routing +of incoming and outgoing traffic, thus combining it with .Xr pfsync 4 requires special care, because this can create a race condition between balanced routers and the host they are serving. -ARP balancing safely can be used with pfsync if the -.Xr pf -ruleset is translates the source address to an unshared address on the -outgoing interface using a nat rule. +ARP balancing can be safely used with pfsync if the +.Xr pf 4 +ruleset translates the source address to an unshared address on the +outgoing interface using a NAT rule. This requires multiple CARP groups with .Em different IP addresses on the outgoing interface, configured so that each host is the master of one group. -.El .Sh EXAMPLES For firewalls and routers with multiple interfaces, it is desirable to failover all of the |