nico/master-thesis
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove / replace default route on ipv4 hosts

Browse source
This commit is contained in:
Nico Schottelius 2019-03-31 10:51:47 +02:00
commit c5a3be5ccf
2 changed files with 20 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

26
doc/plan.org
View file

@ -168,29 +168,35 @@
| 2019-03-30 | | |
| | Refactoring code | |
| | Hitting expression bug | |
| | Translating TO icmp4 works! | |
| | | |
| | | |
| 2019-03-30 | NAT64 1:1 table ICMP, ICMPv6 working | |
| 2019-04-04 | NAT64 1:1 table ICMP, ICMPv6 working | |
| | Will need some switch local ip addresses | |
| | | |
| | | |
| 2019-04-12 | NAT64 1:1 table TCP/UDP working | |
| 2019-04-18 | NAT64 1:1 table TCP/UDP working | |
| | | |
| | | |
| 2019-03-29 | Jool SIIT / range / offset support https://www.jool.mx/en/run-vanilla.html | |
| 2019-05-02 | Jool SIIT / range / offset support https://www.jool.mx/en/run-vanilla.html | |
| | Jool EAMT support https://www.jool.mx/en/run-eam.html | |
| | Bidirectional support | |
| | Will need IPv6 embedding suport https://tools.ietf.org/html/rfc6052 | |
| | | |
| 2019-04-05 | NAT64 prefix based IPv6->IPv4 conversion [tayga] | |
| 2019-04-18 | NAT64 prefix based IPv6->IPv4 conversion [tayga] | |
| | Use case: IPv6 hosts send to specific /96 | |
| | | |
| 2019-04-19 | NAT64 dynamic pool implementation: n:m ipv6 to ipv4 mapping | |
| 2019-05-23 | NAT64 dynamic pool implementation: n:m ipv6 to ipv4 mapping | |
| | And n:1 stateful mappings https://www.jool.mx/en/run-nat64.html | |
| | Needs active controller | |
| | Needs timeout / leases | |
| | | |
| 2019-05-10 | Benmarking results between P4, Jool, Tayga | |
| 2018-06-27 | | |
| | Target Hardware: code running | |
| | | |
| | | |
| | | |
| 2019-07-25 | Benmarking results between P4, Jool, Tayga | |
| | Real hardware of advantage | |
| | | |
| | | |
@ -547,7 +553,7 @@ rtt min/avg/max/mdev = 6.304/6.304/6.304/0.000 ms
#+END_SRC
***** TODO try4: h3 receives packet, but length seems to be off
***** DONE try4: h3 receives packet, but length seems to be off
- Seeing frame check sequence error
- total length ipv4 = 69 (h3)
- ipv6 payload length = 64 (h1)
@ -592,6 +598,12 @@ rtt min/avg/max/mdev = 6.304/6.304/6.304/0.000 ms
****** TODO Correct ICMP header checksum
****** TODO Fix length issue
- Seems like total_len is too short - but why?
***** DONE try5: packet is good, but routing is "strange": default route == 10.0.0.66
root@ubuntu:~# ip r
default via 10.0.0.66 dev h3-eth0
10.0.0.0/24 dev h3-eth0 proto kernel scope link src 10.0.0.1
root@ubuntu:~#
***** TODO Implement default route handling, maybe implement ARP
**** DONE Add table name support in debug messages
**** DONE Why getting IPv6 packets in
INFO:main:unhandled reassambled=<Ether dst=33:33:ff:00:00:42 src=00:00:0a:00:00:01 type=0x86dd |<IPv6 version=6 tc=0 fl=0 plen=32 nh=ICMPv6 hlim=255 src=fe80::200:aff:fe00:1 dst=ff02::1:ff00:42 |<ICMPv6ND_NS type=Neighbor Solicitation code=0 cksum=0x37df res=0 tgt=2001:db8::42 |<ICMPv6NDOptSrcLLAddr type=1 len=1 lladdr=00:00:0a:00:00:01 |>>>> from table TABLE_V6_NETWORKS

1
p4app/controller.py
View file

@ -330,6 +330,7 @@ class L2Controller(object):
log.debug("Config v4 host: {} {}->{} on {}".format(host, net, ipaddr, dev))
subprocess.call(["mx", host, "ip", "addr", "flush", "dev", dev])
subprocess.call(["mx", host, "ip", "route", "del", "default"])
subprocess.call(["mx", host, "ip", "addr", "add", ipaddr, "dev", dev])
if router: