Date: Thu, 17 Jul 2003 18:31:32 +0100 From: "Andy Gilligan" <andy@evo6.org> To: <freebsd-net@freebsd.org> Subject: Re: MPD 3.13 PPTP server MTU problems & questions Message-ID: <000901c34c89$439bf270$0202000a@vx> References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org> <3F16D1AC.8070802@almonde.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "Yann Nottara" <yann.nottara@almonde.com>
To: <freebsd-net@freebsd.org>
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<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
> inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7
This doesn't look UP to me :)
> ng1: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
> ng2: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
> ng3: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> 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<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7
Client connects:
ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000901c34c89$439bf270$0202000a>