From owner-freebsd-questions@FreeBSD.ORG Wed Mar 9 22:44:48 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AD1216A4CE for ; Wed, 9 Mar 2005 22:44:47 +0000 (GMT) Received: from 214pc223.sshunet.nl (214pc223.sshunet.nl [145.97.223.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id C779B43D54 for ; Wed, 9 Mar 2005 22:44:46 +0000 (GMT) (envelope-from guus@sliepen.eu.org) Received: from xar.sliepen.oi (guus@localhost [127.0.0.1]) j29Miim3020915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Mar 2005 23:44:44 +0100 Received: (from guus@localhost) by xar.sliepen.oi (8.13.3/8.13.3/Submit) id j29MihT8020914; Wed, 9 Mar 2005 23:44:43 +0100 Date: Wed, 9 Mar 2005 23:44:43 +0100 From: Guus Sliepen To: tinc@tinc-vpn.org Message-ID: <20050309224443.GB32676@sliepen.eu.org> Mail-Followup-To: Guus Sliepen , tinc@tinc-vpn.org, jadz@toybox.fyremoon.net, freebsd-questions@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IrhDeMKUP4DT/M7F" Content-Disposition: inline In-Reply-To: X-oi: oi User-Agent: Mutt/1.5.6+20040907i cc: jadz@toybox.fyremoon.net cc: freebsd-questions@freebsd.org Subject: Re: IP packets with source address of 0.0.0.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 22:44:48 -0000 --IrhDeMKUP4DT/M7F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 10, 2005 at 07:57:15AM +0000, jadz@toybox.fyremoon.net wrote: > I've had a quick look at the routing table and everything is fine there. = =20 > Using tcpdump on one of the other vpn sites confirms the packets are=20 > getting to it, so they are being routed over the vpn correctly: >=20 > # tcpdump -i tap0=20 > tcpdump: listening on tap0 > 08:44:24.847529 0.0.0.0 > 10.0.3.1: icmp: echo request > 08:44:25.803251 0.0.0.0 > 10.0.3.1: icmp: echo request > 08:44:26.818328 0.0.0.0 > 10.0.3.1: icmp: echo request > 08:44:27.822987 0.0.0.0 > 10.0.3.1: icmp: echo request > 08:44:28.841233 0.0.0.0 > 10.0.3.1: icmp: echo request That is a tcpdump on the receiving end, but can you also do a tcpdump on the sending side? Also, could you try if the problem persists with tinc 1.0= =2E3? --=20 Met vriendelijke groet / with kind regards, Guus Sliepen --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCL3xbAxLow12M2nsRAnjHAJsEoTODE2t2l6LIIyxNXuur1w3vvwCfV8r9 kPay4bjG8bUc6DXBclCL8HA= =Drx1 -----END PGP SIGNATURE----- --IrhDeMKUP4DT/M7F--