MPD 3.13 PPTP server MTU problems & questions

Andy Gilligan andy at evo6.org
Thu Jul 17 10:31:41 PDT 2003


----- Original Message ----- 
From: "Yann Nottara" <yann.nottara at almonde.com>
To: <freebsd-net at 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



More information about the freebsd-net mailing list