All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Kundrát" <jan.kundrat@fzu.cz>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: network dropouts
Date: Mon, 13 Dec 2004 21:08:51 +0100	[thread overview]
Message-ID: <41BDF6D3.4080909@fzu.cz> (raw)
In-Reply-To: <41BCAB6E.8090608@fzu.cz>

So, network availability drops out even without unprivileged domains. 
I'm using default xen configuration, machines are on the same subnet 
(10.8.6.61 and 10.18.6.60), connected by switch.

Does it matter that Gentoo (in current stable version) uses `ifconfig` 
and `route` to setup networking and /etc/xen/scripts/network uses 
iproute2 package? It shouldn't, AFAIK.

One thing that I don't understand is that `ifconfig` shows that eth0 
holds its IP address even after xen-br0 has been brought up (and xen-br0 
has /32 netmask...):
(lo removed from output)

eth0      Link encap:Ethernet  HWaddr 00:10:4B:B6:BD:0E
           inet addr:10.18.6.60  Bcast:10.18.6.63  Mask:255.255.255.192
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:7484 errors:0 dropped:0 overruns:0 frame:0
           TX packets:3407 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:872358 (851.9 Kb)  TX bytes:481887 (470.5 Kb)
           Interrupt:11 Base address:0xe400

xen-br0   Link encap:Ethernet  HWaddr 00:10:4B:B6:BD:0E
           inet addr:10.18.6.60  Bcast:10.18.6.63  Mask:255.255.255.255
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:4554 errors:0 dropped:0 overruns:0 frame:0
           TX packets:2630 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:397202 (387.8 Kb)  TX bytes:389085 (379.9 Kb)



jkt

-- 
cd /local/pub && more beer > /dev/mouth



-------------------------------------------------------
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://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-13 20:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12 20:34 network dropouts Jan Kundrát
2004-12-13 20:08 ` Jan Kundrát [this message]
2004-12-14 11:04   ` Ian Pratt
2004-12-14 11:27     ` Jan Kundrát
2004-12-14 11:36       ` Keir Fraser
2004-12-17 18:37         ` Jan Kundrát
2004-12-17 20:06           ` Keir Fraser
2004-12-17 20:25             ` Jan Kundrát
2004-12-17 20:54               ` Keir Fraser
2004-12-17 21:03                 ` Jan Kundrát
2004-12-17 21:18                   ` Jan Kundrát
2004-12-17 20:36             ` Jan Kundrát
2004-12-15 14:58       ` Jan Kundrát
2004-12-14 16:43     ` Nivedita Singhvi

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=41BDF6D3.4080909@fzu.cz \
    --to=jan.kundrat@fzu.cz \
    --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.