From owner-freebsd-net@FreeBSD.ORG Wed Jan 4 10:59:19 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9999106564A for ; Wed, 4 Jan 2012 10:59:19 +0000 (UTC) (envelope-from sodynet1@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 748688FC17 for ; Wed, 4 Jan 2012 10:59:19 +0000 (UTC) Received: by iadj38 with SMTP id j38so40783346iad.13 for ; Wed, 04 Jan 2012 02:59:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=W+/tvvsOyIG6L5lnxP1pNhvfqk4sR3Xo4ncSmDChhsc=; b=EqEwSOL3hfi0lvL5gpCg7xUnBr1j8hIDSZPU2C/evUmc61kES8bi6G0EY01hCQfzeg FrIQFyXtDC/JXWoNLoTIilqMZ5/8d4Hq7Ex8xsyTqgrqoTKln9sSFChBq1NBU2J71FOT QV+R5vwwkNwth6F6BjP9PIMJyS7kmQE05Evf0= MIME-Version: 1.0 Received: by 10.42.161.132 with SMTP id t4mr56941280icx.16.1325674758863; Wed, 04 Jan 2012 02:59:18 -0800 (PST) Received: by 10.231.41.206 with HTTP; Wed, 4 Jan 2012 02:59:18 -0800 (PST) Date: Wed, 4 Jan 2012 12:59:18 +0200 Message-ID: From: Sami Halabi To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: kernel: nd6_setmtu0: new link MTU on ng29 (1218) is too small for IPv6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 10:59:19 -0000 Hi, I'm using a FreeBSD8.2-R-p5 in conjunction with MPD5.5 port for creating pptp/l2tp tunnels. I'm using MPPC (Compression & Encryption), my current onfiguration i use only IPv4. I keep getting in the logs the following: Jan 3 19:15:21 mpd2 kernel: nd6_setmtu0: new link MTU on ng120 (1218) is too small for IPv6 Jan 3 20:00:40 mpd2 kernel: nd6_setmtu0: new link MTU on ng151 (1218) is too small for IPv6 Jan 3 20:09:27 mpd2 kernel: nd6_setmtu0: new link MTU on ng128 (1218) is too small for IPv6 Jan 3 20:30:13 mpd2 kernel: nd6_setmtu0: new link MTU on ng128 (1218) is too small for IPv6 Jan 3 20:34:33 mpd2 kernel: nd6_setmtu0: new link MTU on ng137 (1218) is too small for IPv6 Jan 3 21:06:46 mpd2 kernel: nd6_setmtu0: new link MTU on ng105 (1218) is too small for IPv6 Jan 3 21:42:48 mpd2 kernel: nd6_setmtu0: new link MTU on ng92 (1218) is too small for IPv6 Jan 3 22:12:49 mpd2 kernel: nd6_setmtu0: new link MTU on ng137 (1218) is too small for IPv6 Jan 3 23:21:50 mpd2 kernel: nd6_setmtu0: new link MTU on ng92 (1218) is too small for IPv6 Jan 4 00:00:36 mpd2 kernel: nd6_setmtu0: new link MTU on ng105 (1218) is too small for IPv6 Jan 4 00:34:48 mpd2 kernel: nd6_setmtu0: new link MTU on ng105 (1218) is too small for IPv6 Jan 4 07:47:37 mpd2 kernel: nd6_setmtu0: new link MTU on ng100 (1218) is too small for IPv6 Jan 4 08:31:55 mpd2 kernel: nd6_setmtu0: new link MTU on ng116 (1218) is too small for IPv6 Jan 4 09:16:21 mpd2 kernel: nd6_setmtu0: new link MTU on ng123 (1218) is too small for IPv6 Jan 4 12:55:32 mpd2 kernel: nd6_setmtu0: new link MTU on ng53 (1218) is too small for IPv6 although the NG tunnels don't negotiate IPv6. a close look to the MPD log i see that this happens for connections that set MRU/MTU 1400. I talked to MPD developer (Alexander Motin) and this isn't a MPD problem, rather than a kernel issue as the logs say. why this problem happens when no IPv6 is in work? I don't want to disable ipv6 completely since i have plans in using it in the near future. Any help appreciated, Thanks in advance, -- Sami Halabi Information Systems Engineer NMS Projects Expert