On Wed, Apr 27, 2022 at 09:15:15AM +0200, Sven Auhagen wrote: > When creating a flow table entry, the reverse route is looked > up based on the current packet. > There can be scenarios where the user creates a custom ip rule > to route the traffic differently. > In order to support those scenarios, the lookup needs to add > more information based on the current packet. > The patch adds multiple new information to the route lookup. Applied, thanks
