"git am" says:
/home/blp/nicira/ovs/.git/rebase-apply/patch:9: trailing whitespace.
if (version != type->ofp_version) {
/home/blp/nicira/ovs/.git/rebase-apply/patch:10: trailing whitespace.
return OFPERR_OFPBRC_BAD_VERSION;
Hi Ben,
I emailed the patch to myself and I received it in correct format.
I am resending the patch after configuring my email-client.
I am sending patch for generating OFPERR_OFPBRC_BAD_VERSION error in case of
version mismatch in openflow packets from controller to switch. This patch is
for la
One oddity is that you are using 11:22:33:44:55:66 as an Ethernet source
address when that's invalid as a source address (the multicast bit is
set). I'd expect the NORMAL action to just drop such packets.
Beyond that I really don't understand what you're reporting. The
distinction among access p
Hi Ben,
If you see my two flow entries made earlier both are having action "NORMAL"
but then also if I am making vnet port as access port with vlan 3 then all
tag packets are passing through this port and hitting the flow entry in
bridge.
cookie=0x0, duration=263.359s, table=0, n_packets=1, n_by
The default behavior of the OVS switch is implemented through an action
called "normal". If you write a flow that doesn't execute this action,
then it is up to you to implement the VLAN behavior that you want.
On Tue, Jul 03, 2012 at 09:30:44AM +0530, edward wilson wrote:
> Hi Ben,
>
>
>
> Tha
Hi,
we'd like to add the Open vSwitch kernel module to OpenVZ kernel,
in order to do that we've backported the appropriate code from mainstream
kernel.
It turned out that the vport-patch functionality could be also very useful for
us,
so we are looking for possibility to include it to our kern
Hi Amit, your patch is corrupted. (It is double-spaced, at least.)
Please re-send in a form that can be applied directly, e.g. try emailing
it to yourself then applying with "git am".
On Wed, Jul 04, 2012 at 07:05:39AM +, Amit Tewari wrote:
> Hi Ben,
>
>
>
> I am sending patch for generati
Below I am asking for HTB
On Wed, Jul 4, 2012 at 4:24 PM, selen jia wrote:
> Hi Justin,
>
> Please correct me if I am wrong,I am trying to map "vsctl" parameters with
> "tc" parameters :-
>
> *Mode* of class is artifical value which can be computed from *R (actual
> rate)*,*AR(assured rate)*,*CR
Hi Justin,
Please correct me if I am wrong,I am trying to map "vsctl" parameters with
"tc" parameters :-
*Mode* of class is artifical value which can be computed from *R (actual
rate)*,*AR(assured rate)*,*CR(ceil rate)*. Possible modes are
- *Red*: *R* > *CR*
- *Yellow*: *R* <= *CR* and *R
Hi,
I am the INSTALL.Linux document to install Open Vswitch in fedora
17(release: 3.4.4-3.fc17.x86_64) dom0.
I did
./configure --prefix=/usr --localstatedir=/var
--with-linux=/lib/modules/3.4.4-3.fc17.x86_64/build
and then make. But make gives this error:
make all-recursive
make[1]: Entering
Thanks Justin!
just one more query -
in configuartion cookbook of OVS, you are taking measuring host as separate
machine ,can't I take my bridge (OVS) as measuring machine, because traffic
of VM coming on bridge only and we can verify throttle on bridge itself
through netperf
Regards
Selen
On We
If you configure it through ovs-vsctl, an appropriate configuration should be
pushed down to the kernel. We don't expose as many knobs as the tc command, so
the configuration is much simpler. You should be able to verify the
configuration pushed down by using the tc command to dump classes, qd
Hi Justin,
Sorry to bother you.
I am confused because tc manual is having many paarmeters to configure,
class , handle id etc.. but in OVS we have just rate or burst.
so how we will configure parent -child through OVS vsctl?
regards,
Selen
On Wed, Jul 4, 2012 at 12:32 PM, Justin Pettit wrote:
That's what you're configuring, so OVS is taking care of the tc configuration.
--Justin
On Jul 3, 2012, at 11:54 PM, selen jia wrote:
> Hi,
>
> To verify HTB and HFSC on OVS ,if I am creating queue and setting rate
> through vsctl command then do I need to do some configuration from "tc" als
Hi Ben,
I am sending patch for generating OFPERR_OFPBRC_BAD_VERSION error in case of
version mismatch in
openflow packets from controller to switch. This patch is for latest release
1.6.1.
I have also patched lib/ofp-errors.c file so that OFPERR_OFPBRC_BAD_VERSION
error packet contains sw
15 matches
Mail list logo
