thr3ads.net - Xen users - [Xen-users] Question on default xen network configs [Aug 2008]

If this information is useful, please help other people find it:
Share via:

Phil Winterfield (winterfi)

2008-Aug-20 20:41 UTC

[Xen-users] Question on default xen network configs

I have read through the wiki pages and other docs on what happens with
xen network startup (split driver model) and it seems clear enough, but
I am finding that the default configurations aren''t showing the xenbr0
and vif''s.  According to what I have read, this should be done by
default when ''(network-script network-bridge)'' is excuted in
the xend
startup script.  The ifconfig is shown below.  Are there other steps
that are needed to get this default config to show up?

 

Thanks,

Phil

 

[root@localhost ios]# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA  

          inet addr:192.168.102.94  Bcast:192.168.102.95
Mask:255.255.255.224

          inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:715 errors:0 dropped:0 overruns:0 frame:0

          TX packets:347 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:92461 (90.2 KiB)  TX bytes:56883 (55.5 KiB)

 

eth1      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB  

          inet addr:192.168.102.71  Bcast:192.168.102.95
Mask:255.255.255.224

          inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:30 errors:0 dropped:0 overruns:0 frame:0

          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:10710 (10.4 KiB)  TX bytes:8079 (7.8 KiB)

 

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:12 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:964 (964.0 b)  TX bytes:964 (964.0 b)

 

peth0     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA  

          inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1358 errors:0 dropped:0 overruns:0 frame:0

          TX packets:424 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:100 

          RX bytes:154616 (150.9 KiB)  TX bytes:72105 (70.4 KiB)

          Base address:0x2020 Memory:98820000-98840000 

 

peth1     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB

          inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:498 errors:0 dropped:0 overruns:0 frame:0

          TX packets:302 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:100 

          RX bytes:95790 (93.5 KiB)  TX bytes:48500 (47.3 KiB)

          Base address:0x2000 Memory:98800000-98820000 

 

[root@localhost ios]# brctl show

bridge name     bridge id               STP enabled     interfaces

eth0            8000.00151746efca       no              peth0

eth1            8000.00151746efcb       no              peth1

 



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

Asim

2008-Aug-20 21:15 UTC

head link

Re: [Xen-users] Question on default xen network configs

The vifs will show up when you boot a domU.

-Asim

On 8/20/08, Phil Winterfield (winterfi) <winterfi@cisco.com>
wrote:> I have read through the wiki pages and other docs on what happens with
> xen network startup (split driver model) and it seems clear enough, but
> I am finding that the default configurations aren''t showing the
xenbr0
> and vif''s.  According to what I have read, this should be done by
> default when ''(network-script network-bridge)'' is excuted
in the xend
> startup script.  The ifconfig is shown below.  Are there other steps
> that are needed to get this default config to show up?
>
>
>
> Thanks,
>
> Phil
>
>
>
> [root@localhost ios]# ifconfig
>
> eth0      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA
>
>           inet addr:192.168.102.94  Bcast:192.168.102.95
> Mask:255.255.255.224
>
>           inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link
>
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
>           RX packets:715 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:347 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:0
>
>           RX bytes:92461 (90.2 KiB)  TX bytes:56883 (55.5 KiB)
>
>
>
> eth1      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB
>
>           inet addr:192.168.102.71  Bcast:192.168.102.95
> Mask:255.255.255.224
>
>           inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link
>
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
>           RX packets:30 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:0
>
>           RX bytes:10710 (10.4 KiB)  TX bytes:8079 (7.8 KiB)
>
>
>
> 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:12 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:964 (964.0 b)  TX bytes:964 (964.0 b)
>
>
>
> peth0     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA
>
>           inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link
>
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
>           RX packets:1358 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:100
>
>           RX bytes:154616 (150.9 KiB)  TX bytes:72105 (70.4 KiB)
>
>           Base address:0x2020 Memory:98820000-98840000
>
>
>
> peth1     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB
>
>           inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link
>
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
>           RX packets:498 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:302 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:100
>
>           RX bytes:95790 (93.5 KiB)  TX bytes:48500 (47.3 KiB)
>
>           Base address:0x2000 Memory:98800000-98820000
>
>
>
> [root@localhost ios]# brctl show
>
> bridge name     bridge id               STP enabled     interfaces
>
> eth0            8000.00151746efca       no              peth0
>
> eth1            8000.00151746efcb       no              peth1
>
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Phil Winterfield (winterfi)

2008-Aug-20 21:24 UTC

head link

RE: [Xen-users] Question on default xen network configs

Does xenbr0 no longer get displayed?  It doesn''t show up.

Thanks
> -----Original Message-----
> From: Asim [mailto:linkasim@gmail.com]
> Sent: Wednesday, August 20, 2008 2:16 PM
> To: Phil Winterfield (winterfi)
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Question on default xen network configs
> 
> The vifs will show up when you boot a domU.
> 
> -Asim
> 
> On 8/20/08, Phil Winterfield (winterfi) <winterfi@cisco.com> wrote:
> > I have read through the wiki pages and other docs on what happens
with> > xen network startup (split driver model) and it seems clear enough,
but> > I am finding that the default configurations aren''t showing
the
xenbr0> > and vif''s.  According to what I have read, this should be
done by
> > default when ''(network-script network-bridge)'' is
excuted in the
xend> > startup script.  The ifconfig is shown below.  Are there other steps
> > that are needed to get this default config to show up?
> >
> >
> >
> > Thanks,
> >
> > Phil
> >
> >
> >
> > [root@localhost ios]# ifconfig
> >
> > eth0      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA
> >
> >           inet addr:192.168.102.94  Bcast:192.168.102.95
> > Mask:255.255.255.224
> >
> >           inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link
> >
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >
> >           RX packets:715 errors:0 dropped:0 overruns:0 frame:0
> >
> >           TX packets:347 errors:0 dropped:0 overruns:0 carrier:0
> >
> >           collisions:0 txqueuelen:0
> >
> >           RX bytes:92461 (90.2 KiB)  TX bytes:56883 (55.5 KiB)
> >
> >
> >
> > eth1      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB
> >
> >           inet addr:192.168.102.71  Bcast:192.168.102.95
> > Mask:255.255.255.224
> >
> >           inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link
> >
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >
> >           RX packets:30 errors:0 dropped:0 overruns:0 frame:0
> >
> >           TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
> >
> >           collisions:0 txqueuelen:0
> >
> >           RX bytes:10710 (10.4 KiB)  TX bytes:8079 (7.8 KiB)
> >
> >
> >
> > 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:12 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:964 (964.0 b)  TX bytes:964 (964.0 b)
> >
> >
> >
> > peth0     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA
> >
> >           inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link
> >
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >
> >           RX packets:1358 errors:0 dropped:0 overruns:0 frame:0
> >
> >           TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
> >
> >           collisions:0 txqueuelen:100
> >
> >           RX bytes:154616 (150.9 KiB)  TX bytes:72105 (70.4 KiB)
> >
> >           Base address:0x2020 Memory:98820000-98840000
> >
> >
> >
> > peth1     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB
> >
> >           inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link
> >
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >
> >           RX packets:498 errors:0 dropped:0 overruns:0 frame:0
> >
> >           TX packets:302 errors:0 dropped:0 overruns:0 carrier:0
> >
> >           collisions:0 txqueuelen:100
> >
> >           RX bytes:95790 (93.5 KiB)  TX bytes:48500 (47.3 KiB)
> >
> >           Base address:0x2000 Memory:98800000-98820000
> >
> >
> >
> > [root@localhost ios]# brctl show
> >
> > bridge name     bridge id               STP enabled     interfaces
> >
> > eth0            8000.00151746efca       no              peth0
> >
> > eth1            8000.00151746efcb       no              peth1
> >
> >
> >
> >
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Asim

2008-Aug-20 21:33 UTC

head link

Re: [Xen-users] Question on default xen network configs

As evident from your brctl command - your bridges are called eth0 and
eth1 and they are being displayed. Did past versions of Xen call them
as xenbr0 - I don''t know but the point is - it(xenbr0) is not relevant
here.

-Asim

On 8/20/08, Phil Winterfield (winterfi) <winterfi@cisco.com>
wrote:> Does xenbr0 no longer get displayed?  It doesn''t show up.
>
> Thanks
>
>> -----Original Message-----
>> From: Asim [mailto:linkasim@gmail.com]
>> Sent: Wednesday, August 20, 2008 2:16 PM
>> To: Phil Winterfield (winterfi)
>> Cc: xen-users@lists.xensource.com
>> Subject: Re: [Xen-users] Question on default xen network configs
>>
>> The vifs will show up when you boot a domU.
>>
>> -Asim
>>
>> On 8/20/08, Phil Winterfield (winterfi) <winterfi@cisco.com>
wrote:
>> > I have read through the wiki pages and other docs on what happens
> with
>> > xen network startup (split driver model) and it seems clear
enough,
> but
>> > I am finding that the default configurations aren''t
showing the
> xenbr0
>> > and vif''s.  According to what I have read, this should be
done by
>> > default when ''(network-script network-bridge)''
is excuted in the
> xend
>> > startup script.  The ifconfig is shown below.  Are there other
steps
>> > that are needed to get this default config to show up?
>> >
>> >
>> >
>> > Thanks,
>> >
>> > Phil
>> >
>> >
>> >
>> > [root@localhost ios]# ifconfig
>> >
>> > eth0      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA
>> >
>> >           inet addr:192.168.102.94  Bcast:192.168.102.95
>> > Mask:255.255.255.224
>> >
>> >           inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link
>> >
>> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >
>> >           RX packets:715 errors:0 dropped:0 overruns:0 frame:0
>> >
>> >           TX packets:347 errors:0 dropped:0 overruns:0 carrier:0
>> >
>> >           collisions:0 txqueuelen:0
>> >
>> >           RX bytes:92461 (90.2 KiB)  TX bytes:56883 (55.5 KiB)
>> >
>> >
>> >
>> > eth1      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB
>> >
>> >           inet addr:192.168.102.71  Bcast:192.168.102.95
>> > Mask:255.255.255.224
>> >
>> >           inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link
>> >
>> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >
>> >           RX packets:30 errors:0 dropped:0 overruns:0 frame:0
>> >
>> >           TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
>> >
>> >           collisions:0 txqueuelen:0
>> >
>> >           RX bytes:10710 (10.4 KiB)  TX bytes:8079 (7.8 KiB)
>> >
>> >
>> >
>> > 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:12 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:964 (964.0 b)  TX bytes:964 (964.0 b)
>> >
>> >
>> >
>> > peth0     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA
>> >
>> >           inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link
>> >
>> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >
>> >           RX packets:1358 errors:0 dropped:0 overruns:0 frame:0
>> >
>> >           TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
>> >
>> >           collisions:0 txqueuelen:100
>> >
>> >           RX bytes:154616 (150.9 KiB)  TX bytes:72105 (70.4 KiB)
>> >
>> >           Base address:0x2020 Memory:98820000-98840000
>> >
>> >
>> >
>> > peth1     Link encap:Ethernet  HWaddr 00:15:17:46:EF:CB
>> >
>> >           inet6 addr: fe80::215:17ff:fe46:efcb/64 Scope:Link
>> >
>> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >
>> >           RX packets:498 errors:0 dropped:0 overruns:0 frame:0
>> >
>> >           TX packets:302 errors:0 dropped:0 overruns:0 carrier:0
>> >
>> >           collisions:0 txqueuelen:100
>> >
>> >           RX bytes:95790 (93.5 KiB)  TX bytes:48500 (47.3 KiB)
>> >
>> >           Base address:0x2000 Memory:98800000-98820000
>> >
>> >
>> >
>> > [root@localhost ios]# brctl show
>> >
>> > bridge name     bridge id               STP enabled     interfaces
>> >
>> > eth0            8000.00151746efca       no              peth0
>> >
>> > eth1            8000.00151746efcb       no              peth1
>> >
>> >
>> >
>> >
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Todd Deshane

2008-Aug-21 02:36 UTC

head link

Re: [Xen-users] Question on default xen network configs

On Wed, Aug 20, 2008 at 5:24 PM, Phil Winterfield (winterfi)
<winterfi@cisco.com> wrote:> Does xenbr0 no longer get displayed?  It doesn''t show up.
As of Xen 3.2, the bridges are no longer xenbr* and instead are eth*

Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

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

Artur Linhart - Linux communication

2008-Aug-27 15:46 UTC

head link

RE: [Xen-users] Question on default xen network configs

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...

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...

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?

Cheers, Archie

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Todd Deshane
Sent: Thursday, August 21, 2008 4:36 AM
To: Phil Winterfield (winterfi)
Cc: xen-users@lists.xensource.com; Asim
Subject: Re: [Xen-users] Question on default xen network configs

On Wed, Aug 20, 2008 at 5:24 PM, Phil Winterfield (winterfi)
<winterfi@cisco.com> wrote:> Does xenbr0 no longer get displayed?  It doesn''t show up.
As of Xen 3.2, the bridges are no longer xenbr* and instead are eth*

Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

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

This email was Anti Virus checked by Astaro Security Gateway.
http://www.astaro.com


__________ Informace od NOD32 3373 (20080821) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz



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

Todd Deshane

2008-Aug-27 19:09 UTC

head link

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@bcpraha.com> 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

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

Artur Linhart - Linux communication

2008-Aug-28 08:00 UTC

head link

RE: [Xen-users] Question on default xen network configs

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@gmail.com] 
Sent: Wednesday, August 27, 2008 9:09 PM
To: Artur Linhart - Linux communication
Cc: Phil Winterfield (winterfi); xen-users@lists.xensource.com; 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@bcpraha.com> 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@lists.xensource.com
http://lists.xensource.com/xen-users

Todd Deshane

2008-Aug-28 13:47 UTC

head link

Re: [Xen-users] Question on default xen network configs

On Thu, Aug 28, 2008 at 4:00 AM, Artur Linhart - Linux communication
<AL.LINUX@bcpraha.com> wrote:> Hello,
>
>  Thank You for response ;-)
>
>  I work with Debian Etch.
>
One question I still have, is the network-manager packages installed?
>  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.
>
So you are asking for a bridge that doesn''t have an external address,
and
further, you want the domU to get an address through that bridge right?

I don''t know if it is possible or not, but you could do a simple test
to see

add the following to your /etc/network/interfaces

auto br0
  bridge_ports eth0
  bridge_fd 9
  bridge_hello 2
  bridge_maxage 12
  bridge_stp offi

eth0 can be replaced with any eth* that you want to use as your
bridge port.

Then configure a test domU to use bridge=br0 as its vif option.

If the domU can get an address and get out, then you are successful,
If it can''t then my best guess is that it probably won''t work
(or there is
another way that I don''t know about)

Hope that helps,
Cheers,
Todd

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

Xen users - Aug 2008 - Question on default xen network configs

[Xen-users] Question on default xen network configs

Re: [Xen-users] Question on default xen network configs

RE: [Xen-users] Question on default xen network configs

Re: [Xen-users] Question on default xen network configs

Re: [Xen-users] Question on default xen network configs

RE: [Xen-users] Question on default xen network configs

Re: [Xen-users] Question on default xen network configs

RE: [Xen-users] Question on default xen network configs

Re: [Xen-users] Question on default xen network configs