From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] word on wifi - tcp syn attempts rejected
Date: Sat, 22 Mar 2014 19:49:39 +0000 [thread overview]
Message-ID: <CAA93jw4u5YznJH0M67m5-1NdPHrj6FmmQELEX1bXwo4RM2hzFw@mail.gmail.com> (raw)
it appears that wifi is working fine. What may be going wrong for
jg is something related to lots of tcp syn attempts, particularly over
a he tunnel.
it takes a really long time (24 hours) for the problem to occur, once it occurs,
all syn attempts from a given interface (in jims case, 2.4ghz) never make it out
the router. things like dns traffic continue to work.
the only things looking at syns is the syn flood protection and (sigh)
conntrack,
I have disabled synflood protection on jims box and I guess I'll have
some results in 24 hrs.
If you get in a situation where dns works and attempts to use tcp
outside the net do not, please take a capture of the offending
interface.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2014-03-22 19:49 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=CAA93jw4u5YznJH0M67m5-1NdPHrj6FmmQELEX1bXwo4RM2hzFw@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