Hello,
Thank You for response ;-)
I work with Debian Etch.
My point is, why have I to define the IP address in Dom0 if I want to use
the bridge for the DomU? I do not want the Dom0 has also the IP address on
that interface, which receives the traffic for DomU - mainly from security
and configuration effort reasons.
I do not understand why if my bridge is cofigured properly:
wonderland:/# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.001517708dbc no peth0
eth1 8000.001517708dbd no peth1
vif4.0
eth2 8000.000423e45f5a no peth2
eth4 8000.000c42072d75 no peth4
eth5 8000.000c42072d74 no peth5
eth6 8000.000c42072d77 no peth6
wonderland:/#
and on eth1 the vif4.0 exists on peth1, why there comes no traffic through?
In the DomU if I ping something, i just get always the "destination host
unreachable" error, the DomU also cannot be pinged from outside...
In iptables I have in forward chain following line
ACCEPT 0 -- anywhere anywhere PHYSDEV match
--physdev-in vif4.0
What looks to be also correct for me...
Also in ifconfig the part relevant for this case looks good I think...
So, where can be the problem? Why have I to define the IP addres in Dom0 to
get it working?
With regards, Archie
-----Original Message-----
From: Todd Deshane [mailto:deshantm@xxxxxxxxx]
Sent: Wednesday, August 27, 2008 9:09 PM
To: Artur Linhart - Linux communication
Cc: Phil Winterfield (winterfi); xen-users@xxxxxxxxxxxxxxxxxxx; Asim
Subject: Re: [Xen-users] Question on default xen network configs
Hello,
On Wed, Aug 27, 2008 at 11:46 AM, Artur Linhart - Linux communication
<AL.LINUX@xxxxxxxxxxx> wrote:
> Hello,
>
> are there any other conditions what to define in xen 3.2.1 in the
> comparison with Xen 3.1.0? My problem is, the bridge is not working till I
> do not define the corresponding eth device and the IP addresses for it in
> /etc/network/interfaces. My DomUs are not accessible through the network
> till I did not define the corresponding eth device in the config file and
> till the Dom0's eth is not accessible throught the IP protocol...
>
It sounds like you are using Ubuntu, the issue here is likely that you have
network manager installed and it doesn't define the network devices in
/etc/network/interfaces.
> In xen 3.1.0 it was much more better - I defined the network bridges
> independently on the vast if the Dom0 "knows" the IP network connected to
> the physical interfaces...
>
This is probably an issue of Xen on <your distro> not being network manager
aware.
> Or do I some mystake and have there some misconfiguration? Re there any
new
> schemes according to the bridges? Can I use the old-style bridging, where
it
> is not necessary to define the corresponding eth device in Dom0 to get
DomU
> working on the interface?
>
You can define your own bridges and that will work fine, but you have
to make sure
all your configurations are updated (i.e. guest configs and if you
specify anything in
the xend config, etc.)
Hope that helps,
Cheers,
Todd
--
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com
This email was Anti Virus checked by Astaro Security Gateway.
http://www.astaro.com
__________ Informace od NOD32 3394 (20080827) __________
Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users