Question/feature request: Expose forwarder for easier debugging.
Closed this issue · 1 comments
yan-foto commented
Hi everyone! @Pairarma and I, are testing integration of changes in #74 for RIOT (see my fork).
We were wondering if there are any explicit reasons not to give users access to the forwarder, mainly to be able to list fib, pit, and face entries. The current implementation allows adding faces, routes, etc. but does not allow listing them which makes debugging a real pain.
If you guys are OK with it, I can send a PR with a single function which returns a const pointer to forwarder struct.
Zhiyi-Zhang commented
The reason is for hiding the details of underlying forwarding details.
I think it's fine to have that function and yeah a PR sounds good.