On Wed, Sep 23, 2015 at 11:44 PM, Kristian Evensen < [email protected]> wrote:
> On Wed, Sep 23, 2015 at 1:23 PM, Kristian Evensen > <[email protected]> wrote: > > On Wed, Sep 23, 2015 at 1:07 PM, Hans Dedecker <[email protected]> > wrote: > >> Indeed we're using source based routing in combination with a default > route > >> in the main routing table; even the specific routing table(s) can > contain a > >> default route > >> Based on the addr rule the traffic is guided to a specific routing > table so > >> it leaves on the correct interface > > I should point out that I don't know what the "correct" behavior and > how (if) this should be solved. But these patches do break earlier > working use-cases, so I am not sure what the OpenWRT-policy on this > is. > Intention of the patches was to support more scenarios like a default route in the main table. As the patches currently break some other scenarios it will need some further tweaking. The main issue is the nw rule; therefore I would like to understand which scenario the nw rule is covering before just reverting to the "old" nw rule implementation. If no route is hit in the main routing table the traffic will also be returned on the wan interface in case of the "old" nw rule implementation; so i'm wondering if this rule is ever hit in a scenario The iif lo rule stuff was originally added to fix a kernel issue; but since it's used in other scenarios they can be re-added again after the main table lookup . Meanwhile I will do some further tweaking and testing with the different scenarios in mind. Hans > > -Kristian >
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
