Re: [Xen-users] XEN Network configuration

[Net Warrior <netwarrior863@xxxxxxxxx>]

On 07/04/10 23:58, Fajar A. Nugraha wrote:
> On Mon, Jul 5, 2010 at 9:45 AM, Net Warrior <netwarrior863@xxxxxxxxx> wrote:
>   
>> Hi there.
>>
>> I need some advice about how to set up my network, I'm a bit confused.
>>
>> First, all the docs I read talk about a xenbr0 interfase which I do not
>> have, I only have eth0 of course and peth0.
>>     
> Old Xen version use xenbr0 as the default bridge name.
> Newer Xen version use eth0 as the default bridge name
>
>   
>> eth0 is wired to the internet with a public IP, peth0 has no ip.
>> So i do not know how to handle peth0 in order to enable the DomU gests
>> to connect to the internet.
>>
>> xend-config looks like this.
>>
>> (network-script network-bridge)
>> (vif-script vif-bridge)
>>
>> Do not know if my DomU config file should be
>> vif = [ 'bridge=eth0' ]
>> vif = [ 'bridge=xenbr0' ]
>> vif = [ 'bridge=peth0' ]
>> vif = [ip=x.x.x.x ]
>>     
> run "brctl show"
> look at the column "bridge name". I suggest you add static MAC address
> there as well, to prevent domU from detecting MAC address changes and
> (in some distros) assign new device names  every time domU boots. I
> also like to put custom vif name, so I'd get more meaningful entry in
> dom0 (e.g. when doing "brctl show") instead of just something like
> "vif5.0".
>
> My entry for bridge networking is something like this (note that I use
> custom bridge)
>
>
> vif = [
>       'mac=00:16:3E:52:CB:78, bridge=br129, vifname=ubuntu-eth0'
>       ]
>
> Also note that the default bridge networking (in your case, using eth0
> bridge) means domU will be using the same method as dom0 to get its IP
> address. This is fine when you're in a LAN with dhcp enabled. It might
> became a problem, however, for some dom0 networking setup (for
> example, if the dom0 needs to use pptp to get internet access)
>
>   

Thank you, I've done that.

 eth0  inet addr:x.x.x.x  Bcast:0.0.0.0  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2620069 errors:0 dropped:0 overruns:0 frame:0
          TX packets:312635 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:659430301 (628.8 MiB)  TX bytes:27199638 (25.9 MiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:15326 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15326 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:64535771 (61.5 MiB)  TX bytes:64535771 (61.5 MiB)

peth0     Link encap:Ethernet  HWaddr 00:21:86:94:c5:c0 
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:2620212 errors:0 dropped:0 overruns:0 frame:0
          TX packets:312785 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:696116739 (663.8 MiB)  TX bytes:27224805 (25.9 MiB)
          Interrupt:154 Base address:0x2000

ubuntu904 Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff 
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:103 errors:0 dropped:0 overruns:0 frame:0
          TX packets:962174 errors:0 dropped:1399 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:8573 (8.3 KiB)  TX bytes:57825325 (55.1 MiB)


Now, what should I do now, add an reserved range IP address to the host
like 192.x.x.x and use iptables to filter the packages of the filter is
done automatically by the peth/vif.X? I tried to assign an IP like that
to the host ( within the host and from the DomU config file ) and still
cannot reach internet, I copied the resolv.conf from dom0 to domU just
in case.

Thanks for your time and support
Regards




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