Bug in always_defrag

Tom Oehser (tom@toms.net)
Sun, 27 Dec 1998 10:23:20 -0500 (EST)


This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.

--8323328-1824826731-914748556=:674
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.3.95.981227101719.184Z@toms.net>

> I just emailed you, it's not a fragment level problem but a packet level
> 'backup' or 'bottleneck' and a protocol/program not designed to account
> for such bottlenecks.

No, this is not what is happening to me. It happens with all the pipes
empty and the systems idle, there are no timeouts or bottlenecks involved.

Setting:

*idle* systems
*idle* PPP (MTU/MRU 296)
*idle* eth0
always_defrag is turned on

Some systems completely fail to forward, and changing the PPP MTU/MRU to
1500 fixes it. To me, this means they are not defragmenting, and of
course the fragments can't masquerade. There is a bug in the
always_defrag.

-Tom

--8323328-1824826731-914748556=:674--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/