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)
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
