From owner-freebsd-net@FreeBSD.ORG Fri Feb 12 17:15:08 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 221AB106568B for ; Fri, 12 Feb 2010 17:15:08 +0000 (UTC) (envelope-from gumbo@bsdmail.org) Received: from imr-da03.mx.aol.com (imr-da03.mx.aol.com [205.188.105.145]) by mx1.freebsd.org (Postfix) with ESMTP id D08888FC12 for ; Fri, 12 Feb 2010 17:15:07 +0000 (UTC) Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imr-da03.mx.aol.com (8.14.1/8.14.1) with ESMTP id o1CHEofj002806 for ; Fri, 12 Feb 2010 12:14:50 -0500 Received: from gumbo@bsdmail.org by imo-da04.mx.aol.com (mail_out_v42.9.) id n.ceb.73cfcfcb (34929) for ; Fri, 12 Feb 2010 12:14:44 -0500 (EST) Received: from smtprly-db02.mx.aol.com (smtprly-db02.mx.aol.com [205.188.249.153]) by cia-da04.mx.aol.com (v127.7) with ESMTP id MAILCIADA042-5bca4b758c773ce; Fri, 12 Feb 2010 12:14:43 -0500 Received: from web-mmc-m03 (web-mmc-m03.sim.aol.com [64.12.224.136]) by smtprly-db02.mx.aol.com (v127.7) with ESMTP id MAILSMTPRLYDB021-5bca4b758c773ce; Fri, 12 Feb 2010 12:14:31 -0500 References: <8CC796E5FBF77EA-2B00-1FEE@web-mmc-m03.sysops.aol.com> <20100212.054440.00550279.hrs@allbsd.org> <8CC798334B50596-2B00-26B5@web-mmc-m03.sysops.aol.com> To: freebsd-net@freebsd.org Date: Fri, 12 Feb 2010 12:14:31 -0500 X-AOL-IP: 98.207.201.67 In-Reply-To: <8CC798334B50596-2B00-26B5@web-mmc-m03.sysops.aol.com> X-MB-Message-Source: WebUI MIME-Version: 1.0 From: gumbo@bsdmail.org X-MB-Message-Type: User X-Mailer: Mail.com Webmail 30746-STANDARD Received: from 98.207.201.67 by web-mmc-m03.sysops.aol.com (64.12.224.136) with HTTP (WebMailUI); Fri, 12 Feb 2010 12:14:31 -0500 Message-Id: <8CC7A1DF9B06ECC-2B00-4C4D@web-mmc-m03.sysops.aol.com> X-Spam-Flag: NO X-AOL-SENDER: gumbo@bsdmail.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: re: problems using gif tunnels X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2010 17:15:08 -0000 The following configuration should reproduce the problem. node01 ifconfig em1 alias 10.66.0.1/24 ifconfig gif0 create ifconfig gif0 tunnel 10.66.0.1 10.66.0.2 ifconfig gif0 10.7.223.1 10.7.223.2 netmask 255.255.255.255 ifconfig gif1 create ifconfig gif1 tunnel 10.66.0.1 10.66.0.3 ifconfig gif1 10.7.224.1 10.7.224.3 netmask 255.255.255.255 ifconfig gif2 create ifconfig gif2 tunnel 10.66.0.1 10.66.0.4 ifconfig gif2 10.7.225.1 10.7.225.4 netmask 255.255.255.255 =20 node02 ifconfig em1 alias 10.66.0.2/24 ifconfig gif0 create ifconfig gif0 tunnel 10.66.0.2 10.66.0.1 ifconfig gif0 10.7.223.2 10.7.223.1 netmask 255.255.255.255 =20 Start a ping on node02 and see that it's woking.=20 ping -I 10.7.223.2 224.0.0.5 =20 Bring down gif2 on node01. ifconfig gif2 down =20 The ping on node02 no longer sees responses. This happens consistently. -----Original Message----- From: Hiroki Sato To: gumbo@bsdmail.org Cc: freebsd-net@FreeBSD.org Sent: Thu, Feb 11, 2010 12:44 pm Subject: Re: problems using gif tunnels gumbo@bsdmail.org wrote in <8CC796E5FBF77EA-2B00-1FEE@web-mmc-m03.sysops.aol.com>: gu> I am running two nodes with freebsd 7.2 release on both. u> node 1 has three gifs with tunnels configured on all. The first gif has= a=20 unnel to node 2. u> Node two has one gif with a tunnel to node 1 configured. If I start a= =20 ulticast ping from u> node 2 to the inner address of node 1 gif0, everything is fine. If I= then=20 ring down gif2 on u> node 1, the ping receives no more responses. The down gif should have= no=20 ffect on the u> ping. Has anyone seen this problem ? What's going on ? Is this a kno= wn=20 ug ? Can you show a way to reproduce your symptom by using command lines you entered, for example? -- Hiroki