inside the documentation, which seems to suggest this: "after LACP
negotiation is complete, there is no need for special handling of
received packets".
Thanks,
Hans van Kranenburg
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
ubinterfaces (like eth0.3) but while trying to fix that (refactoring it
into e.g. bridge=ovs0,tag=11) we quickly discovered that's a pita,
because adding an option name requires hacking around in lots of python
files from xen. Anyway, it works (tm).
I don't know how it fits together
On 10/22/2012 10:51 PM, Denis Iskandarov wrote:
Nope, your suggestion didn't work as well. (
Just a suggestion: You might want to provide the developers who are
reading this list with more information about what you exactly did and
what happened than only "don't remember exact command", "had
On 07/25/2012 01:55 PM, Hans van Kranenburg wrote:
I really hate the fact I haven't been able to reproduce the situation
again...
So, it happened again yesterday. Exactly at the moment when one of my
collegues started a newly set up domU on one of our servers, a virtual
network interfa
On 07/25/2012 01:13 PM, Ian Campbell wrote:
On Tue, 2012-07-17 at 19:05 +0200, Hans van Kranenburg wrote:
On 07/10/2012 08:16 PM, Ian Campbell wrote:
On Fri, 2012-06-29 at 16:06 +0200, Hans van Kranenburg wrote:
We're seeing weird behaviour regarding network traffic between a Xen
dom
On 07/10/2012 08:16 PM, Ian Campbell wrote:
On Fri, 2012-06-29 at 16:06 +0200, Hans van Kranenburg wrote:
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 al
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
n domU right now.
Luckily the're some sort of workaround to resolve issues when they arise
by moving a domU around to other servers a few extra times until
hopefully all network interfaces work again. :|
--
Hans van Kranenburg - System / Network Engineer
+31 (0)10 2760434 | hans.van.kranen
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
een moving around some
test/acceptance systems of which 2 also broke today with exactly the
same symptoms), so I'm leaving the situation as-is right now, as I don't
want to risk breaking a customer production domU right now.
--
Hans van Kranenburg - System /
Don't want to revive the thread, but just for the sake of completeness:
On 01/09/2012 09:01 PM, Jesse Gross wrote:
> On Sun, Jan 8, 2012 at 1:01 PM, Hans van Kranenburg
> wrote:
>> On 1/8/12 10:33 AM, Dave Whitla wrote:
>>>
>>>
>>> The issue persist
On 1/8/12 10:33 AM, Dave Whitla wrote:
The issue persists in all kernels on the 2.6 branch. I've not
experienced it with 3.x kernels but my scripts have disabled TX
checksumming since I first came across the issue.
The problem is that many people run VMs to support "legacy" systems
on new high-
On 01/05/2012 04:04 AM, Jesse Gross wrote:
On Wed, Jan 4, 2012 at 8:32 AM, Hans van Kranenburg
wrote:
Any idea?
delta.mgt.kantoor.mendix.nl:~ 0-# ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: off
udp
On 10/27/2011 10:23 PM, Ben Pfaff wrote:
On Wed, Oct 26, 2011 at 01:37:08AM +0200, Hans van Kranenburg wrote:
Perhaps it's best to consider the devices set up by ovs at boot time
equal to the nics that are physically present in a server. Using
this approach, I can just say "Yay, I hav
On 10/24/2011 08:20 PM, Ben Pfaff wrote:
On Sat, Oct 22, 2011 at 10:50:11PM +0200, Hans van Kranenburg wrote:
On 10/22/2011 01:54 AM, Ben Pfaff wrote:
On Thu, Oct 20, 2011 at 01:08:57PM +0200, Frank wrote:
Is there a good way to with some kind of hook to add ip addresses to
interfaces defined
er used its config directives).
Taking the udev-way of doing things as a basis and improving the above
could be an idea. The configuration of eth0 can stay in
/etc/network/interfaces, but the configuration of interfaces which are
part of ovs needs to go somewhere else, albeit being configurable.
16 matches
Mail list logo
