Date: Thu, 11 Mar 2010 02:52:46 -0800 From: "Li, Qing" <qing.li@bluecoat.com> To: "Michael Butler" <imb@protected-networks.net> Cc: freebsd-current@freebsd.org Subject: RE: Error 127.0.0.1: no route to host Message-ID: <B583FBF374231F4A89607B4D08578A4306CE24B1@bcs-mail03.internal.cacheflow.com> In-Reply-To: <4B980347.8020500@protected-networks.net> References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com> <B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com> <B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com><4B96FD4B.3090706@FreeBSD.org> <4B978E41.4010800@protected-networks.net> <B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com> <4B980347.8020500@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>=20
> Without the route.h patch, I can't ping 127.0.0.1 or the local or
> remote address of the OpenVPN tunnel (on tap0). In fact, you=20
> can't even build OpenVPN from ports as it'll fail its self-test.
>=20
Please see my previous clarification email on the what and the why
about the "route.h.diff" patch. =20
I spent some time looking into the issue and found the problem=20
is the if_tap interface turns out to be one of those interfaces=20
that claims to be of IFT_ETHER type, but does not touch the=20
"if_link_state" variable.
>
> With the route.h patch, I can ping all local addresses but not the=20
> far end of the tunnel.
>=20
Please try the new patch at
http://people.freebsd.org/~qingli/ecmp-tap.diff
Let me know how it works out for you.
-- Qing
P.S. You really just need the 2-line fix in the if_tap.c file.
route.h is slightly touch to be (ifp) instead of just ifp in
the macro.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A4306CE24B1>