Date: Wed, 9 Mar 2005 23:44:43 +0100 From: Guus Sliepen <guus@sliepen.eu.org> To: tinc@tinc-vpn.org Cc: freebsd-questions@freebsd.org Subject: Re: IP packets with source address of 0.0.0.0 Message-ID: <20050309224443.GB32676@sliepen.eu.org> In-Reply-To: <Pine.LNX.4.44.0502100730530.27160-100000@toybox.fyremoon.net> References: <Pine.LNX.4.44.0502100730530.27160-100000@toybox.fyremoon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <guus@sliepen.eu.org>
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050309224443.GB32676>