From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 10:52:19 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 3CC5B37B401 for ; Thu, 17 Jul 2003 10:52:19 -0700 (PDT) Received: from bull.almonde.com (almonde.net2.nerim.net [62.212.111.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB3CE43FA3 for ; Thu, 17 Jul 2003 10:52:17 -0700 (PDT) (envelope-from yann.nottara@almonde.com) Received: from almonde.com (vulture.almonde.com [192.168.0.156]) by bull.almonde.com (8.12.6/8.12.6) with ESMTP id h6HHqDi7073110 for ; Thu, 17 Jul 2003 19:52:14 +0200 (CEST) (envelope-from yann.nottara@almonde.com) Message-ID: <3F16E28C.10105@almonde.com> Date: Thu, 17 Jul 2003 19:53:16 +0200 From: Yann Nottara Organization: Almonde User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: fr, en-us MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org> <3F16D1AC.8070802@almonde.com> <000901c34c89$439bf270$0202000a@vx> In-Reply-To: <000901c34c89$439bf270$0202000a@vx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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:52:19 -0000 Andy Gilligan wrote: > ----- Original Message ----- > From: "Yann Nottara" >>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 :) [...] > 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 Ok, my mistake on this one :) but now, what do you think of this ? ng0: flags=88d1 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 inet 192.168.0.10 --> 192.168.0.200 netmask 0xffffffff and here's the part from my mpd.conf that's related to this connection : pptp0: new -i ng0 pptp0 pptp0 set iface disable on-demand set iface enable proxy-arp set iface idle 3600 set bundle enable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1460 <----------------- ! set ipcp yes vjcomp set ipcp ranges 192.168.0.10/32 192.168.0.200/32 set ipcp dns 192.168.0.10 set ipcp nbns 192.168.0.10 So, where's the catch ? --Yann