From: Dave Taht <dave.taht@gmail.com>
To: Neil Shepperd <nshepperd@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.34-4 dev build released
Date: Sat, 5 Apr 2014 09:02:57 -0700 [thread overview]
Message-ID: <CAA93jw5Z-rPwF0xaYu6MdVGgZa_KL1JhDTO300VgrjymsQocNA@mail.gmail.com> (raw)
In-Reply-To: <533FFBC7.2030201@gmail.com>
On Sat, Apr 5, 2014 at 5:49 AM, Neil Shepperd <nshepperd@gmail.com> wrote:
>> Sounds like you are going to stick with -4 for a bit?
>
> Actually, this is the first time I've tried cerowrt on a router. But
> yeah, I'll stick with the current version unless you come out with a new
> patch to try.
Thx. I am hoping this is the *last* priority 1 bug cerowrt has.
but_fixing_it_is_going_to_be_pita.
I_confess_to_"embedded_fatigue".
>> what I've been doing is mounting a usb stick, and just running continuously
>> on the stick
>>
>> tcpdump -s 128 -i ge00 -w ge00.cap &
>> tcpdump -s 128 -i sw00 -w sw00.cap &
>>
>> This definately hurts performance...
>>
>> And it's probably time to do a tcpdump on the connected device as well.
>>
>
> Update: I did this, and experienced the hang again. A first look at the
> tcpdump output on sw00 shows a sudden reduction in traffic at 20:40:54,
> so I assume that's probably the time of the event. After that, I see
> many DHCP and ARP requests arriving, but no responses leaving the interface.
It_would_be_nice_to_see_10sec_of_these_captures_before_and_after.
>
> In fact, I don't see anything leaving except, oddly, some DNS responses
> (which are indeed received by my laptop). I also see some EAPOL stuff on
> both the router and laptop at roughly the same time, so I guess that's
> getting through, but I don't know the direction.
>
> I think next time I'll try with -Pin/-Pout to separate incoming and
> outgoing packets properly...
Tis easier_to_sort_in_wireshark_against_one_capture,IMHO.
I_have_been_looking_for_failed_syn_attempts_and_retries_as_a_key_indicator
that_something_Bad_happened.
>> Hmm. OK, this brings back the device driver into the equation... I
>> WAS seeing dhcp and arp requests "getting through" from the captures,
>> and it seemed like arp in particular was getting through...
>
> So I guess this is only half right? What I see in syslog is dnsmasq
> saying it has sent a packet, but it doesn't make it onto the interface.
> Apart from DNS packets, so I don't know what to make of that.
It_is_possible_there_are_a_variety_of_failure_modes.
I_am_not_entirely_convinced_this_is_actually_a_wifi_specific_failure.
can_you_try_ssh_to_the_router_during_a_failure,and/or_accessing
the_web_admin_interface?and/or_trying_to
if_you_are_not_using_babel_disable_it.It_makes_a_lot_of_updates
to_the_routing_table.that_might_be_malfunctioning..
(I_really_need_a_keyboard_that_recovers_from_damp_weather.)
> Neil
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-04-05 16:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 1:17 Dave Taht
2014-04-03 1:48 ` Stephen Hemminger
2014-04-03 1:58 ` Dave Taht
2014-04-03 2:43 ` Dave Taht
2014-04-03 10:09 ` David Personette
2014-04-03 15:17 ` Jim Gettys
2014-04-03 18:20 ` Neil Shepperd
2014-04-03 22:36 ` Dave Taht
2014-04-03 22:51 ` Maxim Kharlamov
2014-04-03 22:54 ` Dave Taht
2014-04-03 22:56 ` Aaron Wood
2014-04-03 22:57 ` Aaron Wood
2014-04-03 22:58 ` Dave Taht
2014-04-03 23:01 ` Maxim Kharlamov
2014-04-04 1:26 ` David Personette
2014-04-04 7:04 ` Aaron Wood
2014-04-04 6:57 ` Toke Høiland-Jørgensen
2014-04-05 12:49 ` Neil Shepperd
2014-04-05 16:02 ` Dave Taht [this message]
2014-04-05 16:15 ` Dave Taht
2014-04-05 8:34 ` Török Edwin
2014-04-05 15:53 ` Dave Taht
2014-04-05 21:25 ` Török Edwin
2014-04-07 14:45 ` Toke Høiland-Jørgensen
2014-04-07 15:27 ` Török Edwin
2014-04-07 15:31 ` Toke Høiland-Jørgensen
2014-04-07 17:58 ` Dave Taht
2014-04-07 18:51 ` Török Edwin
2014-04-05 19:11 ` Jim Reisert AD1C
2014-04-05 19:26 ` Dave Taht
2014-04-06 0:15 ` Jim Reisert AD1C
2014-04-06 10:23 ` Robert Bradley
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=CAA93jw5Z-rPwF0xaYu6MdVGgZa_KL1JhDTO300VgrjymsQocNA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=nshepperd@gmail.com \
/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