You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The longest prefix matching (LPM) table of GK blocks does not accept a default route (i.e. a route for the prefix of length zero) because it uses DPDK's LPM implementation, which doesn't accept a prefix of length zero.
Given that Gatekeeper servers are expected to be BGP speaker, this may not be an issue at all, but someone may find a deployment scenario in which default routes are necessary. Thus, until this deployment scenario becomes known, this issue has very low priority.
A solution is patching DPDK to support zero-length prefixes.
The text was updated successfully, but these errors were encountered:
The old libraries rte_lpm and rte_lpm6 do not support
the zero-length prefix, but the new libraries rte_fib and
rte_fib6 do. This commit removes the previous restrictions.
This commit impacts the routing table of Gatekeeper servers, and
the LPM tables used on Lua policies.
This commit closes#91.
The old libraries rte_lpm and rte_lpm6 do not support
the zero-length prefix, but the new libraries rte_fib and
rte_fib6 do. This commit removes the previous restrictions.
This commit impacts the routing table of Gatekeeper servers, and
the LPM tables used on Lua policies.
This commit closes#91.
This commit replaces the backend libraries rte_lpm and rte_lpm6
with the new FIB library to implement the routing table.
Thanks to the new RIB and FIB libraries, the zero-length prefix
(AKA the default route) is now supported.
This commit closes#91.
This commit replaces the backend libraries rte_lpm and rte_lpm6
with the new FIB library to implement the routing table.
Thanks to the new RIB and FIB libraries, the zero-length prefix
(AKA the default route) is now supported.
This commit closes#91.
The longest prefix matching (LPM) table of GK blocks does not accept a default route (i.e. a route for the prefix of length zero) because it uses DPDK's LPM implementation, which doesn't accept a prefix of length zero.
Given that Gatekeeper servers are expected to be BGP speaker, this may not be an issue at all, but someone may find a deployment scenario in which default routes are necessary. Thus, until this deployment scenario becomes known, this issue has very low priority.
A solution is patching DPDK to support zero-length prefixes.
The text was updated successfully, but these errors were encountered: