Observed behaviour:
When net.inet.ip.fastforwarding=1 is active, packets destined for remote EIDs are not being encapsulated in LISP, but instead are fastforwarded to the default gateway according to the routing table.
Expected behaviour:
Packets destined for remote EIDs are being encapsulated in LISP, even if net.inet.ip.fastforwarding=1
Note
I suspect that fastforward processes packets before the lisp data-plane hook in the kernel
I'm far from being really confident with BSD or LISP even, so this is just pure speculation.
Considerations
Therefore the fastforward feature is not really to blame, however this should either be
a) changed so that lisp hooks before fastforward, if possible
b) very well documented/pointed out, so that one cannot miss it, and/or even change some default behaviour
I.e. set the fastforward knob automatically to 0 when using lisp, remove it completly with the lisp installation, or emit some log messages if its active
Observed behaviour: When net.inet.ip.fastforwarding=1 is active, packets destined for remote EIDs are not being encapsulated in LISP, but instead are fastforwarded to the default gateway according to the routing table.
Expected behaviour: Packets destined for remote EIDs are being encapsulated in LISP, even if net.inet.ip.fastforwarding=1
Note I suspect that fastforward processes packets before the lisp data-plane hook in the kernel I'm far from being really confident with BSD or LISP even, so this is just pure speculation.
Considerations Therefore the fastforward feature is not really to blame, however this should either be a) changed so that lisp hooks before fastforward, if possible b) very well documented/pointed out, so that one cannot miss it, and/or even change some default behaviour I.e. set the fastforward knob automatically to 0 when using lisp, remove it completly with the lisp installation, or emit some log messages if its active