Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [Cerowrt - Bug #437] bug in initializing wifi interfaces
Date: Sun, 15 Dec 2013 22:17:26 -0800	[thread overview]
Message-ID: <CAA93jw63xiOitwvxyjefHbTF+6WrrcH2hUi=vhS+dPnOyUh5vQ@mail.gmail.com> (raw)
In-Reply-To: <redmine.journal-1765.20131215221618@lists.bufferbloat.net>

---------- Forwarded message ----------
From:  <cerowrt@lists.bufferbloat.net>
Date: Sun, Dec 15, 2013 at 10:16 PM
Subject: [Cerowrt - Bug #437] bug in initializing wifi interfaces
To:



Issue #437 has been updated by David Taht.


Stephen walker rightly pointed out that netifd has taken over some of
the functionality
formerly in mac80211.sh. I just merged the code in cero with that, and
gave it a shot.

http://www.bufferbloat.net/attachments/download/189/mac80211.sh

It is looking good here. slam this file into your /lib/wifi and see
what happens?
----------------------------------------
Bug #437: bug in initializing wifi interfaces
https://www.bufferbloat.net/issues/437

Author: David Taht
Status: New
Priority: Normal
Assignee:
Category:
Target version:


Since about cerowrt 3.10.18 there has been a bug in initializing the
wifi interfaces.

It looks like a set of race conditions in netfd. On initial boot
(while competing with a jffss init,
it generally does better in bringing up more interfaces) but on the
second boot, it's anybody's guess as to what will come up.

(there is a similar problem in starting dnsmasq)

The problem persists in cerowrt 3.10.24-4 which is built from openwrt svn 39076


--
You have received this notification because you have either subscribed
to it, or are involved in it.
To change your notification preferences, please click here:
http://www.bufferbloat.net/my/account


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

      parent reply	other threads:[~2013-12-16  6:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-437.20131215150033@lists.bufferbloat.net>
2013-12-15 23:31 ` [Cerowrt-devel] Fwd: [Cerowrt - Bug #437] (New) " Dave Taht
     [not found] ` <redmine.journal-1765.20131215221618@lists.bufferbloat.net>
2013-12-16  6:17   ` Dave Taht [this message]

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='CAA93jw63xiOitwvxyjefHbTF+6WrrcH2hUi=vhS+dPnOyUh5vQ@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