MisterE
2011-Aug-31 20:57 UTC
[Pkg-xen-devel] Bug#639942: Xen "non-bridged traffic is not supported anymore" with bridges
Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). This appeared in the messages when i started and stopped a DomU: root at dom0:~# cat messages Aug 31 22:04:52 dom0 kernel: [ 775.569937] device vif6.0 entered promiscuous mode Aug 31 22:04:52 dom0 kernel: [ 775.575993] br_lan: port 2(vif6.0) entering forwarding state Aug 31 22:04:52 dom0 kernel: [ 775.606023] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Aug 31 22:04:53 dom0 kernel: [ 776.323952] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi) Aug 31 22:07:53 dom0 kernel: [ 955.709120] br_lan: port 2(vif6.0) entering disabled state Aug 31 22:07:53 dom0 kernel: [ 955.721359] br_lan: port 2(vif6.0) entering disabled state Aug 31 22:07:53 dom0 kernel: [ 955.790532] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. grep bridge /etc/xen/paradeb01.cfg vif = [ 'mac=00:16:3E:0B:EE:5B, bridge=br_lan' ] I run a virtual pfsense firwall in a DomU. I created multiple bridges. The interfaces itself (except eth2 (connected to br_lan)) itself don't have a IP assigned. root at dom0:/etc/xen/scripts# cat /etc/xen/scripts/my-network-script #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth3 bridge=br_inet "$dir/network-bridge" "$@" vifnum=1 netdev=eth2 bridge=br_lan "$dir/network-bridge" "$@" vifnum=2 netdev=eth1 bridge=br_wlan "$dir/network-bridge" "$@" vifnum=4 netdev=dummy0 bridge=br_dmz If i start the firewall (connected to multiple bridges) i get a LOT of those scary messages. -- Best regards, MisterE mailto:MisterE2002 at zonnet.nl
Debian Bug Tracking System
2012-May-06 15:57 UTC
[Pkg-xen-devel] Bug#639942: marked as done (Xen "non-bridged traffic is not supported anymore" with bridges)
Your message dated Sun, 6 May 2012 17:55:53 +0200 with message-id <20120506155553.GC13846 at wavehammer.waldi.eu.org> and subject line fixed has caused the Debian Bug report #571634, regarding Xen "non-bridged traffic is not supported anymore" with bridges 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 at bugs.debian.org immediately.) -- 571634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571634 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: MisterE <MisterE2002 at zonnet.nl> Subject: Xen "non-bridged traffic is not supported anymore" with bridges Date: Wed, 31 Aug 2011 22:57:00 +0200 Size: 3758 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120506/e928d580/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: fixed Date: Sun, 6 May 2012 17:55:53 +0200 Size: 1496 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120506/e928d580/attachment-0001.mht>
Apparently Analagous Threads
- Bug#639941: Xen "line 118: sigerr: command not found" error for unassigned network interfaces
- RE: Hotplug scripts not working... xen/ia64 domU stoppedworking
- Xen3: Unable to start xenU with Intel Core Duo T2050
- Processed: forcibly merging 571634 639942
- Xen PCI Pass-through: 0xbf701000 is using VM_IO, but it is 0xfffffffffffff000!