Hi *
First of all, let me say that I have almost no knowledge about how
networks works. I must fill this gap soon.
So, don't feel obliged to completely answer my question(s). I only
expect some tips/clues to start with.
What I have:
1) A dom0 server with 2 NIC cards (eth0, eth1), running centOS52 xen 3.2.
2) A switch to a VLAN with several physical machines (already up and
running).
What I need:
1) A domU with a static IP and also connected to the VLAN.
My plan:
1) use dom0 eth0 to connect to the outside world; domU will use it also
to connect to the outside (this is the default anyway).
2) use dom0 eth1 to connect domU to the switch connected to the VLAN.
Do not know if this makes much sense, it makes to me at least,.
My progress:
Till now, all my created domU's (each with a static IP) were connecting
to the web through xenbr0. The second NIC on dom0 was not being used at
all. The xen config file pointed to xenbr0, and I only had to change
inside the domU the network configurations (/etc/sysconfig/network and
/etc/sysconfig/network-scripts-eth0). An ifconfig on the host shows me
the following network components (deleted not so important stuff):
[root@dom0 ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:81:4D:30:D0
inet addr:132.212.155.68 Bcast:132.212.155.255
Mask:255.255.255.0
inet6 addr: fe80::2e0:81ff:fe4d:30d0/64 Scope:Link
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
If I activate the 2nd dom0 NIC and connect it to the switch of the VLAN,
after a dom0 reboot I have:
[root@dom0 ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:81:4D:30:D0
inet addr:132.212.155.68 Bcast:132.212.155.255
Mask:255.255.255.0
inet6 addr: fe80::2e0:81ff:fe4d:30d0/64 Scope:Link
eth0 Link encap:Ethernet HWaddr 00:E0:81:4D:30:D1
inet addr:10.0.0.49 Bcast:10.0.0.255 Mask:255.255.255.0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
So it seems that the dom0 is well configured, both to the outside world
and to the VLAN. Though I thought 2 xen bridges should appear ... one
for each NIC card?
I booted a domU (after changing in the xen cfg file xenbr0 to xenbr1)
created is this machine (when the eth1 was still inactivated) and I had
problems because Kudzu detected a change in the network configuration.
So probably, I should create the domU when both dom0 NIC cards are
active, right?
How can I accomplish my 2 goals above on "My plans" section?
Any insights for me to start playing?
Sorry for such long e-mail, and thanks for your reading.
Cheers,
N.
--
==============================================
Nuno Ricardo Santos Loureiro da Silva Ferreira
NMR Spectroscopy Research Group
Bijvoet Center for Biomolecular Research
Utrecht University
Bloembergen gebouw
Padualaan 8, 3584 CH Utrecht
The Netherlands
P: +31.(0)30.253 9932
F: +31.(0)30.253 2652
E: n.l.ferreira@xxxxx
W: http://nmr.chem.uu.nl
==============================================
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
| 
Home