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

@ -123,12 +123,16 @@
| | Parsing on wrong field detected by unset fields in wireshark | |
| | Correcting parser->leads to incorrect checksum | |
| | - NDP is answered to, but icmp6 echo request isn't -> extend table | |
| | | |
| | Problem with multiple LPM keys in table | |
| | - logical problem, overlapping length matches | |
| | - priority / ordering would be helpful | |
| | | |
| | | |
| 2019-03-25 | | |
| | Writing down double LPM problem | |
| | Removing source network support, documenting limitation | |
| | Rewriting code to use multiple NAT64 destinations | |
| | | |
| | | |
| | | |
@ -1281,7 +1285,7 @@ Code:
}
#+END_SRC
**** (current) Limitations
**** (current) Implementation limitations
***** No fragmentation support (yet)
***** No session handling (yet)
1:1 mappings. No (automatic) session.
@ -1292,6 +1296,10 @@ has already been solved in a different domain - could even do
transparent / in network modification
***** Incomplete NDP
Very limited option support
***** NAT64 mappings not source network dependent
Only the destination network is matched for deciding on NAT64, as
priority based double LPM is not supported. This limits a prefix to be
used only in one network.
*** References / Follow up
**** RFC 2460 IPv6 (Checksum https://tools.ietf.org/html/rfc2460#section-8.1)
**** RFC 3810 MLD2 https://tools.ietf.org/html/rfc3810