On Tue, Oct 6, 2020 at 7:17 PM Konstantin Ananyev <konstantin.anan...@intel.com> wrote: > > Introduces two changes into l3fwd-acl behaviour to make > it behave in the same way as l3fwd: > - Add a command-line parameter to allow the user to specify the > destination mac address for each ethernet port used. > - While forwarding the packet update source and destination mac > addresses.
This new parameter is optional, but I see no default for l2 destination in the patch. How does it work when you won't set this option? Bonus question, what keeps us from merging this example with l3fwd? -- David Marchand
