[src/trunk]: src/share/man/man4 More explicitly point to MSS-clamping, after ...

[martin <martin%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/4869cbc25d46
branches:  trunk
changeset: 546013:4869cbc25d46
user:      martin <martin%NetBSD.org@localhost>
date:      Sat Apr 19 10:08:40 2003 +0000

description:
More explicitly point to MSS-clamping, after explaining why the ifmtu
sysctl may not be enough. Hopefully this avoids users stoping after the
"but this does not work for you" phrase and makes them read the next
paragraph too.

diffstat:

 share/man/man4/pppoe.4 |  6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diffs (20 lines):

diff -r 8428ad7c9fee -r 4869cbc25d46 share/man/man4/pppoe.4
--- a/share/man/man4/pppoe.4    Sat Apr 19 08:35:25 2003 +0000
+++ b/share/man/man4/pppoe.4    Sat Apr 19 10:08:40 2003 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: pppoe.4,v 1.19 2003/02/25 10:35:14 wiz Exp $
+.\"    $NetBSD: pppoe.4,v 1.20 2003/04/19 10:08:40 martin Exp $
 .\"
 .\" Copyright (c) 2002 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -121,7 +121,9 @@
 Unfortunately this sysctl does not fix the MSS advertised by hosts in
 the network behind a
 .Nm
-connected router.
+connected router. To fix this you need
+.Em MSS-clamping ,
+explained below.
 .Ss Setting up NAT with MSS-clamping
 Some systems behind misconfigured firewalls try to use
 Path-MTU-Discovery, while their firewall blocks all ICMP messages.