++ info ++ link local

This commit is contained in:
Nico Schottelius 2019-03-19 23:21:40 +01:00
commit 2a623a0807
2 changed files with 9 additions and 4 deletions

View file

@ -113,7 +113,7 @@
| | | |
| 2019-03-21 | Meet Laurent #3 | |
| | - My dog ate my homework | |
| | | |
| | - Router solicitation for finding router on startup! | |
| | | |
| | | |
| 2019-03-30 | NAT64 1:1 table ICMP, ICMPv6 working | |
@ -770,8 +770,8 @@ DEBUG:main:OUTGOING: <Ether dst=00:00:0a:00:00:01 src=00:00:0a:00:00:42 type=0x
DEBUG:main:INCOMING: <Ether dst=00:00:0a:00:00:01 src=00:00:0a:00:00:42 type=0x86dd |<IPv6 version=6 tc=0 fl=0 plen=32 nh=ICMPv6 hlim=255 src=2001:db8::42 dst=fe80::200:aff:fe00:1 |<ICMPv6ND_NA type=Neighbor Advertisement code=0 cksum=0xa5e9 R=0 S=1 O=1 res=0x0 tgt=2001:db8::42 |<ICMPv6NDOptDstLLAddr type=2 len=1 lladdr=00:00:0a:00:00:42 |>>>>
****** Do we have a routing for fe80::/10? Probably not. Shouldn't we see it in the controller then?
****** TODO Implement address learning?
****** TODO Not sure whether we should react on router solicitation
- Using static routes -> should do the job
***** TODO Implement the calculation
***** TODO Sketch the flow for session handling for icmp6 w/o packet loss
- switch receives icmp6 packet for known prefix