Document double/triple matching

This commit is contained in:
Nico Schottelius 2019-03-25 11:51:36 +01:00
commit 42f5e00e74
3 changed files with 25 additions and 4 deletions

View file

@ -13,7 +13,6 @@ In other words:
should be mapped to 10.1.1.0/24
## What I tried to do
### 2 LPM keys
I tried to use one table with two LPM keys, which I would like to
@ -46,6 +45,8 @@ This results into the compiler problem
^^^^^
```
## How it could be solved
### 2 tables (recommendation of Nate)
It does not work, when matching the source address first:
@ -113,4 +114,11 @@ testing / development, it does not work for a production setup.
### Ternary matching (recommendation of Andy)
- Have to investigate
Could be a solution, because it offers priorities. Is not exactly what
I want to achieve, because I want to do LPM matching, but it could be
misused for it.
### Double table with using ID of first match (Andy + Nate ideas)
Use the handle of the source network to match again on exact in the
2nd table. This might be a very reasonable approach.