From owner-freebsd-net Thu Dec 7 11:39:36 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 11:39:34 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 8AE4637B401 for ; Thu, 7 Dec 2000 11:39:33 -0800 (PST) Received: (qmail 5012 invoked from network); 7 Dec 2000 19:39:29 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 7 Dec 2000 19:39:29 -0000 From: "Patrick Bihan-Faou" To: Subject: RE: Problem with PPP, tcpmssd and routing socket messages Date: Thu, 7 Dec 2000 14:39:56 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Patrick Bihan-Faou [mailto:patrick@netzuno.com] > > My workaround for now is to invalidate the MTU information if I > see any message on the routing socket that are related to the > interface I am monitoring. Then when I have to modify a packet, I > refetch the correct MTU at that point. > > This is just a workaround for the problem that the RTM_IFINFO is > never received, which looks like a bug to me. If you give me some > pointers as to where to look, I can spend some time on it. I am happy to report that this workaround works just fine. I'd be happy to trace the "lost RTM_IFINFO" message issue if somebody can provide me with a couple of starting points. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message