From: Aaron Wood <woody77@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] going back to the default multicast rate on wifi
Date: Tue, 11 Feb 2014 14:34:36 +0100 [thread overview]
Message-ID: <CALQXh-NpiAf+dnBSFM=gfddCP=XxeHJFTFPJ2stb8GKJvPeyMA@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-NrYsjNtm03HhDnDOM1soda8qyvm4S8X=OiU=f1U2owoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3189 bytes --]
>
> I'm getting 40MHz (MCS13 at the moment, often MCS15) on ch 36,
> country-code FR (but that was expected, right?)
>
I'm also able to get 40MHz operation ch 44.
Putting the radio onto channel 40, however, disabled it:
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): Configuration
file: /var/run/hostapd-phy1.conf
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): sw10:
interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): sw10:
interface state COUNTRY_UPDATE->HT_SCAN
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): Switch own
primary and secondary channel to get secondary channel with no Beacons from
other BSSes
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): HT40 channel
pair (44, -1) not allowed
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): Interface
initialization failed
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): sw10:
interface state HT_SCAN->DISABLED
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046):
hostapd_free_hapd_data: Interface sw10 wasn't started
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): cat: can't
open '/var/run/wifi-phy1.pid': No such file or directory
Tue Feb 11 12:22:11 2014 daemon.notice netifd: radio1 (1046): Command
failed: Invalid argument
which led to this when trying to switch to channel 48 from the broken 44
config (via luci)
Tue Feb 11 12:28:00 2014 daemon.warn hostapd: sw10: IEEE 802.11 Configured
channel (48) not found from the channel list of current mode (2) IEEE
802.11a
Tue Feb 11 12:28:00 2014 daemon.warn hostapd: sw10: IEEE 802.11 Hardware
does not support configured channel
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): Configuration
file: /var/run/hostapd-phy1.conf
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): sw10:
interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): sw10: IEEE
802.11 Configured channel (48) not found from the channel list of current
mode (2) IEEE 802.11a
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): sw10: IEEE
802.11 Hardware does not support configured channel
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): Could not
select hw_mode and channel. (-3)
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): sw10: Unable
to setup interface.
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360):
hostapd_free_hapd_data: Interface sw10 wasn't started
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): cat: can't
open '/var/run/wifi-phy1.pid': No such file or directory
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): Command
failed: Invalid argument
Tue Feb 11 12:28:00 2014 daemon.notice netifd: radio1 (3360): Device setup
failed: HOSTAPD_START_FAILED
Remembering that HT40+ and ch 48 weren't allowed, I tried to switch to
HT40-. And... now it's really borked up. The luci ui won't give me any
options other than client mode on 48 or auto. I'm going to attempt to fix
this up by hand.
btw, this is on 3.10.24-8. Are the -28 builds ok for non-Comcast use?
-Aaron
[-- Attachment #2: Type: text/html, Size: 4071 bytes --]
next prev parent reply other threads:[~2014-02-11 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 17:48 Dave Taht
2014-02-10 17:57 ` Daniel Ezell
2014-02-10 18:39 ` Sebastian Moeller
2014-02-10 20:18 ` Aaron Wood
2014-02-11 13:34 ` Aaron Wood [this message]
2014-02-11 13:54 ` Aaron Wood
2014-02-11 14:23 ` Fred Stratton
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='CALQXh-NpiAf+dnBSFM=gfddCP=XxeHJFTFPJ2stb8GKJvPeyMA@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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