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

Re: [Xen-users] trouble installing


  • To: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • From: Ted Brenner <griztown@xxxxxxxxx>
  • Date: Wed, 23 Feb 2011 07:38:39 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 23 Feb 2011 05:40:14 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=N/ONAOSF0Odazd+Cj1z2iKkQW7ODr5Z6sowAITANJvhZ4noI6xT/RblqqGhpFlx6YY +XZHCSBYY7rUXTayGJZVUXuSmpa4XgmtVD72R3j5cZFrmY3h8dEWErfO5o7qgMSe5UN+ LoHNBGZ9QUvoohov7Vz5Hp09wIHa1UMnIc8pQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Thanks Fajar and Pasi,

I'm not sure how to add my IP to the bridge.  It tells me 10.0.0.3 is not an interface.  I'm sorry if I don't know much about networking.

Here's my /etc/network/interface

# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp

# brctl show
bridge name    bridge id        STP enabled    interfaces
br0        8000.000000000000    no       

# ip ad sh br0
4: br0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

# ip ad sh eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
    inet6 fe80::225:22ff:fe8d:84b2/64 scope link
       valid_lft forever preferred_lft forever


On Wed, Feb 23, 2011 at 6:47 AM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
On Wed, Feb 23, 2011 at 6:57 PM, Ted Brenner <griztown@xxxxxxxxx> wrote:
> Thanks Pasi,
>
> I did that but now the internet doesn't work on either domU or dom0.  Here's
> my bridge status.
>
> # /etc/xen/scripts/network-bridge status

Why would you run that command? You commented-out the script from
xend.sxp earlier, right?

> bridge name    bridge id        STP enabled    interfaces
> br0        8000.0025228d84b2    no                 eth0
>                                                                   vif1.0
>
> 10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.3  metric 1
> default via 10.0.0.1 dev eth0  proto static
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 10.0.0.0        0.0.0.0         255.255.255.0   U     1      0        0 eth0
> 0.0.0.0         10.0.0.1        0.0.0.0         UG    0      0        0 eth0

That's wrong. Let's start with some simple things:
- if you use OS network script do NOT touch
/etc/xen/scripts/network-bridge again. Ever.
- The sample http://wiki.debian.org/BridgeNetworkConnections is good,
although it uses both eth0 and eth1. You most likely only need one
(eth0).
- Put your dom0 IPs on the bridge (in your case, br0), and NOT the
interface member (eth0).

The wiki provides good example for both dhcp and static ip address on
br0. Why aren't you following that? From the output you sent it looks
like you're still putting IP addresses on eth0, not br0.

Go back and create a correct config for dom0 bridge using
/etc/network/interfaces. Don't start any domU yet. Verify network
connection is running fine on dom0. THEN create a domU.

If you're still having problems, paste:
- your /etc/network/interfaces
- output of "brctl show", "ip ad sh br0", "ip ad sh eth0" (to make
sure interfaces are up and properly configured)
- netstat -nr (to make sure routing is properly configured)

--
Fajar



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

 


Rackspace

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