Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Mar 2009 18:24:56 -0300
From:      "Luiz Otavio O Souza" <lists.br@gmail.com>
To:        "Li, Qing" <qing.li@bluecoat.com>
Cc:        Brett Glass <brett@lariat.net>, Qing Li <qingli@freebsd.org>, net@freebsd.org
Subject:   Re: Problems with inward PPTP tunnel
Message-ID:  <0DC74661A0F84C5EA642A274E0CEF595@adnote989>
References:  <200903222114.PAA17884@lariat.net> <87153F88702C4FBCA3FC799082960C45@adnote989> <B583FBF374231F4A89607B4D08578A4303928C88@bcs-mail03.internal.cacheflow.com> <5E03C21CD6544D23B4E4A61E85C7E2C8@adnote989> <B583FBF374231F4A89607B4D08578A43039B2E9A@bcs-mail03.internal.cacheflow.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>>
>> Yes i've read your patch, but i don't understand what you are
meaning...
>> and yes, changing the definition of rt_Update is not my first
intention,
>> but it is the way i've found to fix this.
>>
>> Backing to the patch... The rt_Update need the ifp and ifa information
>> to correctly update the route, and this is available only in
>> route_UpdateMTU (wich read the current route table).
>>
>> You are suggesting that this information could be found at
>> sa[RTAX_GATEWAY] (if sa[RTAX_GATEWAY]->sa_family == AF_LINK) ? And i
>> don't need to pass the sa[RTAX_IFP] and sa[RTAX_IFA] ?
>>
>
> Yes. The concept should be similar to the handling code for route
> insertion
> where one does, e.g.:
>
> route add -net a.b.c.d/24 -iface em0
>
> Joe Marcus verified my patch in his environment. My suggestion is for
> you
> to try it out and see if that patch also fixes whatever problem that you
> are
> running into.
>

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) 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0DC74661A0F84C5EA642A274E0CEF595>