That seems like a reasonable way to start out.
On Wed, Nov 30, 2016 at 08:40:27AM -0800, Guru Shetty wrote:
> ct_lb is tricky. I guess, the default should be to just pick the first
> option.
>
> On 30 November 2016 at 08:24, Ben Pfaff wrote:
>
> > One initial, trivial, step might be to just hav
Hello,
I find it difficult to debug OVS files without any debuggers. Would you
suggest me to use GDB or is there any specific techniques to debug the
problem ? As both user space and kernel space modules in OVS run as daemon
process will I be able to debug it using GDB ?
Thank you,
Ajeeth Kannan
On Thu, Dec 01, 2016 at 12:20:59PM +1100, Shivaram Mysore wrote:
> Can I configure OVS in Openflow mode to constantly send telemetry data
> (ofstats) to a particular configured controller without the controller
> polling for data?
>
> Or is there an other way?
OpenFlow doesn't have a feature for
Hello,
I am working into the code of OVS. Can I use GDB to debug both user space
and kernel space modules in OVS ?
Thank you,
Ajeeth Kannan
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Can I configure OVS in Openflow mode to constantly send telemetry data
(ofstats) to a particular configured controller without the controller
polling for data?
Or is there an other way?
Thanks
/Shivaram
___
discuss mailing list
disc...@openvswitch.org
I think this issue is not that simple. It depends on how you use it.
For normal use cases, a tunnel port will terminate the tunnel traffic, so a
packet sent to a tunnel port will never be from another tunnel port, so no
tunnel metadata is available for the first packet, but for the packets which
Feel free to take measurements to find out the actual reason.
On Wed, Nov 30, 2016 at 06:36:07AM +, Naoyuki NS Shimizu wrote:
> Hi,
>
>
>
>
>
> "it just takes more time to process packets arriving at the local TCP/IP
> stack than it does to send packets to a physical port."
>
> ⇒Why? I
ct_lb is tricky. I guess, the default should be to just pick the first
option.
On 30 November 2016 at 08:24, Ben Pfaff wrote:
> One initial, trivial, step might be to just have every ct_next respond
> that the flow is established. Then at least it would be possible to see
> how packets flow thr
On Wed, Nov 30, 2016 at 04:00:48PM +0100, Ashish Kurian wrote:
> Does OVS provide a controller so that we can use it in mininet to act as
> the OVSController? Previously it was named OVSController and later to
> ovs-testcontroller. But now I cannot find such a file in the master branch
> of OVS
It
One initial, trivial, step might be to just have every ct_next respond
that the flow is established. Then at least it would be possible to see
how packets flow through the system in the normal case.
I noticed that you were getting DHCP-related errors from ovn-trace. I
have a patch out that fixes
Hi, folks
I tried to build ovs 2.6.1 in Ubuntu trusty 64 with the below configuration
options, but it failed, it is ok when I use the same way to build in Ubuntu
16.04 which has Linux kernel 4.4. What is the minimum Linux kernel version ovs
2.6.1 build requires?
./configure --prefix=/ --with-l
I also face that problem in my OPNFV APEX deployment. I hope, it is fixed
soon.
Best regards,
Ahmed
On Sat, Nov 26, 2016 at 11:08 PM, Ben Pfaff wrote:
> On Thu, Nov 24, 2016 at 02:39:43AM +, Yang, Yi Y wrote:
> > I noticed vxlan module always uses tp_dst from tunnel metadata in
> preference
Hi Folks,
Does OVS provide a controller so that we can use it in mininet to act as
the OVSController? Previously it was named OVSController and later to
ovs-testcontroller. But now I cannot find such a file in the master branch
of OVS
Best Regards,
Ashish Kurian
__
On 11/28/2016 05:49 PM, Gerhard Stenzel wrote:
...
>
> It seems the tunnel port is set in ./net/openvswitch/flow_netlink.c:
>
> static int validate_and_copy_set_tun(const struct nlattr *attr,
> struct sw_flow_actions **sfa, bool log)
> {
>
> if (k
On 11/26/2016 11:08 PM, Ben Pfaff wrote:
> On Thu, Nov 24, 2016 at 02:39:43AM +, Yang, Yi Y wrote:
>> I noticed vxlan module always uses tp_dst from tunnel metadata in preference
>> to vxlan->cfg.dst_port, this isn't the result we want in some use cases, for
>> example, if we create two vxlan
15 matches
Mail list logo