Your message dated Sat, 01 May 2021 08:08:11 -0700 (PDT) with message-id <608d6edb.1c69fb81.57759.c40e@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #697357, regarding bridging broken over bond interfaces to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 697357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697357 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: bridging broken over bond interfaces
- From: Peter Palfrader <weasel@debian.org>
- Date: Fri, 04 Jan 2013 12:17:12 +0100
- Message-id: <20130104111712.25539.62770.reportbug@valiant.palfrader.org>
Package: linux-image-3.2.0-4-amd64 Version: 3.2.35-2 Severity: important Hi, I tried to set up a new KVM host in the usual way: - have a bond0 interface over all physcial eth* interfaces - create a br0 over that bond0 and any vnet* interfaces for the guests. on wheezy's 3.2.0-4-amd64 this setup results in network breaking in the following way: - host can talk to guest and vice versa, - host can talk to other hosts on the network, and vice versa, - other hosts on the network can get arp replies from guests, but cannot talk IP to them. tcpdumping on the host suggests the br0 never even sees the packets intended for the guest. * Manually switching the eth* to promiscious mode makes stuff work. Cheers, weasel
--- End Message ---
--- Begin Message ---
- To: 697357-done@bugs.debian.org
- Cc: 697357-submitter@bugs.debian.org
- Subject: Closing this bug (BTS maintenance for src:linux bugs)
- From: carnil@debian.org
- Date: Sat, 01 May 2021 08:08:11 -0700 (PDT)
- Message-id: <608d6edb.1c69fb81.57759.c40e@mx.google.com>
Hi This bug was filed for a very old kernel or the bug is old itself without resolution. If you can reproduce it with - the current version in unstable/testing - the latest kernel from backports please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore
--- End Message ---