From exim@www1.ietf.org  Wed Dec  3 18:43:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16355
	for <vrrp-archive@odin.ietf.org>; Wed, 3 Dec 2003 18:43:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARgeT-00022C-4w
	for vrrp-archive@odin.ietf.org; Wed, 03 Dec 2003 18:43:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3NhPCI007816
	for vrrp-archive@odin.ietf.org; Wed, 3 Dec 2003 18:43:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARgeT-00021z-1Y
	for vrrp-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 18:43:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16335
	for <vrrp-web-archive@ietf.org>; Wed, 3 Dec 2003 18:43:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARgeP-0004Ic-00
	for vrrp-web-archive@ietf.org; Wed, 03 Dec 2003 18:43:21 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARgeP-0004IV-00
	for vrrp-web-archive@ietf.org; Wed, 03 Dec 2003 18:43:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARge4-0001xy-N4; Wed, 03 Dec 2003 18:43:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARgds-0001uV-U4
	for vrrp@optimus.ietf.org; Wed, 03 Dec 2003 18:42:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16305
	for <vrrp@ietf.org>; Wed, 3 Dec 2003 18:42:30 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARgdp-0004Hz-00
	for vrrp@ietf.org; Wed, 03 Dec 2003 18:42:45 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARgdo-0004Hv-00
	for vrrp@ietf.org; Wed, 03 Dec 2003 18:42:44 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hB3NghV25238
	for <vrrp@ietf.org>; Thu, 4 Dec 2003 01:42:43 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T664b4f76edac158f24060@esvir04nok.ntc.nokia.com>;
 Thu, 4 Dec 2003 01:42:43 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Wed, 3 Dec 2003 15:42:41 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Dec 2003 17:42:41 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABE27@daebe009.americas.nokia.com>
Thread-Topic: VMAC vs ND for VRRPv3
Thread-Index: AcO580bqUaYdv9czTFm2R9l7EOJaZwAAraqQ
To: <dprovan@bivio.net>, <vrrp@ietf.org>
X-OriginalArrivalTime: 03 Dec 2003 23:42:41.0764 (UTC) FILETIME=[248AC240:01C3B9F7]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] RE: VMAC vs ND for VRRPv3
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Thanks Don.=20

This could have been used this as yet another argument=20
for using ND instead of VMACs in the meeting but this is=20
still useful to know.

Regards
Mukesh

> -----Original Message-----
> From: ext Don Provan [mailto:dprovan@bivio.net]
> Sent: Wednesday, December 03, 2003 3:15 PM
> To: vrrp@ietf.org
> Cc: Gupta Mukesh (IPRG/MtView)
> Subject: RE: VMAC vs ND for VRRPv3
>=20
>=20
> Mukesh asked me to look into whether the problems with ARP
> implementations in IPv4 has been cleared up in IPv6's Neighbor
> Discovery mechanism. (I think he wanted this in time for November's
> meeting...oh, well.) I've finally gotten a chance to look into it.
>=20
> First of all, it's very clear that the problem of IPv4 ARP
> implementations ignoring unsolicited MAC address changes was
> understood and addressed in the ND work. RFC-2461 has an entire
> section (7.2.6., "Sending Unsolicited Neighbor Advertisements", p 64)
> describing when and how a node recognizing a change in the MAC layer
> address should convey that information to other nodes in the
> environment. In addition, a careful reading of the previous section
> (7.2.5., "Receipt of Neighbor Advertisements", starting on p 62) will
> ultimately lead one to the fact that an unsolicited advertisement
> MUST update the link-layer address.
>=20
> In short, handling MAC address updates is a well specified and
> unmistakable requirement for ND implementations.
>=20
> The downside is an ND concept called "Neighbor Unreachability
> Detection". This requires that a newly learned MAC address be
> confirmed reachable. This can be accomplished by an upper layer such
> as TCP seeing an event which tells it that one of its packets has been
> sent over the new path, but it could fall to ND itself to confirm the
> reachability using a unicast solicitation/advertisement exchange.
>=20
> So a MAC change might trigger a two packet exchange with all
> neighbors, but reachability has to be confirmed every 30 seconds or
> so, anyway, so the additional traffic triggered by one MAC change will
> be insignificant compared to the background of such exchanges.
>=20
> I claim that the old IPv4 ARP problem can no longer be used as a
> justification of the VMAC in VRRPv3. There may still be other reasons
> we might want to use VMACs to keep the burden of changing paths in
> the layer 2 switches, but unreliable ND implementations in layer 3
> components does not appear to be one of them.
>=20
> -don provan
> dprovan@bivio.net
>=20

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Dec  9 11:01:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01276
	for <vrrp-archive@odin.ietf.org>; Tue, 9 Dec 2003 11:01:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATkIT-0002bU-Hv
	for vrrp-archive@odin.ietf.org; Tue, 09 Dec 2003 11:01:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9G1DG0010007
	for vrrp-archive@odin.ietf.org; Tue, 9 Dec 2003 11:01:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATkIT-0002bK-EN
	for vrrp-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 11:01:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01222
	for <vrrp-web-archive@ietf.org>; Tue, 9 Dec 2003 11:00:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATkIQ-00022q-00
	for vrrp-web-archive@ietf.org; Tue, 09 Dec 2003 11:01:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATkIQ-00022l-00
	for vrrp-web-archive@ietf.org; Tue, 09 Dec 2003 11:01:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATkIG-0002ZZ-V0; Tue, 09 Dec 2003 11:01:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATkHp-0002YN-3R
	for vrrp@optimus.ietf.org; Tue, 09 Dec 2003 11:00:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01191
	for <vrrp@ietf.org>; Tue, 9 Dec 2003 11:00:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATkHm-00021d-00
	for vrrp@ietf.org; Tue, 09 Dec 2003 11:00:30 -0500
Received: from heini.fbbwu.fh-lueneburg.de ([193.174.21.2] helo=rzserv1-sud.fhnon.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATkHl-00021a-00
	for vrrp@ietf.org; Tue, 09 Dec 2003 11:00:29 -0500
Received: from ws150 (luenecom.cgw.lg.de.bcc-ip.net [212.68.66.238])
	by rzserv1-sud.fhnon.de (8.11.7+Sun/8.11.6) with ESMTP id hB9G0SW20777
	for <vrrp@ietf.org>; Tue, 9 Dec 2003 17:00:28 +0100 (MET)
To: vrrp@ietf.org
From: =?iso-8859-1?Q?Philipp_P=E4per?= <philipp-paeper@stud-sud.fhnon.de>
Content-Type: text/plain; format=flowed; charset=iso-8859-1
MIME-Version: 1.0
Date: Tue, 09 Dec 2003 17:00:47 +0100
Message-ID: <oprzw73liv5k8ho8@mail.stud-sud.fhnon.de>
User-Agent: Opera7.23/Linux M2 build 518
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by rzserv1-sud.fhnon.de id hB9G0SW20777
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] no failover until making some traffic (ping)
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

hi,
here is a short description of the system:

debian woody (+sarge or sid)
quagga for ospf
vrrpd 0.72

network plan
                             ^
                             |
			          |
		          +~~~~~~~~~~~~+
        	  ####    |  159.102   |   #### VRRP
                      /| virtual ip |\
                     / +~~~~~~~~~~~~+ \
                 (1)/                  \(2)
                   /                    \
                  /                      \
       10.0.200.2/                        \10.0.200.1
         +------+                          +------+
#####   | gw11 |                          | gw14 |    ##### OSPF
         +------+\                         +------+
    170.1 |       \170.5
          |        \
          |         \
          |          \
    170.2 |           \170.6
       +------+170.10  +------+
       | gw12 |--------| gw13 |
       +------+   170.9+------+
          |
          |
          |
        170.64/26


there'll be a connection between gw14 and gw13 in future (it is a=20
test-network)...
ospf works fine...

gw11 should be the active (vrrp) router and gw14 the backup.

gw11:
  vrrpd -i eth1 -v 1 -p 150 x.x.159.102

gw14:
  vrrpd -i eth0 -v 2 -p 100 x.x.159.102

i hope that's ok

so if i remove wire (1) gw14 should become the aktive router, but it=20
doesn't until gw14 makes some traffic (ping x.x.159.101).

the ping on x.x.159.102 gets down, when removing the wire and first get u=
p=20
again, if i make a ping from gw14

and gw11 also doesn't become the active router again, if i plugin the wir=
e=20
(or du i have to do this by hand?)

regards,
  philipp p=E4per

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Tue Dec  9 15:51:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16490
	for <vrrp-archive@odin.ietf.org>; Tue, 9 Dec 2003 15:51:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATopD-0000lc-DU
	for vrrp-archive@odin.ietf.org; Tue, 09 Dec 2003 15:51:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9KpJrp002944
	for vrrp-archive@odin.ietf.org; Tue, 9 Dec 2003 15:51:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATopD-0000lP-8r
	for vrrp-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 15:51:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16392
	for <vrrp-web-archive@ietf.org>; Tue, 9 Dec 2003 15:51:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATopB-0000UG-00
	for vrrp-web-archive@ietf.org; Tue, 09 Dec 2003 15:51:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATopA-0000U1-00
	for vrrp-web-archive@ietf.org; Tue, 09 Dec 2003 15:51:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AToow-0000jr-FB; Tue, 09 Dec 2003 15:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AToof-0000jV-G1
	for vrrp@optimus.ietf.org; Tue, 09 Dec 2003 15:50:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16338
	for <vrrp@ietf.org>; Tue, 9 Dec 2003 15:50:29 -0500 (EST)
From: Mukesh.Gupta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATood-0000TE-00
	for vrrp@ietf.org; Tue, 09 Dec 2003 15:50:44 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATooc-0000T9-00
	for vrrp@ietf.org; Tue, 09 Dec 2003 15:50:43 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hB9Kof824583
	for <vrrp@ietf.org>; Tue, 9 Dec 2003 22:50:41 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6669981fa7ac158f25139@esvir05nok.ntc.nokia.com>;
 Tue, 9 Dec 2003 22:50:41 +0200
Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 9 Dec 2003 14:50:16 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Dec 2003 14:50:16 -0600
Message-ID: <8D260779A766FB4A9C1739A476F84FA42ABE33@daebe009.americas.nokia.com>
Thread-Topic: VMAC vs ND.
Thread-Index: AcO+k83WpJhoH71pSg6wZIOUwq8TtAAAML5g
To: <myth@ucx.lkg.dec.com>
Cc: <Bob.Hinden@nokia.com>, <vrrp@ietf.org>
X-OriginalArrivalTime: 09 Dec 2003 20:50:16.0821 (UTC) FILETIME=[0CF43A50:01C3BE96]
Content-Transfer-Encoding: quoted-printable
Subject: [VRRP] Proposed changes to VRRPv3
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Group,

Mark had proposed the following changes (in addition to the
VMAC replacement) to the VRRPv3 draft during his presentation=20
in the WG meeting.

1) Bag "MUST NOT" answer ping if prio<255
2) Listen/audit VRRP packets when prio=3D255
3) Accept VRRP packets with wrong interval

I think, all these changes have been discussed on the mailing list.
They were considered useful and I didn't see any objections. So
lets incorporate them in the next version of the draft.

The question is:

- Was there anything else that came up on the mailing list and
  seemed like a useful change ? (Did I miss anything ??)

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Fri Dec 12 15:44:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25544
	for <vrrp-archive@odin.ietf.org>; Fri, 12 Dec 2003 15:44:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu92-0007ln-Gi
	for vrrp-archive@odin.ietf.org; Fri, 12 Dec 2003 15:44:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCKiGT4029861
	for vrrp-archive@odin.ietf.org; Fri, 12 Dec 2003 15:44:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu92-0007lY-BN
	for vrrp-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 15:44:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25532
	for <vrrp-web-archive@ietf.org>; Fri, 12 Dec 2003 15:44:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu90-00003B-00
	for vrrp-web-archive@ietf.org; Fri, 12 Dec 2003 15:44:14 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu90-000032-00
	for vrrp-web-archive@ietf.org; Fri, 12 Dec 2003 15:44:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu8n-0007kC-Sv; Fri, 12 Dec 2003 15:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu8S-0007jU-8t
	for vrrp@optimus.ietf.org; Fri, 12 Dec 2003 15:43:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25507
	for <vrrp@ietf.org>; Fri, 12 Dec 2003 15:43:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu8P-00002O-00
	for vrrp@ietf.org; Fri, 12 Dec 2003 15:43:37 -0500
Received: from ns1.slums.de ([213.133.101.8] helo=bronson.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu8O-00001k-00
	for vrrp@ietf.org; Fri, 12 Dec 2003 15:43:37 -0500
Received: from localhost (diva [127.0.0.1])
	by bronson.de (Postfix) with ESMTP id B6ACA33E6B
	for <vrrp@ietf.org>; Fri, 12 Dec 2003 21:43:01 +0100 (CET)
Received: from bronson.de ([127.0.0.1])
 by localhost (diva [127.0.0.1:10024]) (amavisd-new) with ESMTP id 09570-01
 for <vrrp@ietf.org>; Fri, 12 Dec 2003 21:42:30 +0100 (CET)
Received: from prometheus.int.slums.dyndns.org (dsl-213-023-037-196.arcor-ip.net [213.23.37.196])
	by bronson.de (Postfix) with ESMTP id DE3D333E6C
	for <vrrp@ietf.org>; Fri, 12 Dec 2003 21:42:29 +0100 (CET)
Received: by prometheus.int.slums.dyndns.org (Postfix, from userid 501)
	id 0DE74C266C; Fri, 12 Dec 2003 21:42:31 +0100 (CET)
Date: Fri, 12 Dec 2003 21:42:31 +0100
From: Nik Engel <vrrp@bronson.de>
To: vrrp list <vrrp@ietf.org>
Message-ID: <20031212204231.GJ20963@prometheus.int.slums.dyndns.org>
Reply-To: vrrp@bronson.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Organization: Slums
Organisation: Slums ** Wir haben immer Zeit **  
X-Operating-System: Darwin 7.0.0 Power Macintosh
Orgaisation: Netways Gmbh =?iso-8859-1?Q?N=C3rnberg?=
X-Virus-Scanned: by amavisd-new
Subject: [VRRP] Redundant Firewallsetup
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>

Hello all ! 
I want to use vrrp to setup an redundant firewall system under Linux. 
Is it gernerally possible ? How can the layout look like ? 
Do I need additional hubs, where do I find more dokumentation on the
project? 

thanks 
Nik Engel


_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



From exim@www1.ietf.org  Fri Dec 12 22:56:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11667
	for <vrrp-archive@odin.ietf.org>; Fri, 12 Dec 2003 22:56:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AV0sz-0000OH-Nq
	for vrrp-archive@odin.ietf.org; Fri, 12 Dec 2003 22:56:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBD3u9Af001495
	for vrrp-archive@odin.ietf.org; Fri, 12 Dec 2003 22:56:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AV0sz-0000O2-49
	for vrrp-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 22:56:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11661
	for <vrrp-web-archive@ietf.org>; Fri, 12 Dec 2003 22:56:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AV0sv-00021w-00
	for vrrp-web-archive@ietf.org; Fri, 12 Dec 2003 22:56:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AV0sv-00021t-00
	for vrrp-web-archive@ietf.org; Fri, 12 Dec 2003 22:56:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AV0ss-0000Mq-Ho; Fri, 12 Dec 2003 22:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AV0sM-0000M6-Ky
	for vrrp@optimus.ietf.org; Fri, 12 Dec 2003 22:55:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11653
	for <vrrp@ietf.org>; Fri, 12 Dec 2003 22:55:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AV0sJ-000219-00
	for vrrp@ietf.org; Fri, 12 Dec 2003 22:55:27 -0500
Received: from [66.150.197.45] (helo=vbind.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AV0sI-000216-00
	for vrrp@ietf.org; Fri, 12 Dec 2003 22:55:26 -0500
Received: from localhost (va-purceville1d-20.chvlva.adelphia.net [24.51.157.20])
	by vbind.com (8.11.6/8.11.6) with ESMTP id hBD3tPi13963;
	Fri, 12 Dec 2003 22:55:25 -0500
Date: Fri, 12 Dec 2003 22:55:21 -0500
From: Allan Liska <allan@allan.org>
X-Mailer: The Bat! (v1.62r) Personal
Reply-To: Allan Liska <allan@allan.org>
X-Priority: 3 (Normal)
Message-ID: <1816681487.20031212225521@allan.org>
To: Nik Engel <vrrp@bronson.de>
CC: vrrp list <vrrp@ietf.org>
Subject: Re: [VRRP] Redundant Firewallsetup
In-Reply-To: <20031212204231.GJ20963@prometheus.int.slums.dyndns.org>
References: <20031212204231.GJ20963@prometheus.int.slums.dyndns.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: vrrp-admin@ietf.org
Errors-To: vrrp-admin@ietf.org
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vrrp>,
	<mailto:vrrp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5

Hello Nik,

Friday, December 12, 2003, 3:42:31 PM, you wrote:

NE> Hello all !
NE> I want to use vrrp to setup an redundant firewall system under Linux.
NE> Is it gernerally possible ? How can the layout look like ?
NE> Do I need additional hubs, where do I find more dokumentation on the
NE> project?

VRRP is generally not used for firewall failover, because it does not
maintain state.  If you are not worried about maintaining state, and
simply want one firewall to become active in the event the other one
fails then VRRP is the answer.

As to how to implement it, that depends on your firewall vendor.
Nokia, Cisco, and Netscreen all have good tutorials on their websites,
so you probably want to check them out.  If you are simply using
IPTables on top of Linux take a look at keepalived
(http://keepalived.sourceforge.net/) or one of the other VRRP-based
daemons for Linux.

Hope this helps.


allan
- --
Allan Liska
allan@allan.org

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQCVAwUAP9qNrikg6TAvIBeFAQEntQP7B0Z5Bmjl/ZmDFaVPslUrEQPOD4EpHHEK
+L6/AyRgH9TvC4vEN2wRwngqWOUhy2PKal/Q41muIP0ZqA5034iTxMb2MOsFWyzI
cRYRbnB+636ykuZA4mL0uuihfzOwqeM/b0hjbZoTt4xO45e5XY3xQDoukmMJB7Np
9C4FTrb1EF4=
=lXCf
-----END PGP SIGNATURE-----



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp



