[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: Packets dropped if no ARP entry


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Peter Mellon <knascent@xxxxxxxxx>
  • Date: Thu, 18 Jun 2009 08:53:23 -0400
  • Delivery-date: Thu, 18 Jun 2009 05:54:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=xJUopHdNzthgw/opDMoRNWWGpocNunXBEN1u0jWmW93Q227vDOaMqDPemTDsGf5qxJ grniPfcr6+WgViUfBUJyW0RfXA2hjqE3GZLyLzliWKdSVfBgYxJSK13H1smEhl85pscd uVdCB1KJIoKDZ+WjGZtuXHtzZJp6yZlJsQYaQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Okay, it turns out the problem is more simple than I thought (but I still don't know how to solve it). So ignore my previous post, here is what is happening:

On a normal kernel, successful pings shows up on tcpdump and Wireshark

On the xen kernel, successful pings do not show up on tcpdump or Wireshark. BUT, other packets like SSH connections do.

Anyone know why this is happening?

On Wed, Jun 17, 2009 at 2:20 PM, Peter Mellon <knascent@xxxxxxxxx> wrote:
Hey everyone, I have a machine A with IP address 192.168.2.2. It is connected to another computer B that doesn't have an IP address (I'm using that computer as a bridge for another program).
 
Using a normal 2.6 kernel on B, if I ping from A to another computer on the same subnet, say '192.168.2.1', here is the output of tcpdump on B
 
[root@server5 ~]# tcpdump -i eth3
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth3, link-type EN10MB (Ethernet), capture size 96 bytes
09:54:45.834857 arp who-has 192.168.2.1 tell 192.168.2.2
09:54:46.834858 arp who-has 192.168.2.1 tell 192.168.2.2
09:54:47.834859 arp who-has 192.168.2.1 tell 192.168.2.2
09:54:49.834856 arp who-has 192.168.2.1 tell 192.168.2.2
09:54:50.834855 arp who-has 192.168.2.1 tell 192.168.2.2
09:54:51.834855 arp who-has 192.168.2.1 tell 192.168.2.2
 
6 packets captured
6 packets received by filter
0 packets dropped by kernel
 
This is good, it is what I'm looking for. If instead I use the xen kernel on B and everything else is exactly the same, here is the output (in dom0; no virtual machines installed yet):
 
[root@server5 ~]# tcpdump -i eth3
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth3, link-type EN10MB (Ethernet), capture size 96 bytes
 
0 packets captured
5 packets received by filter
5 packets dropped by kernel
 
As you can see, 5 packets because of the ping were received, but the xen kernel drops all of them. Anyone know how I can make the kernel accept them?
 
Thanks

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.