Greg Black wrote:
| "Matthew Emmerton" wrote:
|
| | > | > I've had ppp -nat working just fine over a normal modem link,
| | > | > but it is not working at all well on my ADSL link to the same
| | > | > provider.
| | > | >
| | > | > To quantify "not working at all well", although I can ping and
| | > | > traceroute ok from the hosts on my LAN, HTTP and FTP traffic is
| | > | > so slow and bursty as to be useless. Clicking on a link with
| | > | > Netscape will see short bursts of data with long periods (of a
| | > | > minute or more) where it says "stalled".
| | > | >
| | > | > Clicking on <http://www.freebsd.org/gnome/newsflash.html> from
| | > | > my gateway host gets the page in an eye-blink, but on the NAT
| | > | > hosts, it will take 40 seconds to load the top banner and the
| | > | > "FreeBSD GNOME News Flash" heading, then another delay of 40 or
| | > | > so seconds before the rest of the page will be displayed. Even
| | > | > then, Netscape thinks it has stalled and keeps waiting for the
| | > | > last bit of data.
| | > | >
| | > | > With FTP, a small transfer (e.g., a directory listing of / on
| | > | > ftp.freebsd.org) will complete normally; but something slightly
| | > | > larger (e.g., a listing of /pub/FreeBSD on the same server),
| | > | > will produce:
| | > | >
| | > | > ftp> cd /pub/FreeBSD
| | > | > 250 CWD command successful.
| | > | > ftp> dir
| | > | > 200 PORT command successful.
| | > | > 150 Opening ASCII mode data connection for '/bin/ls'.
| | > | > ftp: netin: Connection reset by peer
| | > | > 226 Transfer complete.
| | > | > ftp> quit
| | > | > 421 Timeout (60 seconds): closing control connection.
| | > | >
| | > | > If I do the same things from the host that is connected to the
| | > | > modem(s), everything works fine, for both types of connections.
| | > | >
| | > | > I'm finding this very frustrating, and I'm wondering if there's
| | > | > something weird about PPPoE with the ADSL link that needs some
| | > | > special magic in order for things to work properly.
| | > | >
| | > | > If anybody can point me at the truth, I'd be most grateful.
| > | >
| | > | > Alternatively, if anybody can suggest steps I could take to
| | > | > identify the nature of the problem, that would also be most
| | > | > welcome.
| | > |
| | > | What version of FreeBSD are you using? The ppp included in early 4.x
| | > | distributions doesn't have the TCP MSS fixup code that is required to
| | > | make
| | > | things work properly with a PPPoE connection, and cause the kinds of
| | > | symptoms that you describe.
| | >
| | > The NAT box is running 4.2-RELEASE -- is that a problem?
| |
| | Yes. This problem was first fixed in 4.2-STABLE. There are two safe ways to
| | fix this:
| | - upgrade to a newer -RELEASE or -STABLE
| | - run the tcpmssd program (which is in the ports collection -
| | /usr/ports/net/tcpmssd)
|
| I'll try tcpmssd first -- I have some other systems in a similar
| situation that are running 4.1-RELEASE and can't be upgraded, so my
| solution needs to work for them too. Thanks for the information.
OK, I have setup tcpmssd on my 4.1-R and 4.2-R NAT boxes and it
seems to be doing the job, but I am seeing some worrying log
messages on one of the machines:
tcpmssd: write to divert socket failed: Message too long
There have been 26 of these over 10 hours during which 4 Mbytes
of data in 21k packets have been through the divert rule. Is
there a fix, or do I just ignore it in the hope that things will
sort themselves out?
Greg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
