Date: Tue, 24 Mar 2009 15:38:26 -0600 From: Brett Glass <brett@lariat.net> To: "Luiz Otavio O Souza" <lists.br@gmail.com>, "Li, Qing" <qing.li@bluecoat.com> Cc: net@freebsd.org Subject: Re: Problems with inward PPTP tunnel Message-ID: <200903242138.PAA27632@lariat.net> In-Reply-To: <0DC74661A0F84C5EA642A274E0CEF595@adnote989> References: <200903222114.PAA17884@lariat.net> <87153F88702C4FBCA3FC799082960C45@adnote989> <B583FBF374231F4A89607B4D08578A4303928C88@bcs-mail03.internal.cacheflow.com> <5E03C21CD6544D23B4E4A61E85C7E2C8@adnote989> <B583FBF374231F4A89607B4D08578A43039B2E9A@bcs-mail03.internal.cacheflow.com> <0DC74661A0F84C5EA642A274E0CEF595@adnote989>
next in thread | previous in thread | raw e-mail | index | archive | help
>Qing, > >Sorry, but your patch doesn't fix the issue, everytime the >route_UpdateMTU* is called the route is set to the ethernet >interface using the gateway address instead of the correct tun interface. > >The patch in PR works exactly in that situation as confirmed by Brett. > >Thanks, >Luiz > >* This will happen every time you provide ppp over ethernet (pppoe, vpns) Qing: I can confirm that Luiz' patch does work. I applied it and was able to disable my workaround. The only thing I would change is that I would turn off the "gateway" flag (RTF_GATEWAY) in the routing table entry. (You suggested this, implicitly, when you mentioned using the -iface flag.) This is because the "tun" interface is really a bridge, not a gateway. --Brett Glass
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903242138.PAA27632>