On Tue, May 24, 2016 at 11:57 PM, Justin Pettit wrote:
>
>> On May 24, 2016, at 2:28 AM, Steffen Fredrik Birkeland
>> wrote:
>>
>> Hi
>> I am currently working with open vswitch for my master thesis and I have
>> discovered some issues with the port naming in vswitch.
>>
>> If I chose a port na
On Tue, May 24, 2016 at 10:41 PM, Flaviof wrote:
>
>
> On Tue, May 24, 2016 at 7:33 PM, Thadeu Lima de Souza Cascardo <
> casca...@redhat.com> wrote:
>
>> On Tue, May 24, 2016 at 07:14:11PM -0400, Flaviof wrote:
>> > On Tue, May 24, 2016 at 7:06 PM, Thadeu Lima de Souza Cascardo <
>> > casca...@r
On Tue, May 24, 2016 at 7:33 PM, Thadeu Lima de Souza Cascardo <
casca...@redhat.com> wrote:
> On Tue, May 24, 2016 at 07:14:11PM -0400, Flaviof wrote:
> > On Tue, May 24, 2016 at 7:06 PM, Thadeu Lima de Souza Cascardo <
> > casca...@redhat.com> wrote:
> >
> > > On Tue, May 24, 2016 at 06:24:21PM
Hi Ryan,
> John->I've probably missed an orbit here, but in the ovn-northd
> implementation,
>I was expecting to find service chains in the egress and router pipelines
>in addition to the ingress pipeline (see below for why I think a service
>chain stage in the egress pipeline makes sense ...)
>A
Ryan,
Thanks for getting back to me and pointing me in a more OVS like direction.
What you say makes sense, let me hack something together. I have been a little
distracted getting some use cases together. The other area is how to better map
the flow-classifier I have been thinking about it a li
On Tue, May 24, 2016 at 07:14:11PM -0400, Flaviof wrote:
> On Tue, May 24, 2016 at 7:06 PM, Thadeu Lima de Souza Cascardo <
> casca...@redhat.com> wrote:
>
> > On Tue, May 24, 2016 at 06:24:21PM -0400, Flaviof wrote:
> > > Hi folks,
> > >
> > > I'm trying to write a simple script to generate a pac
On Tue, May 24, 2016 at 7:06 PM, Thadeu Lima de Souza Cascardo <
casca...@redhat.com> wrote:
> On Tue, May 24, 2016 at 06:24:21PM -0400, Flaviof wrote:
> > Hi folks,
> >
> > I'm trying to write a simple script to generate a packet into an existing
> > ovs interface (below). Instead of using "ovs-a
On Tue, May 24, 2016 at 06:24:21PM -0400, Flaviof wrote:
> Hi folks,
>
> I'm trying to write a simple script to generate a packet into an existing
> ovs interface (below). Instead of using "ovs-appctl ofproto/trace", I'm
> attempting "ovs-appctl netdev-dummy/receive" so I can generate the raw
> by
Hi folks,
I'm trying to write a simple script to generate a packet into an existing
ovs interface (below). Instead of using "ovs-appctl ofproto/trace", I'm
attempting "ovs-appctl netdev-dummy/receive" so I can generate the raw
bytes, similar to what we have in the AT tests.
Is "netdev-dummy/recei
Hi,
I am planning to write a usability debug-tool script for OVS-DPDK. The script
can collect and report all the relevant system information that can be used to
debug most of the possible OVS-DPDK issues remotely. A basic implementation of
the script and a sample dump-log file produced by the sc
> On May 24, 2016, at 6:53 AM, Igor Shafran
> wrote:
>
> Hi,
>
> I am trying to get STT tunnel into work on linux (Ubuntu) , kernel version
> 4.2 , ovs version 2.5.
> I compiled sources with kernel modules support and able to create tunnels
> with type: gre/vxlan/geneve successfully. Howeve
> On May 24, 2016, at 2:28 AM, Steffen Fredrik Birkeland
> wrote:
>
> Hi
> I am currently working with open vswitch for my master thesis and I have
> discovered some issues with the port naming in vswitch.
>
> If I chose a port name that is more than 15 characters long, the names are
> beein
Hi,
I am trying to get STT tunnel into work on linux (Ubuntu) , kernel version 4.2
, ovs version 2.5.
I compiled sources with kernel modules support and able to create tunnels with
type: gre/vxlan/geneve successfully. However for stt type vport-stt.ko is not
loaded properly due to lack of corre
Hi
I am currently working with open vswitch for my master thesis and I have
discovered some issues with the port naming in vswitch.
If I chose a port name that is more than 15 characters long, the names are
beeing cut off
ipsec_gre-rasp1-r1 shows up as ipsec_gre-r2-ra. Furthermore, if you
On 05/02/2016 10:36 PM, Ben Pfaff wrote:
What if we just make ofp_port_t 32 bits? That has to be the long-term
trend anyway because OpenFlow 1.1+ uses a 32-bit port number. The
following passes all the unit tests on i386 (though I haven't carefully
looked at all the uses of ofp_port_t), what ab
15 matches
Mail list logo
