diff options
Diffstat (limited to 'network/vrrpd')
| -rw-r--r-- | network/vrrpd/README | 57 | ||||
| -rw-r--r-- | network/vrrpd/vrrpd.SlackBuild | 22 |
2 files changed, 45 insertions, 34 deletions
diff --git a/network/vrrpd/README b/network/vrrpd/README index 9dbf7a280e..d0ce0adc19 100644 --- a/network/vrrpd/README +++ b/network/vrrpd/README @@ -1,34 +1,35 @@ -VRRP daemon (vrrpd) is an RFC 2338 compliant implementation of the -Virtual Router Redundancy Protocol (VRRP). The Virtual Router Redundancy -Protocol is designed to eliminate the single point of failure associated -with statically routed networks by automatically providing failover using -multiple LAN paths through alternate routers. +VRRP daemon (vrrpd) is an RFC 2338 compliant implementation of +the Virtual Router Redundancy Protocol (VRRP). The Virtual Router +Redundancy Protocol is designed to eliminate the single point of +failure associated with statically routed networks by automatically +providing failover using multiple LAN paths through alternate routers. -As specified in RFC 2338, VRRP uses an election protocol that dynamically -assigns responsibility for a virtual router to one of the VRRP routers on -a LAN. When a VRRP router controls the IP address(es) associated with a -virtual router, it is called the Master. The Master continues to forward -packets sent to these IP addresses until it has a problem that causes the -VRRP routers to hold an election. The election process provides dynamic -failover by electing a new Master should the existing Master become -unavailable. +As specified in RFC 2338, VRRP uses an election protocol that +dynamically assigns responsibility for a virtual router to one of the +VRRP routers on a LAN. When a VRRP router controls the IP address(es) +associated with a virtual router, it is called the Master. The Master +continues to forward packets sent to these IP addresses until it has a +problem that causes the VRRP routers to hold an election. The election +process provides dynamic failover by electing a new Master should the +existing Master become unavailable. -The virtual router associated with each alternate path under VRRP uses the -same IP address and MAC address as the routers for other paths. As a result, -the host's gateway information does not change, no matter what path is used. -Because of this design, VRRP-based redundancy significantly reduces -administrative overhead when compared to redundancy schemes that require -hosts to be configured with multiple default gateways. +The virtual router associated with each alternate path under VRRP uses +the same IP address and MAC address as the routers for other paths. As +a result, the host's gateway information does not change, no matter +what path is used. Because of this design, VRRP-based redundancy +significantly reduces administrative overhead when compared to +redundancy schemes that require hosts to be configured with multiple +default gateways. -The primary function of the Virtual Router Redundancy Protocol is to provide -routing redundancy for specific IP addresses. In addition to this primary -function, RFC 2338 also states that the protocol should: +The primary function of the Virtual Router Redundancy Protocol is to +provide routing redundancy for specific IP addresses. In addition to +this primary function, RFC 2338 also states that the protocol should: * Minimize the duration of black holes. - * Minimize the steady state bandwidth overhead and processing complexity. - * Function over a variety of multiaccess LAN technologies that support IP - traffic. - * Provide for election of multiple virtual routers on a network for load - balancing. + * Minimize the steady state bandwidth overhead and processing + complexity. + * Function over a variety of multiaccess LAN technologies that support + IP traffic. + * Provide for election of multiple virtual routers on a network for + load balancing. * Support multiple logical IP subnets on a single LAN segment. - diff --git a/network/vrrpd/vrrpd.SlackBuild b/network/vrrpd/vrrpd.SlackBuild index e64cade1af..d0a05408fb 100644 --- a/network/vrrpd/vrrpd.SlackBuild +++ b/network/vrrpd/vrrpd.SlackBuild @@ -1,4 +1,4 @@ -#!/bin/sh +#!/bin/bash # Slackware build script for vrrpd @@ -22,26 +22,36 @@ # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +cd $(dirname $0) ; CWD=$(pwd) + PRGNAM=vrrpd VERSION=${VERSION:-1.0} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} +PKGTYPE=${PKGTYPE:-tgz} if [ -z "$ARCH" ]; then case "$( uname -m )" in - i?86) ARCH=i486 ;; + i?86) ARCH=i586 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac fi -CWD=$(pwd) +# If the variable PRINT_PACKAGE_NAME is set, then this script will report what +# the name of the created package would be, and then exit. This information +# could be useful to other scripts. +if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then + echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE" + exit 0 +fi + TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} -if [ "$ARCH" = "i486" ]; then - SLKCFLAGS="-O2 -march=i486 -mtune=i686" +if [ "$ARCH" = "i586" ]; then + SLKCFLAGS="-O2 -march=i586 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" @@ -91,4 +101,4 @@ mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cd $PKG -/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} +/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE |