All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrik Pates <demon@devrandom.net>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "Jan Kundrát" <jan.kundrat@fzu.cz>,
	"Ron Watkins" <xen-devel@malor.com>,
	xen-devel@lists.sourceforge.net
Subject: Re: ARP problems in -testing?
Date: Sun, 16 Jan 2005 19:27:36 -0500	[thread overview]
Message-ID: <41EB0678.4070707@devrandom.net> (raw)
In-Reply-To: <E1CqGkT-00040k-00@mta1.cl.cam.ac.uk>

Keir Fraser wrote:
> The MAC addresses from the tcpdump log look sane. The problem must lie
> elsewhere. 

I just tried this on a dedicated server located at thePlanet in Texas; I 
think this is an issue that combines the following:

   - No MAC address specified causes a random MAC address to be selected 
at domain create time
   - The upstream router has a local ARP cache
   - The host system's ARP cache for addresses on the virtual NIC for 
the instance is blown out when the virtual interface disappears when the 
domain is destroyed

This seems to explain why tcpdump shows packets going to the VM's IP, 
but TCP sessions and ICMP packets don't get a response - the switch 
still knows the "old" MAC address, but the first outbound packet to the 
outside world implicitly eradicates the old ARP-cache entry. I don't 
think this is Xen's fault at all, just a property of the implementation 
of ARP resolution. I just happened to notice that the MAC shown in 
incoming packets didn't match the current MAC address (based on 
ifconfig's output), so this is my current theory on what's happening.

-- 
Derrik Pates
demon@devrandom.net


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-17  0:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 16:42 ARP problems in -testing? Ron Watkins
2005-01-16 18:30 ` Felipe Alfaro Solana
2005-01-16 18:49   ` Ron Watkins
2005-01-16 19:18     ` Jan Kundrát
2005-01-16 20:11       ` Keir Fraser
2005-01-17  0:27         ` Derrik Pates [this message]
2005-01-17  0:58           ` Felipe Alfaro Solana
2005-01-17  1:33             ` Adam Sulmicki
2005-01-17 13:41             ` Keir Fraser
2005-01-17 14:27               ` Felipe Alfaro Solana
2005-01-17 10:39           ` Ron Watkins
2005-01-17 11:14             ` Keir Fraser
2005-01-16 22:44       ` Felipe Alfaro Solana
2005-01-16 22:39     ` Felipe Alfaro Solana
  -- strict thread matches above, loose matches on Subject: below --
2005-01-16 17:46 Ian Pratt
2005-01-16 18:33 ` Ron Watkins
2005-01-16 18:51   ` Ron Watkins
2005-01-17  1:23 Ian Pratt
2005-01-17  2:03 ` Adam Sulmicki
2005-01-17  1:41 Ian Pratt
2005-01-17 14:08 Tim Durack

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=41EB0678.4070707@devrandom.net \
    --to=demon@devrandom.net \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=jan.kundrat@fzu.cz \
    --cc=xen-devel@lists.sourceforge.net \
    --cc=xen-devel@malor.com \
    /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.