All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fajar A. Nugraha" <fajar@telkom.co.id>
To: xen-devel@lists.sourceforge.net
Subject: Re: any recent changes to bridging or networking in -testing?
Date: Mon, 21 Mar 2005 08:53:06 +0700	[thread overview]
Message-ID: <423E2902.6000502@telkom.co.id> (raw)
In-Reply-To: <b1fa291705032017315b8ce490@mail.gmail.com>

Kip Macy wrote:

>I'm using the exact same setup as I've successfully been using for
>both -testing and -unstable. However, at least as of today, guests on
>-testing can't see the network.
>
>>From my -unstable machine:
>vif13.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>  
>
[snip]

>>From my -testing machine:
>vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
>          BROADCAST MULTICAST  MTU:1500  Metric:1
>  
>
I believe this is the problem (no UP there).
I get the same result installing from 
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0.5-src.tgz.
At that point I assumed I messed up install procedure somewhere, and 
simply copied the file /etc/xen/scripts/vif-bridge from another box with 
older xen version. I think the line "ifconfig ${vif} $OP" is missing.

Regards,

Fajar


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

  reply	other threads:[~2005-03-21  1:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21  1:31 any recent changes to bridging or networking in -testing? Kip Macy
2005-03-21  1:53 ` Fajar A. Nugraha [this message]
2005-03-21  2:00   ` Kip Macy

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=423E2902.6000502@telkom.co.id \
    --to=fajar@telkom.co.id \
    --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.