[ovs-discuss] About open flow flow entries ( dl_dst error ( Invalid Ethernet address))

sanket raut sankets.raut at gmail.com
Mon May 4 02:40:58 UTC 2015


Hello,
My topology is as follows and I am implementing vxlan on both openvswitches
in mininet.
I had configured my tunneling end point as s1-vtep and s2-vtep.
I had used pingall command to check network connectivity, and network is
able to ping all hosts.
When I give my manual-flows by  sh ovs-ofctl add-flows s1 s1text.txt
It gives me error in dl_dst command that Ethernet address is invalid.
But it is valid mac address I'm specifying as per topology.
I'm not able to figure out what are the problem associated with dl_dst
command, and I had followed
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt rules to define my
flow table.
I had attached my python script and flow files along with this email.
So, could you please help me with the same.

[image: Inline image 2]




-- 
With Regards,

*Sanket*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20150503/96b195a5/attachment-0002.html>
-------------- next part --------------
table=0,in_port=1,actions=set_field:100->tun_id,resubmit(,1)
table=0,in_port=2,actions=set_field:200->tun_id,resubmit(,1)
table=0,in_port=3,actions=set_field:5500->tun_id,resubmit(,1)
table=0,in_port=4,actions=set_field:12000->tun_id,resubmit(,1)
table=0,actions=resubmit(,1)

table=1,tun_id=100,dl_dst=00.00.00.00.00.00.01,actions=output:1 
table=1,tun_id=200,dl_dst=00.00.00.00.00.00.02,actions=output:2 
table=1,tun_id=5500,dl_dst=00.00.00.00.00.00.03,actions=output:3
table=1,tun_id=12000,dl_dst=00.00.00.00.00.00.04,actions=output:4
table=1,tun_id=100,dl_dst=00.00.00.00.00.00.05,actions=output:10
table=1,tun_id=200,dl_dst=00.00.00.00.00.00.06,actions=output:10
table=1,tun_id=5500,dl_dst=00.00.00.00.00.00.07,actions=output:10
table=1,tun_id=12000,dl_dst=00.00.00.00.00.00.08,actions=output:10 
table=1,tun_id=100,arp,nw_dst=10.0.0.1,actions=output:1
table=1,tun_id=200,arp,nw_dst=10.0.0.2,actions=output:2
table=1,tun_id=5500,arp,nw_dst=10.0.0.3,actions=output:3
table=1,tun_id=12000,arp,nw_dst=10.0.0.4,actions=output:4 
table=1,tun_id=100,arp,nw_dst=10.0.0.5,actions=output:10 
table=1,tun_id=200,arp,nw_dst=10.0.0.6,actions=output:10 
table=1,tun_id=5500,arp,nw_dst=10.0.0.7,actions=output:10 
table=1,tun_id=12000,arp,nw_dst=10.0.0.8,actions=output:10 
table=1,priority=100,actions=drop
 
    
-------------- next part --------------
table=0,in_port=1,actions=set_field:100->tun_id,resubmit(,1)
table=0,in_port=2,actions=set_field:200->tun_id,resubmit(,1)
table=0,in_port=3,actions=set_field:5500->tun_id,resubmit(,1)
table=0,in_port=4,actions=set_field:12000->tun_id,resubmit(,1)
table=0,actions=resubmit(,1)

table=1,tun_id=100,dl_dst=00.00.00.00.00.00.05,actions=output:1 
table=1,tun_id=200,dl_dst=00.00.00.00.00.00.06,actions=output:2 
table=1,tun_id=5500,dl_dst=00.00.00.00.00.00.07,actions=output:3
table=1,tun_id=12000,dl_dst=00.00.00.00.00.00.08,actions=output:4
table=1,tun_id=100,dl_dst=00.00.00.00.00.00.01,actions=output:10
table=1,tun_id=200,dl_dst=00.00.00.00.00.00.02,actions=output:10
table=1,tun_id=5500,dl_dst=00.00.00.00.00.00.03,actions=output:10
table=1,tun_id=12000,dl_dst=00.00.00.00.00.00.04,actions=output:10 
table=1,tun_id=100,arp,nw_dst=10.0.0.5,actions=output:1
table=1,tun_id=200,arp,nw_dst=10.0.0.6,actions=output:2
table=1,tun_id=5500,arp,nw_dst=10.0.0.7,actions=output:3
table=1,tun_id=12000,arp,nw_dst=10.0.0.8,actions=output:4 
table=1,tun_id=100,arp,nw_dst=10.0.0.1,actions=output:10 
table=1,tun_id=200,arp,nw_dst=10.0.0.2,actions=output:10 
table=1,tun_id=5500,arp,nw_dst=10.0.0.3,actions=output:10 
table=1,tun_id=12000,arp,nw_dst=10.0.0.4,actions=output:10 
table=1,priority=100,actions=drop
 
    
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vx.py
Type: text/x-python
Size: 1879 bytes
Desc: not available
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20150503/96b195a5/attachment-0002.py>


More information about the discuss mailing list