WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-fr

[Xen-fr] 2 cartes réseaux avec 2 passerelles

To: xen-fr@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-fr] 2 cartes réseaux avec 2 passerelles
From: Ko0nz <yesiko0nz@xxxxxxxxx>
Date: Wed, 7 Nov 2007 17:00:56 +0100
Delivery-date: Wed, 07 Nov 2007 08:01:23 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=KG6TkORv7de/Eq+DSKF4LMXfUuqIJjkCWBCpeRbKobU=; b=QXzAaGtwxdsLxNb9Kbo77MSHiPGcJ9yNTCJjHbQssxjb49uwmQa+025pQqvwaiOScr4PRBXHTiFXgZSceZgB/dsH/xCh3JJtW9Y7KZbZzF0xhtSlCrZTL8Lt2T+J4/IbSBHPYkrp/AXC9kXcKsO6CJjMIEHyfN4Gh92Kx2aqHkQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WQ3Dq8JftML+nGxPdSxa6+XwiyNaUJoYH0p7IBB4PwKLzW8nDEYBE4Bhlk9ud2hce5j8xa+zQaC7/zozFmHpEsorPKR/TS/eWoal3TOKV8VdzQ5O7TnJhVhhzjQmHQFvy0VPyDBr7tqQXydN7sQ34T1CRh9/huZPxpVC5OcLhtM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-archive: <http://lists.xensource.com/archives/html/xen-fr>
List-help: <mailto:xen-fr-request@lists.xensource.com?subject=help>
List-id: xen-fr.lists.xensource.com
List-post: <mailto:xen-fr@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-fr>, <mailto:xen-fr-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-fr>, <mailto:xen-fr-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-fr@xxxxxxxxxxxxxxxxxxx
Sender: xen-fr-bounces@xxxxxxxxxxxxxxxxxxx
Bonjour,

Actuellement, j'ai un serveur avec deux cartes réseaux.
j'ai le besoin de les utiliser toutes les.
chacune est dans un sous-réseau avec chacune une passerelle différente.
eth0: 192.168.1.10 gw 192.168.1.1
eth1: 192.168.2.20 gw 192.168.2.1

j'aimerais servir de eth1 comme "bridge" pour mon Dom1 qui aura une ip
du genre 192.168.2.x avec une passerelle 192.168.2.1

pourquoi cette envie de config, c'est parce que ce serveur est
connecté à un Routeur qui est configuré en VLAN.
eth0 sera connecté en LAN et eth1 sera en DMZ.


 ---Router(VLAN)----
l                         l
l                         l
eth0---Dom0-----eth1
l                         l
l         Dom1-----eth0
l
l------eth0--Dom2
l
l------eth0--Dom3

===========================
# cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto xenbr0
iface xenbr0 inet static
 address 192.168.1.10
 netmask 255.255.255.0
 network 192.168.1.0
 broadcast 192.168.1.255
 gateway 192.168.1.1
 bridge_ports eth0
 # optional
 bridge_maxwait 0

auto xenbr0
iface xenbr0 inet static
 address 192.168.2.20
 netmask 255.255.255.0
 network 192.168.2.0
 broadcast 192.168.2.255
 gateway 192.168.2.1
 bridge_ports eth0
 # optional
 bridge_maxwait 0
=============================
# cat /etc/xen/xend-config.sxp

(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)
(vncpasswd '')
===============================
# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:0F:FE:6D:F4:E5
         inet6 addr: fe80::20f:feff:fe6d:f4e5/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:55205 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3464 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:11382549 (10.8 MiB)  TX bytes:725505 (708.5 KiB)
         Base address:0x2100 Memory:f0500000-f0520000

eth1      Link encap:Ethernet  HWaddr 00:13:F7:0B:A9:5C
         inet6 addr: fe80::213:f7ff:fe0b:a95c/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:135269 errors:0 dropped:0 overruns:0 frame:0
         TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:39981510 (38.1 MiB)  TX bytes:1588 (1.5 KiB)
         Interrupt:19 Base address:0xa000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:21 errors:0 dropped:0 overruns:0 frame:0
         TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:2376 (2.3 KiB)  TX bytes:2376 (2.3 KiB)

vif8.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
         RX packets:10 errors:0 dropped:0 overruns:0 frame:0
         TX packets:28659 errors:0 dropped:1 overruns:0 carrier:0
         collisions:0 txqueuelen:32
         RX bytes:496 (496.0 b)  TX bytes:6112602 (5.8 MiB)

xenbr0    Link encap:Ethernet  HWaddr 00:0F:FE:6D:F4:E5
         inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::20f:feff:fe6d:f4e5/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:30636 errors:0 dropped:0 overruns:0 frame:0
         TX packets:717 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:6003035 (5.7 MiB)  TX bytes:135514 (132.3 KiB)

xenbr1    Link encap:Ethernet  HWaddr 00:13:F7:0B:A9:5C
         inet addr:192.168.2.20  Bcast:192.168.2.255  Mask:255.255.255.0
         inet6 addr: fe80::213:f7ff:fe0b:a95c/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:82384 errors:0 dropped:0 overruns:0 frame:0
         TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:22305870 (21.2 MiB)  TX bytes:720 (720.0 b)
=============================================
# brctl show

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000ffe6df4e5       no              eth0
                                               vif8.0
xenbr1          8000.0013f70ba95c       no              eth1
============================================

je peux pinger  mon Dom0: 192.168.1.10 and 192.168.2.20

sur mon Dom1, j'ai ajouté

# grep vif /etc/xen/test0.cfg
vif  = [ 'ip=192.168.2.200,bridge=xenbr1' ]

#cat /etc/network/interfaces

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
 address 192.168.2.200
 netmask 255.255.255.0
 network 192.168.2.0
 broadcast 192.168.2.255
 gateway 192.168.2.1
---------

Merci d'avance de vos retours.

ps:

l'erreur ici est que mon Dom1 est dans le "bridge" xenbr0 qui, lui,
utilise l'interface eth0
or moi, j'aimerais qu'il utilise le "bridge" xenbr1 connecté à l'interface eth1

# brctl show

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000ffe6df4e5       no              eth0
                                               vif8.0
xenbr1          8000.0013f70ba95c       no              eth1

_______________________________________________
Xen-fr mailing list
Xen-fr@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-fr

<Prev in Thread] Current Thread [Next in Thread>