hi ,
Please help us in understanding the error packet designing.
On Fri, Jun 29, 2012 at 11:04 PM, sonny sonny wrote:
> hi Ben,
> We both were working on this.Sorry for confusion..Please help us in
> understanding the design change..
>
>
> On Fri, Jun 29, 2012 at 10:57 PM, Ben Pfaff wrote:
>> Wh
On Fri, Jun 29, 2012 at 5:09 AM, Michael A. Collins
wrote:
> I recently tried unsuccessfully to compile the kernel version of the 1.6.1
> tarball release on a box with kernel 3.3. I recieved a redefinition error
> in vlan.h, which I can only guess means that there is no good way to get
> around p
hi Ben,
We both were working on this.Sorry for confusion..Please help us in
understanding the design change..
On Fri, Jun 29, 2012 at 10:57 PM, Ben Pfaff wrote:
> Who are you? Are you the same person as "sonny sonny"? Is this the
> same question or a different one?
>
> On Fri, Jun 29, 2012 at
Who are you? Are you the same person as "sonny sonny"? Is this the
same question or a different one?
On Fri, Jun 29, 2012 at 10:39:22PM +0530, Amit Tewari wrote:
> hi,
> i wanted to display BAD_VERSION error from switch to controller..am working
> on error handling on my controller from switch.
hi,
i wanted to display BAD_VERSION error from switch to controller..am working
on error handling on my controller from switch. But why is switch behaving
like this,
i also used openvswitch-1.2.2 there error packet header version from
switch was 1 not 3 . what is this design change in 1.6 version
On Fri, Jun 29, 2012 at 05:06:32PM +0530, sonny sonny wrote:
> Following is my setup on openvswitch 1.6.1
> controller - nox 0.9.0(zaku)
> Switch generates error packet for vendor message from controller, with
> header version as 1 in error packet , which is correct behaviour of
> switch.
> But whe
On 06/29/2012 04:06 PM, Hans van Kranenburg wrote:
Package: xen-hypervisor-4.0-amd64
Version: 4.0.1-5.2
Whoops, accidentally mailed ovs-discuss again, when submitting the issue
to debian, please ignore, sorry.
Anyway, after asking on IRC, I was advised to also report the issue at
debian, be
Package: xen-hypervisor-4.0-amd64
Version: 4.0.1-5.2
Hi,
We're seeing weird behaviour regarding network traffic between a Xen
dom0 and domU. I reported this issue yesterday to the
openvswitch-discuss mailing list, but it seems this could also be a
(regression?) bug in the xen hypervisor or th
I recently tried unsuccessfully to compile the kernel version of the
1.6.1 tarball release on a box with kernel 3.3. I recieved a
redefinition error in vlan.h, which I can only guess means that there is
no good way to get around patching the openvswitch kernel code in the
kernel, or try removi
Hi,
Following is my setup on openvswitch 1.6.1
controller - nox 0.9.0(zaku)
Switch generates error packet for vendor message from controller, with
header version as 1 in error packet , which is correct behaviour of
switch.
But when i change header version to 3 in vendor message on controller
i rec
When re-reading my post from yesterday...
On 06/28/2012 08:21 PM, Hans van Kranenburg wrote:
On the interface at the ovs (dom0) side, I can see arp requests, which
are not being answered by the problematic host.
# tcpdump -n -i domU-24-09
tcpdump: WARNING: domU-24-09: no IPv4 address assigned
11 matches
Mail list logo