On Tue, Oct 25, 2016 at 07:41:28AM +, Andrej Leitner wrote:
> In specification for OF bundles (extension #230 for v1.3) there is the field
> struct onf_bundle_prop_header properties[0] in message BUNDLE_CONTROL.
>
> This field is present also in the second BUNDLE_ADD_MESSAGE however commented
On Wed, Oct 26, 2016 at 12:45:48PM +0300, Ben Kelly wrote:
> Hi,
>
> I've been searching for ways to implement something like "protected
> mode" for ovs without much luck so far. Hoping someone on the discuss
> mailing list might have some suggestions.
>
> Protected mode is available on some broa
Hi Thadeu,
Finally, I switch to Open vSwitch 2.5.1 and DPDK 2.2.0 with identical
hugepage setup, and it works fine.
Using the stable version of OVS is a workaround to avoid this issue.
I searched for the error messages, and they are from a patch for Jumbo
Frames on Aug 9, 2016(
http://openvswitc
Thanks Mark, I will check this.
I am not using multi-queue and from this thread, they have already added a
change in OVS to support older version of QEMU(queue 0 is enabled in OVS
even if qemu doesnt send VRING_ENABLE), which is what helped me to use qemu
2.4.1 till OVS 2.5.9. are these threads re
>
>Hi Mark,
>
>This commit is already part of 2.6.0 that i am using. Also, when i create an
>port with
>mtu_request, it is creating with the expected mtu, no problems here.
>
>The issue i am facing is, i am not even able to run traffic through a
>PHY-VM-PHY with the
>default MTU (mtu_request not
Hi Mark,
This commit is already part of 2.6.0 that i am using. Also, when i create
an port with mtu_request, it is creating with the expected mtu, no problems
here.
The issue i am facing is, i am not even able to run traffic through a
PHY-VM-PHY with the default MTU (mtu_request not used).
I am j
Hello Curtis,
thank you very much for your help. Your suggestion was correct, after
patching the hostapd, compiling openwrt again and inserting one line
into my hostapd config file my clients could establish a encrypted
connection to my access point.
I've also tried to understand the caus
>
>Hi,
>
>Issue Setup: DPDK 16.07 + OVS 2.6.0 + qemu 2.4.1 : PHY-VM-PHY
>
>I am trying to upgrade from (DPDK16.04 + OVS2.5.9), to (DPDK16.07 + OVS2.6.0)
>for jumbo frame
>support. After the upgrade, all packets are getting dropped on the vhostuser
>port.
>The dpdk/vhost user ports used here has
On Wed, Oct 26, 2016 at 10:01:39PM +0800, Bo Sun wrote:
> Hi Thadeu,
>
> Thank you for your inspiring advice and patience.
>
> I set the brige and device as type dpdk, then I found that it's caused by
> insufficient memory.
>
> Since I get the reason, I will change NUMA memory policy and try to
Hi Thadeu,
Thank you for your inspiring advice and patience.
I set the brige and device as type dpdk, then I found that it's caused by
insufficient memory.
Since I get the reason, I will change NUMA memory policy and try to solve
it.
Thanks again.
Here are logs:
2016-10-26T13:50:29Z|00022|dpd
On Wed, Oct 26, 2016 at 09:25:38PM +0800, Bo Sun wrote:
> It also failed.
> I think, if dpdk0 is available, it should appear in logs. But I never see
> dpdk0 in logs.
>
> Here are details of adding dpdk0:
>
> # ovs-vsctl add-port ovsbr dpdk0
> ovs-vsctl: Error detected while setting up 'dpdk0'.
It also failed.
I think, if dpdk0 is available, it should appear in logs. But I never see
dpdk0 in logs.
Here are details of adding dpdk0:
# ovs-vsctl add-port ovsbr dpdk0
ovs-vsctl: Error detected while setting up 'dpdk0'. See ovs-vswitchd log
for details.
Log details:
2016-10-26T13:16:39.224
On Wed, Oct 26, 2016 at 09:13:46PM +0800, Bo Sun wrote:
> Sorry for forgetting to include mail list, I'm re-sending my reply.
>
> The problem is that there isn't dpdk0 or dpdk1 port shown up.
> So I can't add dpdk port to the brige, which means that I can't use dpdk to
> transfer packets.
> I did
Sorry for forgetting to include mail list, I'm re-sending my reply.
The problem is that there isn't dpdk0 or dpdk1 port shown up.
So I can't add dpdk port to the brige, which means that I can't use dpdk to
transfer packets.
I didn't add any other ports to the brige, because I intend to use OVS-DP
Hi,
Issue Setup: DPDK 16.07 + OVS 2.6.0 + qemu 2.4.1 : PHY-VM-PHY
I am trying to upgrade from (DPDK16.04 + OVS2.5.9), to (DPDK16.07 +
OVS2.6.0) for jumbo frame support. After the upgrade, all packets are
getting dropped on the vhostuser port.
The dpdk/vhost user ports used here has default MTU o
On Wed, Oct 26, 2016 at 08:10:55PM +0800, 孙博 wrote:
> The problem is that there isn't dpdk0 or dpdk1 port shown up.
> So I can't add dpdk port to the brige, which means that I can't use dpdk to
> transfer packets.
> I didn't add any other ports to the brige, because I intend to use OVS_DPDK.
>
>
On Wed, Oct 26, 2016 at 06:08:24PM +0800, Bo Sun wrote:
> Hi list,
>
> I'm using OVS 2.6.0 and DPDK 16.07 on CentOS 7.2, following the
> instructions on ovs/INSTALL.DPDK.rst.
>
> When I start ovs-vswitchd, it can't function properly.
>
> I got warnings like "ovs|00014|timeval|WARN|Unreasonably l
Dear All,
I was trying to implement GRE tunneling in OVS using mininet. I have two
Ubuntu 16 VMs with mininet and OVS installed on them. I saw in some youtube
video that we must enable adapter 2 as shown below in order to enable
networking between different VMs.
When I start the VM before the
Hi list,
I'm using OVS 2.6.0 and DPDK 16.07 on CentOS 7.2, following the
instructions on ovs/INSTALL.DPDK.rst.
When I start ovs-vswitchd, it can't function properly.
I got warnings like "ovs|00014|timeval|WARN|Unreasonably long 6567ms poll
interval (232ms user, 5958ms system)" and many others. I
Hi John,
I successfully build the rpm for ovs 2.6 on CentOS 7 up to date. Just by
doing ./configure && make rpm. Maybe there is some difference doing this
instead of using rpmbuild directly.
Best regards,
Edouard
Le mer. 26 oct. 2016 à 00:33, John Chludzinski
a écrit :
> Commands:
>
> # ./boot
Hi,
I've been searching for ways to implement something like "protected
mode" for ovs without much luck so far. Hoping someone on the discuss
mailing list might have some suggestions.
Protected mode is available on some broadcom switch ASIC, and cisco
switches also have this as a configurable opt
21 matches
Mail list logo
