All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Bonnedahl <tomas@yes.nu>
To: lartc@vger.kernel.org
Subject: [LARTC] problem with fragmenting (mtu/mss)
Date: Wed, 13 Nov 2002 12:34:17 +0000	[thread overview]
Message-ID: <marc-lartc-103719094329057@msgid-missing> (raw)

i have a setup that looks like this

LAN <--> router <--> fw <--> internet

both the router and the fw is slackware with 2.4.5, the fw also has
ipsec tunnels using the freeswan software.

the problem is that the fw is continuously hanging when sending too large
packets through the tunnel, even a frame over 1400 bytes gets the fw to hang.
(which it shouldnt, 40 bytes overhead for the ip and tcp header, and perhaps 20
bytes for the ESP header).

i have run out of options now, that's way im interested to hear your ideas.

the different areas that i have tried to search for a solution for this problem is;
1. changing the mtu on the router to 1300 to send packets (fragmented with a small size) 
to the fw and let it encrypt them
2. using iptables on the router to set the mss on the syn packets travelling _from_ the 
ipsec network to our lan (making our clients think that it has to have that mss to send) to 
everything from 500 to 1440 on the router.

an interactive session is able to go through the tunnel since those packets are
relativly small (40-100 bytes / packet), but using ftp to upload from our lan is
impossible.

anyone has a clue what could cause this problem on the fw, i would feel "better" if
the packets just were not sent, or perhaps that the ipsec software crashed, but this..
wtf?

tomas bonnedahl
network administrator
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-11-13 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 12:34 Tomas Bonnedahl [this message]
2002-11-15 20:09 ` [LARTC] problem with fragmenting (mtu/mss) Vincent Jaussaud
2002-11-22 20:35 ` Tomas Bonnedahl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-103719094329057@msgid-missing \
    --to=tomas@yes.nu \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.