[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] DHCP / Ubuntu



Phil Lello <phil@xxxxxxxxxxxxxxx> wrote:

> /etc/default/interfaces includes:
> 
> auto xenbr0
> iface xenbr0 inet static
>     address 192.168.1.1
>     network 192.168.1.0
>     netmask 255.255.255.0
>     broadcast 192.168.1.255
>     pre-up brctl addbr $IFACE
>     up ip link set $IFACE up
>     post-down brctl delbr $IFACE
>     down ip link set $IFACE down

That's an old way of doing it. These days the OS will take care of it by itself 
- at least Debian has for a long time, I assume Ubuntu has followed suit.

auto xenbr0
iface xenbr0 inet static
  bridge_ports eth0
  address 192.168.1.1
  netmask 255.255.255.0

I don't bother specifying network or broadcast - it's just more to get wrong 
and the system will figure them out automatically.

Also, you want to make sure there are no "network managers" or similar running 
- for this sort of system they are not needed and will just get in the way.

> vif = [ 'script=vif-route' ]

I prefer to explicitly specify the bridge - partly because all of my hosts have 
multiple bridges configured.
vif = [ 'script=vif-route,bridge=xenbr0' ]

Other than that I can see one reason it might not work. The ISC server only 
supports broadcast interfaces* - and I don't know  whether a direct attachment 
to a bridge like that looks enough like an ethernet interface to work. What 
does the server log as it starts up ?

It's to do with the way it must bypass the IP stack for some operations.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.