From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] 7000 traps a second (and dropping). Ipsec, anyone?
Date: Wed, 18 Apr 2012 23:32:58 -0700 [thread overview]
Message-ID: <CAA93jw6ko0ay0Lith_iXv1m-BJWuUw1mtiYm1ST-pOMC9UUjUg@mail.gmail.com> (raw)
http://huchra.bufferbloat.net/~cero1/3.3/3.3.2-6/
is out.
After a truly epic bug hunt...
http://www.bufferbloat.net/issues/360#note-79
ipv6 and ipv4 are performing comparably. (the major differences are
due to the firewall rules)
It looks like we tacked on another 20-30Mbit of peak performance for
ipv4 as well (I see it peak at 290Mbit now with no firewall rules, no
aqm)
which is currently bounded by the last remaining traps in the aqm
code, which we haven't found yet. I have high hopes we will find the
rest over the next week.
If there are any favors I can ask of the list, if there is anyone out
there that can run openvpn and/or strongswan on this release? OR: I
would like to be able to connect an openvpn and/or ipsec client
50-200ms away to make sure the aqm stuff doesn't mess with that too
much, too. (or vice versa)
as we A) fixed up that code and B) expect ipsec at the very least, to
be much faster. C) Or, crash.
I spent a little time fiddling with how to create a 4in6 tunnel
unencrypted and didn't get anywhere.
This is not quite good enough to make it someplace with 4in6
opkg update
opkg install kmod-ip6-tunnel
#!/bin/sh
DEST=2001:X.Y.Z
LOCAL=`ip -o addr show dev ge00 | grep 2001 | awk '{print $4}' | cut -f1 -d/`
#PREFIX=
ip -6 tunnel add ip6tnl1 mode ip4ip6 remote ${DEST} local ${LOCAL}
ip link set dev ip6tnl1 up
ip -6 route add dev ip6tnl1 metric 4
ip addr add 192.168.66.5/24 dev ip6tnl1
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
reply other threads:[~2012-04-19 6:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6ko0ay0Lith_iXv1m-BJWuUw1mtiYm1ST-pOMC9UUjUg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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