From: Ed W <lists@wildgooses.com>
To: Linux Networking Developer Mailing List <netdev@vger.kernel.org>
Subject: Modifying the exponential backoff on new connection SYN packets
Date: Tue, 09 Apr 2013 10:06:17 +0100 [thread overview]
Message-ID: <5163DA09.5070202@wildgooses.com> (raw)
Hi, I have an unusual situation in that I would like to cap the
retransmit frequency on the initial SYN packets at some fairly short
time interval, eg a max of 2-4 seconds, rather than the usual
exponentially increasing interval. I could use some help figuring out
the exact point in the kernel to make such a change please?
The situation is that I am building a firewall which will be used with
expensive satellite links (think $10-100/MB range). Some of the links
are dialup links which take 20-40 seconds to bring up, and then we have
PPP drop the link after 10 seconds of inactivity. However, with the
default exponential backoff on new connections we are generally
retransmitting with a 16sec or 32 sec interval by the time the dialup
link is connected, the timout for inactivity kicks in and drops the link
before the retransmit...
I believe the exponential backoff is intended to prevent amplification
attacks? In this particular case we are accounting for traffic per user
and the internet costs are extremely substantial, so I think it's not a
problem
Could someone please help figure out the appropriate place to tweak the
exponential backoff? Note this is not retransmit of in flight data, just
the backoff for the initial syn (which doesn't seem to be configurable
in user space?)
Note, we have an application proxy here, but I can't see a sensible way
to fake it in user space without a lot of extra coding - any suggestions?
Thanks
Ed W
next reply other threads:[~2013-04-09 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 9:06 Ed W [this message]
2013-04-09 13:48 ` Modifying the exponential backoff on new connection SYN packets Eric Dumazet
2013-04-09 15:12 ` Eric Dumazet
2013-04-09 15:52 ` Ed W
2013-04-09 16:03 ` Eric Dumazet
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=5163DA09.5070202@wildgooses.com \
--to=lists@wildgooses.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox