Date: Fri, 23 Jun 2000 10:25:33 +0300 From: Ruslan Ermilov <ru@sunbay.com> To: Brian Somers <brian@Awfulhak.org> Cc: net@FreeBSD.org Subject: Re: "frag-anyways" knob. Message-ID: <20000623102533.A44764@sunbay.com> In-Reply-To: <200006221925.UAA00485@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Thu, Jun 22, 2000 at 08:25:01PM %2B0100 References: <ru@sunbay.com> <200006221925.UAA00485@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 22, 2000 at 08:25:01PM +0100, Brian Somers wrote: > This looks good. > > In the PPPoE case, we need to be able to bring the program up and > down based on any new MTU values negotiated by ppp(8). > > This could be done if tcpmssd had a ``create a pidfile'' option, > where ppp.linkup could run ``tcpmssd -M IFMTU -P tcpmssd.INTERFACE.pid'' > and ppp.linkdown could run ``kill `cat tcpmssd.INTERFACE.pid`''. > > Ppp would also need to expand IFMTU in command_Expand() in command.c. > > Does this make sense ? The only alternative I see is to implement > this stuff in libalias and have tcpmssd use libalias. > Would it be enough if tcpmssd(8) could track interface MTU (kernel is capable of notifying user processes about MTU changes through a routing socket interface as of sys/net/if.c,v 1.83). usage: tcpmssd [-v] -p port [-i iface | -m mtu] So, if run as `tcpmssd -p 1234 -i tun0', it will peek the initial MTU value on startup and then will monitor routing socket for MTU changes. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000623102533.A44764>