From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Information to collect if wifi hangs
Date: Mon, 21 Apr 2014 18:33:55 -0400 [thread overview]
Message-ID: <E4A46209-15A7-47CD-A456-465112A63BF1@gmail.com> (raw)
The following information was culled from the cerowrt-devel mailing list from April 2014. I don't know if it's relevant for the current 3.10.36... versions, so please update this list and then I'll publish it to the wiki.
Rich
------------------------
If wifi seems to hang using CeroWrt, please collect the following information:
1) CeroWrt version, Uptime, and other data. Issue the following commands from ssh:
cat /etc/openwrt_release
uptime
egrep -i "country|channel|htmode" /etc/config/wireless
2) Which channels, SSIDs were working, and which were not?
- Was 2.4GHz working
- Was 5GHz working?
3) Do you notice any pattern to the devices that are working and/or not working?
- OSX
- Windows
- Linux/Unix
- Android
- iOS devices
4) Log file symptoms:
what's in syslog? (What is the path to the syslog file?)
what other log files might be interesting?
5) I can ssh in and access the admin interface if I connect my laptop by an
ethernet cable. But during the failure, I can't access the admin
interface or the internet over sw00. After resetting sw00 by admin
interface on se00, I can connect over the wireless again.
(https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-April/002701.html)
6) To be forewarned and fore-armed, Dave Täht said this:
> > > what I've been doing is mounting a usb stick, and just running continuously
> > > on the stick
> > > (https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-April/002671.html)
> > >
> > > tcpdump -s 128 -i ge00 -w ge00.cap &
> > > tcpdump -s 128 -i sw00 -w sw00.cap &
> >
> > 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.
7) What else should we check for?
next reply other threads:[~2014-04-21 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 22:33 Rich Brown [this message]
2014-04-22 8:10 ` Sebastian Moeller
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=E4A46209-15A7-47CD-A456-465112A63BF1@gmail.com \
--to=richb.hanover@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