hello,
How to use nlmon? More detail will be well .
Thanks.___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
Thanks Justin for the help, I am able to see the inter-switch links .
For some reason the type of the port are showing "internal" what does this mean,
how is the controller identifying the port as internal and how can i change
this?
because of this when i issue the following curl, the output is
The Open vSwitch team is pleased to announce the release of Open vSwitch 1.9.0:
http://openvswitch.org/releases/openvswitch-1.9.0.tar.gz
This release contains new features and bug fixes. It also represents our new
LTS (long-term support) release branch. Feature highlights of 1.9.0 include:
Hi!
> I thought br0 behaves like a L2 switch on which multiple VLAN tags may exist.
> Thus tagging 100 on br0, I though it does not make any sense. Anyway, thanks
> for your help.
When you are tagging br0 interface, you are not setting that only VLAN
100 traffic can go through the bridge. What
The problem is : It's still failed after releasing the space on disk.
I make a patch to fix it:
--- ovsdb/log.c+++ ovsdb/log.c@@ -324,5 +324,5 @@
json_string = NULL;
-if (file->write_error) {+if (file->write_error && (ENOSPC !=
ovsdb_error_errno(file->write_error))) {return
o
Can you give me a Signed-off-by for that patch?
On Tue, Feb 26, 2013 at 03:42:18PM +, likunyun wrote:
>
> The problem is : It's still failed after releasing the space on disk.
> I make a patch to fix it:
> --- ovsdb/log.c+++ ovsdb/log.c@@ -324,5 +324,5 @@
> json_string = NULL;
> -if (
