Does it properly decrement the TTL if you don't modify the TOS? Does it behave
as you'd expect with OVS 2.0 (the latest release)?
--Justin
> On Feb 3, 2014, at 7:00 PM, Allan Jie wrote:
>
> I want to clarify the problem. And I don't why I cannot post that correctly.
>
> Now here is the thin
I want to clarify the problem. And I don't why I cannot post that correctly.
Now here is the thing.
I start a network like 4 host and 1 switches.
h1,h2 and s1.
I know the dec_ttl action is for ipv4 packet and openflow 1.1+.
So I have finished this command.
ovs-vsctl set bridge s1 protocols=OpenF
Maybe I will try to clarify my problem again.
My setup is very simple. Using Mininet to configure this network.
h1 (h1-eth0)(s1-eth1)s1(s1-eth2)---(h1-eth0)h2.
I start the network using this command.
sudo mn --switch ovsk --mac --custom ~/mininet/custom/LinkCustom.py --topo
mytopo
BTW, I try t
On Fri, Jan 31, 2014 at 10:18 AM, Thomas Glanzmann wrote:
>> Do you know if this happens with an older kernel or with a simpler topology?
>
> No, I don't. I just verified that the Ubuntu Mininet uses the
> openvswitch kernel module from openvswitch and not the one that is
> shipped with the kernel
On Fri, Jan 31, 2014 at 11:20 AM, David Magda wrote:
> On Thu, January 30, 2014 15:45, Jesse Gross wrote:
>>> A particular detail: on which host (i.e, non-VM) interfaces does one
>>> change the MTU for OpenStack? For example, on OS compute nodes, there is
>>> the actual NIC (eth0), but also br-int
No problem, I figured you meant that.
On 2/3/14 3:34 PM, "Justin Pettit" wrote:
>On 2/3/14, 12:30 PM, "Justin Pettit" wrote:
>
>>On 2/3/14, 12:17 PM, "McGarvey, Kevin" wrote:
>>
>>>The TCP workload of a global DNS server consists of TCP sessions, each
>>>with a single request and a response th
On 2/3/14, 12:30 PM, "Justin Pettit" wrote:
>On 2/3/14, 12:17 PM, "McGarvey, Kevin" wrote:
>
>>The TCP workload of a global DNS server consists of TCP sessions, each
>>with a single request and a response that is typically under 2KB, and
>>there is a very large number of source IPs. What level
That's good news. I'll test it.
Kevin
On 2/3/14 3:30 PM, "Justin Pettit" wrote:
>On 2/3/14, 12:17 PM, "McGarvey, Kevin" wrote:
>
>>The TCP workload of a global DNS server consists of TCP sessions, each
>>with a single request and a response that is typically under 2KB, and
>>there is a very l
On 2/3/14, 12:17 PM, "McGarvey, Kevin" wrote:
>The TCP workload of a global DNS server consists of TCP sessions, each
>with a single request and a response that is typically under 2KB, and
>there is a very large number of source IPs. What level of performance,
>expressed in terms of sessions per
The TCP workload of a global DNS server consists of TCP sessions, each with a
single request and a response that is typically under 2KB, and there is a very
large number of source IPs. What level of performance, expressed in terms of
sessions per second, would be expected from Open vSwitch with
On Feb 2, 2014, at 5:19 PM, Jesse Gross wrote:
> On Sat, Feb 1, 2014 at 12:10 AM, Kanthi P wrote:
>> Hi,
>>
>> I installed openvswitch-2.0.0 userspace and kmod rpms on fedora 19. I am
>> trying vxlan configuration using ovs.
>>
>> My kernel version is 3.9.5-301.fc19.i686.PAE
>>
>> I created
On Mon, Feb 3, 2014 at 5:36 AM, Anton Matsiuk wrote:
> Dear all,
>
> I install Layer 1 Flow Rules (namely: Port 1 ->Port 2, Port 2 -> Port 1)
> from Open Flow controller (as well as through ovs-ofctl):
> ovs-ofctl add-flow br0 in_port=1,idle_timeout=0,actions=output:2
> I use 1000 test L4 UDP flow
On Mon, Feb 03, 2014 at 10:59:49PM +0530, raghavan srivats wrote:
> At the level of the dpif, table id does not seem to percolate through nor
> does goto table or resubmit action in any form ;
> and dpif seems to maintain a single table only.
> This collapse of flow table rules spanning multiple t
hi
At the level of the dpif, table id does not seem to percolate through nor
does goto table or resubmit action in any form ;
and dpif seems to maintain a single table only.
This collapse of flow table rules spanning multiple tables into a single
rule in a single table is presumably by intent ? o
These functions schedule events to wake up the following poll_block() call.
For instance, ovsdb-server should wake up next time we receive a JSON rpc
message.
At the end of the loop, there is a poll_block() call that will sleep until
there is further work to do.
On 3 February 2014 00:04, love yo
Hi All,
We are trying to get MPLS push/pop operations working with kernel support using
openvswitch devel/mpls-v2.52 branch but having issues. please find the detailed
description below and let us know if we are missing anything.
We tried various combinations of --protocols=XX and --flow-format=
Dear all,
I install Layer 1 Flow Rules (namely: Port 1 ->Port 2, Port 2 -> Port 1)
from Open Flow controller (as well as through ovs-ofctl):
ovs-ofctl add-flow br0 in_port=1,idle_timeout=0,actions=output:2
I use 1000 test L4 UDP flows (with various dst.ports) to test the Switch
with 1000 of packet
Hi
I have found following three functions get called in ovsdbserver.c. I
didn't get the purpose why server is waiting. Can anyone elaborate the
purpose for that
ovsdb_jsonrpc_server_wait(jsonrpc);
unixctl_server_wait(unixctl);
ovsdb_trigger_wait(db, time_msec());
Regards
18 matches
Mail list logo
