At 07:56 AM 6/25/2002 +0200, Udo Erdelhoff wrote:
>Yes, but the solution in PPP only allows you to lower the MSS to
>1452 so that the return packet is never bigger than 1492 bytes.
>However, if you need an even lower MSS, you are still stuck with
>tcpmssd. I need to lower my MSS to about 1410 to
Hi,
On Mon, Jun 24, 2002 at 03:59:39PM -0400, Mike Tancsa wrote:
> If I recall correctly, the tcpmssd
> daemon was to fix client connection issue behind the FreeBSD box, not
> directly from the FreeBSD box.
exactly. The daemon enforces an upper limit on the MSS of any packet
passing over the '
Hi,
Thanks for the suggestion. If I recall correctly, the tcpmssd
daemon was to fix client connection issue behind the FreeBSD box, not
directly from the FreeBSD box. The problems we are seeing are directly on
the FreeBSD box, but only with certain DSL concentrators. Also, I thought
Mike Tancsa wrote:
Re DSL ...
> (Note, I have tried various MTU and MRU settings.
> Thanks for any pointers.
Perhaps you need /usr/ports/net/tcpmssd
- TCP Maximum Segment Size option corrector
I recently got DSL with Deutsche Telekom, then read the very enjoyable
http://www.ru
ail and may
> >help you solve it.
> >
> >http://renaud.waldura.com/doc/freebsd/pppoe/
> >
> >
> >
> >
> >----- Original Message -----
> >From: "Tom Samplonius" <[EMAIL PROTECTED]>
> >To: "Mike Tancsa" <[EMAIL PROT
: "Tom Samplonius" <[EMAIL PROTECTED]>
>To: "Mike Tancsa" <[EMAIL PROTECTED]>
>Cc: <[EMAIL PROTECTED]>
>Sent: Tuesday, June 18, 2002 3:09 PM
>Subject: Re: tracking down strange MTU issues with PPPoE)
>
>
> >
> > Well, if you nee
gt;
>To: "Mike Tancsa" <[EMAIL PROTECTED]>
>Cc: <[EMAIL PROTECTED]>
>Sent: Tuesday, June 18, 2002 3:09 PM
>Subject: Re: tracking down strange MTU issues with PPPoE)
>
>
> >
> > Well, if you need to find the MTU, the ppp logs should tell you what the
&g
Actually, I spoke too soon. The host I was testing against was the wrong
one :( Its still broken with the
set mtu max 1452
statement.
---Mike
At 05:16 PM 6/18/2002 -0700, Tom Samplonius wrote:
> Possibly. There is a PPPoE session to the Redback (or ERX), then
>usually a L2TP sess
At 05:16 PM 6/18/2002 -0700, Tom Samplonius wrote:
> Possibly. There is a PPPoE session to the Redback (or ERX), then
>usually a L2TP session to the ISP. A PPPoE client connecting to the
>Redback (or ERX) should be told a valid MTU. PPP tunel to L2TP tunnel
>raises some interesting possibli
Possibly. There is a PPPoE session to the Redback (or ERX), then
usually a L2TP session to the ISP. A PPPoE client connecting to the
Redback (or ERX) should be told a valid MTU. PPP tunel to L2TP tunnel
raises some interesting possiblities. I wonder how much mucking about the
SMS does to t
Yes, that did it! Thanks very much! What is different about that, and me
setting it on the other end as part of the virt-template ?
---Mike
At 12:33 AM 6/19/2002 +0100, Brian Somers wrote:
>Perhaps adding
>
> set mtu max 1452
>
>will help ?
>
>On Tue, 18 Jun 2002 16:54:49 -0400, M
Hi,
In terms of the MTU, I can set that in my router as I am the ISP
:-) Not sure how it works with Telus on the west coast, but with Bell,
PPPoE is done between the client and the DSL concentrator. Then the session
is handed off to the ISP via an L2TP tunnel. I can control that par
Perhaps adding
set mtu max 1452
will help ?
On Tue, 18 Jun 2002 16:54:49 -0400, Mike Tancsa <[EMAIL PROTECTED]> wrote:
>
> The DSL whole supplier we use (Bell Canada) has been turfing their Redback
> SMSes and moving to an ERX from unisphere networks.
>
> With the Redback, all was great...
lt;[EMAIL PROTECTED]>
Sent: Tuesday, June 18, 2002 3:09 PM
Subject: Re: tracking down strange MTU issues with PPPoE)
>
> Well, if you need to find the MTU, the ppp logs should tell you what the
> remote end is telling you to use.
>
> Usually, if you are having a MTU problem,
Well, if you need to find the MTU, the ppp logs should tell you what the
remote end is telling you to use.
Usually, if you are having a MTU problem, it relates to fragmentation,
MTU detection and ICMP filters. FreeBSD uses MTU detection by default.
However, MTU detection requires that ICMP
Hi,
the mss fixup is enabled by default and is part of the stock PPP from what
I understand. Also, this was all working just great when the other end was
a redback. The problems only started when the telco moved the termination
to the ERX.
---Mike
At 04:34 PM 18/06/2002 -0500, Nick
On Tue, 18 Jun 2002, Mike Tancsa wrote:
>
> The DSL whole supplier we use (Bell Canada) has been turfing their
> Redback SMSes and moving to an ERX from unisphere networks.
There was, at one time, MTU problems with PPPoE. See the tcpmssd
port or other online documentation. I d
17 matches
Mail list logo
