Windows NodePort Service doesn't work if the traffic is sent out from the local Pod

[wenyingd]

Describe the bug
Orignally, the global vMAC is used as a mark to ensure OVS could rewrite the packet's MAC with the real value when matching local Pod's IP address in the L3Routing table. After Antrea Proxy is enabled, a new mark in reg0[19] is used for such target.

On Windows Nodes, an OpenFlow entry is added in the Classifier table to ensure that the packet sent from the Node's IP (not from the local gateway) interface to the local Pod could enter OVS pipeline, and be forwarded to the target Pod finally. This flow entry is still using the global vMAC but doesn't set the new mark, hence the packet matching this flow entry could not rewrite DMAC with the correct MAC.

To Reproduce

1. Create a NodePort Service
2. Create a client Pod, and ensure it is located on the same Node the Service's backend Pod
3. Access the NodePort Service from the client, using the Node's IP as destination on which the client Pod is located.

Expected
The client Pod could get a correct reply the Service's backend Pod

Actual behavior
The NodePortService traffic doesn't work.

Versions:
Please provide the following information:

• Antrea version (Docker image tag): 0.8.0/0.8.1