All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ron Watkins" <xen-devel@malor.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: ARP problems in -testing?
Date: Sun, 16 Jan 2005 13:33:04 -0500	[thread overview]
Message-ID: <000f01c4fbf9$d12f4120$32dcdc0a@vanish> (raw)
In-Reply-To: A95E2296287EAD4EB592B5DEEFCE0E9D12337F@liverpoolst.ad.cl.cam.ac.uk

Well, I could certainly be doing something wrong.  That's why I'm asking if 
it's a bug, not saying definitely that it is. :-)

If I ping the guest domain from dom0, while running tcpdump in the slave 
domain, I do see arp requests and replies working.  I can be pinging from 
dom0 to the slave and getting answers back at the EXACT SAME TIME that I am 
pinging from outside... the dom0 pings work, the outside pings arrive and go 
unanswered.  As soon as I ping something from within the slave domain, the 
connection wakes up and works normally.

I have attached a redacted tcpdump text file... I have replaced the IP 
addresses, but it is otherwise exact.  You will see that I am pinging from 
69.0.0.74 to 69.0.0.77 (the master to the slave), which is working, while 
simultaneous requests from 24.0.0.10 go unanswered.   There are correct arp 
request/reply packets, it's working, at least, over the virtual link.

The way this colocated server is configured:

network (wire) address 69.0.0.72/29
Router:  69.0.0.73
Domain0: 69.0.0.74
slave1: .75
slave2: .76
slave 3: .77  (this is the one I was using for testing)
slave 4: .78 (not yet active)
broadcast: .79

I just started on the list today and don't have any idea what you're talking 
about wrt a routed setup...  but if it's just now been checked in, it's 
probably not in my code anyway.  I'm in -testing, not -unstable.

(I won't bother redacting the server ips anymore if I post anything else, 
anyone with half an ounce of brains is going to figure it out anyway.  I 
will continue to change my client IP, however.)



-------------------------------------------------------
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-16 18:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 17:46 ARP problems in -testing? Ian Pratt
2005-01-16 18:33 ` Ron Watkins [this message]
2005-01-16 18:51   ` Ron Watkins
  -- strict thread matches above, loose matches on Subject: below --
2005-01-17 14:08 Tim Durack
2005-01-17  1:41 Ian Pratt
2005-01-17  1:23 Ian Pratt
2005-01-17  2:03 ` Adam Sulmicki
2005-01-16 16:42 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
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

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='000f01c4fbf9$d12f4120$32dcdc0a@vanish' \
    --to=xen-devel@malor.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.