Your message dated Sun, 6 May 2012 17:55:53 +0200 with message-id <20120506155553.gc13...@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 ow...@bugs.debian.org immediately.) -- 571634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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@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@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:mistere2...@zonnet.nl
--- End Message ---
--- Begin Message ---Version: 4.1.0~rc6-1 This was fixed in 4.1. Bastian -- There's a way out of any cage. -- Captain Christopher Pike, "The Menagerie" ("The Cage"), stardate unknown.
--- End Message ---
