From: Bharadwaj Yadavalli <bharadwaj.yadavalli@hp.com>
To: xen-devel@lists.sourceforge.net
Subject: [Q] eth0 not up on dom0
Date: Thu, 24 Mar 2005 16:31:22 -0500 [thread overview]
Message-ID: <20050324213122.GC23485@java.zko.dec.com> (raw)
Apologies if this is trivial and an FAQ. Google search
hasn't helped.
I have been unsuccessful in getting eth0 interface up in
dom0. My linux installation is FC3 and I get my address via
DHCP. I am running Linux 2.6.11-xen0. I see the following
steps recommended in the bridge-utils HOWTO page
1. Zero IP the interfaces. The bridge needs the network
devices to be operational, but without TCP/IP running on
them.
# ifconfig eth0 0.0.0.0
2. Create the bridge interface.
# brctl addbr mybridge
3. Add interfaces to the bridge.
# brctl addif mybridge eth0
[I believe steps 2 amd 3 will be done by executing
xend start. I verified this by running 'brctl show'
after I ran 'xend start']
4. Put up the bridge.
# ifconfig xen-br0 up
Now that I have the bridge up, I tried running
ifup eth0
to get an IP address.
I get the following:
"Determining IP information for eth0...PING
<my.dhcp.server.address> from
<what-I-think.is-the-IP.address.I-was-assigned>: eth0"
[usual ping statistics stuff]
failed.
I suspect I am close but not there. Can someone provide the
nudge please?
Thanks,
Bharadwaj
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-24 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 21:31 Bharadwaj Yadavalli [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 21:42 [Q] eth0 not up on dom0 Ian Pratt
2005-03-25 16:56 ` Bharadwaj Yadavalli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050324213122.GC23485@java.zko.dec.com \
--to=bharadwaj.yadavalli@hp.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.