Yes,I have only one flow in flow table, "action=normal".
But when the gre tunnel port becomes a data path《ovs-dpctl show》, we can use
the ovs-ofctl to control the traffic. I did it. I can see the packets pass the
flow table entry.
On 2012-6-6, at 上午11:07, ravi kerur wrote:
> I think probably yo
I think probably you have single flow in the flow table, you can
check using ovs-ofctl dump-flows .
This works well when all type of traffic are going through the tunnel
interface. That's the case for me as well. However, when I want to
split certain type of traffic to go through tunnel and other
I am happy to share my configuration.
2 hosts,
192.168.1.100 eth0
192.168.1.101 eth0
Each has a vm. We config the vm in the same subnet.
We shouldn't add the eth0 on bridge. The bridge likes this:
br0: vnet0
add the gre tunnel on br0:
ovs-vsctl add-port br0 gre0 -- set interface gre0 type=g
Hi Ethan,
Thank you for your reply. I actually sent second email regarding the
comments before this function. If I am reading the logic correctly
(please correct me if I am wrong):
rule_execute() will construct odp actions for two cases, not only
exact-match case:
1) wildcards
2) exact-match with
> /* Grab or compose the ODP actions.
> *
> * The special case for an exact-match 'rule' where 'flow' is not the
> * rule's flow is important to avoid, e.g., sending a packet out its input
> * port simply because the ODP actions were composed for the wrong
> * scenario. */
>
On 6/5/12 3:28 PM, Anisha Kolasani wrote:
Any more suggestions as to why it may not be working?
Try to run tcpdump at all your network path
tcpdump -nnei eth0
tcpdump -nnei br0
Compare with the ones that are working and see the difference between
the tagged ones.
--
Luiz Henrique Ozaki
I tried adding the vlan21 port. But it doesn't work. In fact its allowing
non-vlan traffic between VMs go through, although vlan21 is the only
interface that has an IP address. But not the tagged once. Any more
suggestions as to why it may not be working?
Thank you!
Anisha.
On Tue, Jun 5, 2012 at
Faicker,
Can you share your configuration with general public so everyone can
benefit from it. At least I am having similar issues and still not
working correctly. In your case have you setup flows using ovs-ofctl
to match certain tunnel parameters?
Thanks,
Ravi
>
>
>
> From: discuss-boun...@ope
On 6/5/12 11:53 AM, Anisha Kolasani wrote:
ovs-vsctl add-port br0 eth0 trunks=21
Try this:
ovs-vsctl del-br br0
ovs-vsctl add-br br0 eth0
ovs-vsctl add-port br0 vlan21 tag=21 -- set interface vlan21 type=internal
ifconfig vlan21 192.168.5.5 netmask 255.255.255.128
That should make it work
Hi,
Thank you very much for the reply. I haven't explicitly created VLAN 21 on
the physical machine. As both the physical machines are connected by
crossover cable through eth0, I did the following:
ovs-vsctl add-port br0 eth0
ifconfig eth0 0
ifconfig br0 192.168.5.5 netmask 255.255.255.128
I as
On 6/3/12 6:04 PM, Anisha Kolasani wrote:
The VM1 on machine 1 is able to ping VM3 on machine 2. The tap
interfaces of VM1 and VM3 are not declared as access ports.
But VM2 on machine 1 is not able to ping VM4 on machine 2. VM2 and VM4
are not declared to be on VLAN 21.
Could you please let me
I solved it.
I compile the 1.4.1 source files, and used the openvswitch.ko module to replace
the default kernel module in linux 3.3.7.
Now, it's OK. Only this command is enough:
ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre
options:remote_ip=192.168.1.101
On 2012-6-4, at 下午6:59, f
Hi Kaushal n Justin,
On 06/05/2012 09:19 AM, Kaushal Shubhank wrote:
Surely we will try the 1.7.0 version. Considering this is production,
we will be able to try this in off-peak hours. We will update you with
the results as soon as possible.
Thanks a lot and looking forward to contribute to
Thanks very much for the detailed info, Peter！ And the part of involving
virtual entities into topology is even more interesting. Thanks！
Best,
Bibo
在 2012-6-5 中午12:20，"Peter Phaal" 写道：
> Hi All,
>
> The original question was about L2 topology discovery. One of the
> differences between sFlow and
Surely we will try the 1.7.0 version. Considering this is production, we
will be able to try this in off-peak hours. We will update you with the
results as soon as possible.
Thanks a lot and looking forward to contribute to the project in any way
possible.
Kaushal
On Tue, Jun 5, 2012 at 12:36 PM
Of your nearly 12,000 flows, over 10,000 had fewer than four packets:
[jpettit@timber-2 Desktop] grep -e "packets:[0123]," live_flows_20120604 |wc -l
10143
Short-lived flows are really difficult for OVS, since there's a lot of overhead
in setting up and maintaining the kernel flow table. We
16 matches
Mail list logo
