Debian Squeeze testing Xen 4.0 bridging

Einrichten des lokalen Netzes, Verbindung zu anderen Computern und Diensten.
Antworten
pbrille
Beiträge: 35
Registriert: 15.03.2008 22:16:44

Debian Squeeze testing Xen 4.0 bridging

Beitrag von pbrille » 04.09.2010 15:02:24

Hi,

ich weiß, dass es noch testing ist, aber soweit läuft bei mir alles stabil, bis auf ein bridge Interface.
2 physikalische NIC hat der Server eth0 und eth1. Über eth0 läuft das gesamte interne Netzwerk über br0. br1 überbrücke ich für pppoe.

br0 - LAN
br1 - Internet

1 dom0 2.6.32-5-xen-amd64 xen 4.0rc5, darauf
3 domu, alle mit xen-tools erstellt und laufen auch auf debian squeeze.:
- shiva: eth0 an br0
- dharma: eth0 an br0 und eth1 an br1
- vishnu: eth0 an br0

An für sich laufen alle bridges stabil, lediglich EIN Gast (dharma), der mit an br0 hängt verliert die Verbindung schonmal. Auf dharma läuft DNS, DHCPd, und iptabels über shorewall mit NAT.

Zum Problem:
1) Die Verbindung dharma an das lokale Netzwerk (eth0 an br0) fällt komplett aus. Die pppoe Verbindung bleibt vorhanden.
Die Verbindunge zu den anderen Gästen, die mit auf br0 hängen, geht die Verbindung (zuminderst Dauerhaft) nicht verloren.
2) Das default gw in der dom0 aus der /etc/network/interfaces wird nicht richtig gesetzt. Ich muss mit

Code: Alles auswählen

route add default gw 10.100.200.3 br0
die Route von Hand eintragen, damit ich in der dom0 auch Zugriff aufs Internet habe.

In /var/log/messages find ich z.B. solche Infos:
Sep 4 14:53:50 elise kernel: [220737.916251] br1: port 2(vif10.1) entering disabled state
Sep 4 14:53:50 elise kernel: [220737.946474] br1: port 2(vif10.1) entering disabled state
Sep 4 14:53:50 elise kernel: [220738.004841] br0: port 2(vif10.0) entering disabled state
Sep 4 14:53:50 elise kernel: [220738.038535] br0: port 2(vif10.0) entering disabled state
Sep 4 14:53:51 elise kernel: [220739.154269] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.154280] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.154287] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.154294] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.161069] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.161080] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.161087] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.219282] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.219292] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.219301] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.225866] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:51 elise kernel: [220739.225876] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220741.924901] device vif11.0 entered promiscuous mode
Sep 4 14:53:54 elise kernel: [220741.932155] br0: port 2(vif11.0) entering listening state
Sep 4 14:53:54 elise kernel: [220741.973846] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220741.973864] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220741.981971] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220741.981982] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220741.981989] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220741.999801] device vif11.1 entered promiscuous mode
Sep 4 14:53:54 elise kernel: [220742.006810] br1: port 2(vif11.1) entering listening state
Sep 4 14:53:54 elise kernel: [220742.043280] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220742.043291] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220742.043298] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220742.050636] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220742.050648] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220742.050655] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:54 elise kernel: [220742.050664] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Sep 4 14:53:56 elise kernel: [220744.031413] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
Sep 4 14:53:56 elise kernel: [220744.053263] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
Sep 4 14:54:09 elise kernel: [220756.933545] br0: port 2(vif11.0) entering learning state
Sep 4 14:54:09 elise kernel: [220757.005053] br1: port 2(vif11.1) entering learning state
Außerdem meine Netzwerk Config in /etc/network interfaces
auto br0
allow-hotplug br0
iface br0 inet static
address 10.100.200.20
netmask 255.255.2550
dns-nameservers 10.100.200.3
gateway 10.100.200.3
bridge_ports eth0
bridge_stp yes
up route add default gw 10.100.200.1 br0


allow-hotplug br1
auto br1
iface br1 inet manual
bridge_ports eth1
bridge_stp yes

pbrille
Beiträge: 35
Registriert: 15.03.2008 22:16:44

Re: Debian Squeeze testing Xen 4.0 bridging

Beitrag von pbrille » 05.09.2010 16:10:52

Haha, einen Flüchtigkeitsfehler hab ich gefunden, der es per copy & paste sogar bis hier ins Forum geschafft hat.
Ob es die Ursache ist, werd ich noch posten.
255.255.2550
Nachtrag:
Der Flüchtigkeitsfehler war NICHT die Ursache des Problems. Zwischenzeitlich bin ich auf diesen Thread gestoßen, in dem ich aber noch nach der Lösung suche...
http://bugs.debian.org/cgi-bin/bugrepor ... =571634#10

Antworten