This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 21] Service detection through mDNS does not work

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 21] Service detection through mDNS does not work
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 05 May 2005 22:15:59 +0000
Delivery-date: Thu, 05 May 2005 22:16:03 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

kaf24@xxxxxxxxxxxx changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED

------- Additional Comments From kaf24@xxxxxxxxxxxx  2005-05-05 22:15 -------
The packets must either be getting buffered in the kernel, or dropped. Before 
adding tracing to the 
kernel code it is probably worthwhile seeing if any of the stats in /proc can 
shed any light. For example, 
/proc/net/netstat has all kinds of useful counts (including packets dropped, 
and for what reason). You 
probably want to cook its output to one name,value pair per line, and you will 
need to cross-reference 
with the kernel sources to work out precisely what the counts mean.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>