Changes between Version 3 and Version 4 of JoeSandbox/OpenFlowNATExample/Execute


Ignore:
Timestamp:
08/27/14 13:46:12 (10 years ago)
Author:
zwang@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • JoeSandbox/OpenFlowNATExample/Execute

    v3 v4  
    113113}}}
    114114
    115 == 2 Handle ARP and ICMP ==
     115== 3 Handle ARP and ICMP ==
    116116One of very common mistakes that people make, when writing OF controller, is forgetting to handle ARP and ICMP message and finding their controller does not work as expected.
    117117
    118 === 2.1 ARP ===
     118=== 3.1 ARP ===
    119119As we mentioned before, we should insert rules into the OF switch that allow ARP packets to go through, probably after the switch is connected.
    120120
    121 === 2.2 ICMP ===
     121=== 3.2 ICMP ===
    122122Handling ARP is trivial as NAT does not involve ARP. However, it's not the case for ICMP. If you only process translation for TCP/UDP, you will find you cannot ping between `outside` and `insideX` while nc is working properly. Handling ICMP is even not as straightforward as for TCP/UDP. Because for ICMP, you cannot get port information to bind with. Our provided solution makes use of ICMP echo identifier. You may come up with different approach involves ICMP sequence number or others.
    123123