Thanks for the report.
Since matching on IP addresses in ARPs is an optional switch feature, I don't
think it's 100% clear what the function should do, but I don't object to the
idea that it should probably just extract the addresses. I'll add it to my
queue.
-- Murphy
On Jan 9, 2012, at 6:28 AM, Peter Peresini wrote:
> Hi,
> it seems that util.py extract_flow in destiny branch is not
> consistent with install_datapath_flow. I tried to install a flow
> extracted from a packet and the resulting match failed to capture the
> same packet stream.
> More precisely, if a packet is an ARP packet, extract_flow returns
> following attributes:
>
> {'dl_type': 2054, 'nw_dst': 0, 'dl_vlan_pcp': 0, 'dl_src': array('B',
> [0, 0, 0, 0, 0, 11]), 'nw_proto': 1, 'nw_tos': 0, 'tp_dst': 0,
> 'tp_src': 0, 'dl_dst': array('B', [255, 255, 255, 255, 255, 255]),
> 'dl_vlan': 65535, 'nw_src': 0}
>
> Now If I install the flow using these attributes, the switch still
> forwards the packets to the controller. I experimentally found that
>
> del match[core.NW_DST]
> del match[core.NW_SRC]
>
> solves the problem. According to the
> http://www.openflow.org/wk/index.php/OpenFlow_1.0_release_notes#Match_on_IP_fields_in_ARP_packets
> it seems that nw_src and nw_dst should contain actual IPs from ARP and
> not zeroes.
>
> Kind regards
> Peter Peresini
> _______________________________________________
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev
