From owner-freebsd-current Wed Oct 24 2:34:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 7DA9437B401 for ; Wed, 24 Oct 2001 02:34:16 -0700 (PDT) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA25095; Wed, 24 Oct 2001 11:34:11 +0200 (MET DST) Date: Wed, 24 Oct 2001 11:34:11 +0200 (CEST) From: Harti Brandt To: archie@whistle.com Cc: current@freebsd.org Subject: NgSendMsg may return bad token number Message-ID: <20011024112901.X55663-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, NgSendMsg returns the bad token number if the debugging level is higher than 2. It should use the token number from the message structure instead of the global gMsgId, because that is changed by the ASCII messages sent in _NgDebugMsg. The following patch fixes the problem for NgSendMsg: Index: msg.c =================================================================== RCS file: /usr/ncvs/src/lib/libnetgraph/msg.c,v retrieving revision 1.5 diff -r1.5 msg.c 84c84 < return (gMsgId); --- > return (msg.header.token); The same problem exists obviously in NgSendMsgASCII, but I have no test case for this one and hence no fix. Regards, harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fhg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message