From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 10:31:41 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EA3837B401 for ; Thu, 17 Jul 2003 10:31:41 -0700 (PDT) Received: from mx1.evo6.net (mx1.evo6.net [80.76.194.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 9BF1343F93 for ; Thu, 17 Jul 2003 10:31:39 -0700 (PDT) (envelope-from andy@evo6.org) Received: (qmail 78315 invoked from network); 17 Jul 2003 17:31:37 -0000 Received: from vx.wi.dhcp.evo6.net (HELO vx) (10.0.2.2) by mx1.evo6.net with SMTP; 17 Jul 2003 17:31:37 -0000 Message-ID: <000901c34c89$439bf270$0202000a@vx> From: "Andy Gilligan" To: References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org> <3F16D1AC.8070802@almonde.com> Date: Thu, 17 Jul 2003 18:31:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Status: No, hits=0.2 required=5.0 tests=QUOTED_EMAIL_TEXT,REFERENCES,UPPERCASE_25_50 version=2.55-evo6.net X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55-evo6.net (1.174.2.19-2003-05-19-exp) Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 17:31:41 -0000 ----- Original Message ----- From: "Yann Nottara" To: Sent: Thursday, July 17, 2003 5:41 PM Subject: Re: MPD 3.13 PPTP server MTU problems & questions > Zs you can see in the following real world example, ng0 (which IS up) > MTU stays at 1500 although it's configured to be at 1460 in the mpd.conf > configuration file : > > ng0: flags=8890 mtu 1500 > inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 This doesn't look UP to me :) > ng1: flags=8890 mtu 1500 > ng2: flags=8890 mtu 1500 > ng3: flags=8890 mtu 1500 > ... > > Any idea ? Whenever MPD receives a connection, and assigns that interface to a client, it will change the MTU and mark it as UP. At least, it does for me... Interface down, mpd running, no client connected: ng0: flags=8890 mtu 1500 inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 Client connects: ng0: flags=88d1 mtu 1396 inet 192.168.0.1 --> 192.168.0.2 netmask 0xffffffff inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 Regards, -Andy