From: Kip Macy <kip.macy@gmail.com>
To: Ian.Pratt@cl.cam.ac.uk, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: any recent changes to bridging or networking in -testing?
Date: Sun, 20 Mar 2005 17:31:00 -0800 [thread overview]
Message-ID: <b1fa291705032017315b8ce490@mail.gmail.com> (raw)
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
RX packets:1095 errors:0 dropped:0 overruns:0 frame:0
TX packets:1796 errors:0 dropped:4992 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:95605 (93.3 Kb) TX bytes:1094883 (1.0 Mb)
xen-br0 Link encap:Ethernet HWaddr 00:50:45:01:03:64
inet addr:172.16.9.204 Bcast:172.16.9.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4519788 errors:0 dropped:0 overruns:0 frame:0
TX packets:4291000 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1225490467 (1168.7 Mb) TX bytes:1151961147 (1098.5 Mb)
>From my -testing machine:
vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xen-br0 Link encap:Ethernet HWaddr 00:50:45:01:03:3A
inet addr:172.16.9.203 Bcast:172.16.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:122068 errors:0 dropped:0 overruns:0 frame:0
TX packets:32185 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:151662080 (144.6 Mb) TX bytes:10634890 (10.1 Mb)
Any suggestions?
-Kip
-------------------------------------------------------
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-21 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 1:31 Kip Macy [this message]
2005-03-21 1:53 ` any recent changes to bridging or networking in -testing? Fajar A. Nugraha
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=b1fa291705032017315b8ce490@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.