Re: [ovs-discuss] VXLAN under OVS

2014-09-23 Thread Ben Pfaff
On Wed, Sep 24, 2014 at 11:07:06AM +1000, Jaime Pillora wrote: > #switch 1 > sh ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan > option:remote_ip=172.16.4.1 option:key=flow ofport_request=11 > sh ovs-ofctl add-flow s1 'in_port=11,tun_id=2,actions=output:1' > sh ovs-ofctl add-flow s1 'in_

Re: [ovs-discuss] Karaf feature repository names

2014-09-23 Thread Lori Jakab
Really sorry about the below email, wrong list, I missed autocomplete changing the To: field. -Lori On 9/23/14 2:14 PM, Lori Jakab wrote: Hi, I know there is a policy of naming ODL features with the "odl-" prefix. I didn't see a policy for feature repository names, but I think it should be

[ovs-discuss] Karaf feature repository names

2014-09-23 Thread Lori Jakab
Hi, I know there is a policy of naming ODL features with the "odl-" prefix. I didn't see a policy for feature repository names, but I think it should be the same. There are a few ODL repositories without the "odl-" prefix: opendaylight-user@root>feature:repo-list | grep Helium | grep -v od

Re: [ovs-discuss] VXLAN under OVS

2014-09-23 Thread Ben Pfaff
On Mon, Sep 22, 2014 at 11:13:45AM +1000, Jaime Pillora wrote: > I???ve added a VXLAN ports to vx1,2 to bridges s1,2 and it seems only the > first VXLAN port I create works. Is this a bug or am I only able to use one > VXLAN port for each OVS instance? It's probably a configuration error. How did

[ovs-discuss] A Question About How to Capture and Modify OpenFlow Message Body in Open vSwitch

2014-09-23 Thread Vivien X.W. Liu
Hi, I am currently working on a project that needs to use Open vSwitch, and modify the body of every OpenFlow message that is sent back and forward between the SDN controller and the Open vSwitch (body here means the rest of the bits in an OpenFlow message except the 8 bytes OpenFlow message heade

Re: [ovs-discuss] ping problem between internal port and netdev port

2014-09-23 Thread ychen
Another similar question: p0: type=internal, tag=100, vlan_mode=access, ip=192.168.1.100/24, br0, namespace ns0 p1: type=internal, tag=100, vlan_mode=access, ip=192.168.1.200/24, br0, namespace ns1 p2: type=internal, vlan_mode=trunk, trunks=100,200, br0 use tool scapy send ARP pkt from p2:

[ovs-discuss] ping problem between internal port and netdev port

2014-09-23 Thread ychen
HI, I found that internal port and netdev port can not ping each other, can you tell me why? The topology is like this: p0: type=internal, tag=100, vlan_mode=access, ip=192.168.1.100/24, br0, namespace ns0 eth0: type=netndev, tag=100, vlan_mode=access, ip=192.168.1.1/24, br0 then from

[ovs-discuss] VXLAN under OVS

2014-09-23 Thread Jaime Pillora
I’ve added a VXLAN ports to vx1,2 to bridges s1,2 and it seems only the first VXLAN port I create works. Is this a bug or am I only able to use one VXLAN port for each OVS instance? Jaime ___ discuss mailing list discuss@openvswitch.org http://openvswitch

Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-23 Thread Ben Pfaff
So you enabled fail-open mode then? You asked for it to do that. If you don't want that behavior turn it off. On Tue, Sep 23, 2014 at 12:26:47PM +, Gur Stavi wrote: > Hi Ben, > > This is the back trace I see in the debugger on connection loss with the > controller: > > ofproto_flush_flo

Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-23 Thread Gur Stavi
Hi Ben, This is the back trace I see in the debugger on connection loss with the controller: ofproto_flush_flows fail_open_run connmgr_run ofproto_run Later during ofproto_run, ofproto_flush__ is called and actually deletes the rules from ofproto. So it seems to me that OVS does delete flows w