W dniu 2 kwietnia 2011 03:11 użytkownik Felix Fietkau n...@openwrt.org
napisał:
Should be fixed in r26395 (trunk), r26396 (backfire)
Indeed. Thanks, Felix!
Paweł
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
On 2011-04-03 7:15 PM, Gioacchino Mazzurco wrote:
Here is it
2011/4/2 Felix Fietkaun...@openwrt.org:
On 2011-04-02 10:57 PM, Gioacchino Mazzurco wrote:
i can confirm that adhoc is still not working in backfire r26417
here is my /etc/config/wireless
config 'wifi-device' 'radio0'
yes this fixed...
but why simply naming the wifi-iface section break things??
on madwifi devices I do the same thing and it work fine...
i have to open a issue on bug tracker ?
2011/4/3 Felix Fietkau n...@openwrt.org:
On 2011-04-03 7:15 PM, Gioacchino Mazzurco wrote:
Here is it
2011/4/2
On 2011-04-03 7:34 PM, Gioacchino Mazzurco wrote:
yes this fixed...
but why simply naming the wifi-iface section break things??
on madwifi devices I do the same thing and it work fine...
The problem is the name clash between the wifi-iface section and the
network section from
ok very thanks!
send me a nudge when it is ready ;)
2011/4/3 Felix Fietkau n...@openwrt.org:
On 2011-04-03 7:34 PM, Gioacchino Mazzurco wrote:
yes this fixed...
but why simply naming the wifi-iface section break things??
on madwifi devices I do the same thing and it work fine...
The
i can confirm that adhoc is still not working in backfire r26417
here is my /etc/config/wireless
config 'wifi-device' 'radio0'
option 'type' 'mac80211'
option 'macaddr' '00:15:6D:72:B8:84'
option 'channel' '8'
option 'disabled' '0'
config 'wifi-iface'
On 2011-04-02 10:57 PM, Gioacchino Mazzurco wrote:
i can confirm that adhoc is still not working in backfire r26417
here is my /etc/config/wireless
config 'wifi-device' 'radio0'
option 'type' 'mac80211'
option 'macaddr' '00:15:6D:72:B8:84'
option 'channel' '8'
2011/4/1 Felix Fietkau n...@openwrt.org:
On 2011-03-30 5:26 PM, Paweł Foremski wrote:
W dniu 30 marca 2011 15:05 użytkownik Felix Fietkaun...@openwrt.org
napisał:
On 2011-03-30 9:10 AM, Paweł Foremski wrote:
2011/3/28 Felix Fietkaun...@openwrt.org:
On 2011-03-28 1:40 PM, Paweł
2011/4/2 Larry Vaden va...@texoma.net
How besides downloading and running strings can one tell the rx
for the files at, e.g.,
http://downloads.openwrt.org/snapshots/trunk/ar71xx/?
packages/base-files will tell you.
On Fri, Apr 1, 2011 at 9:17 PM, Jan Willies j...@willies.info wrote:
2011/4/2 Larry Vaden va...@texoma.net
How besides downloading and running strings can one tell the rx
for the files at, e.g.,
http://downloads.openwrt.org/snapshots/trunk/ar71xx/?
packages/base-files will tell you.
2011/3/28 Felix Fietkau n...@openwrt.org:
On 2011-03-28 1:40 PM, Paweł Foremski wrote:
Last week ath9k updates broke adhoc. I'm running todays trunk on
RB433AH + RB52n. From
what I can see, beacons don't fly in adhoc. AP looks OK and
association is possible.
You're running AP and Ad-Hoc on
On 2011-03-30 9:10 AM, Paweł Foremski wrote:
2011/3/28 Felix Fietkaun...@openwrt.org:
On 2011-03-28 1:40 PM, Paweł Foremski wrote:
Last week ath9k updates broke adhoc. I'm running todays trunk on
RB433AH + RB52n. From
what I can see, beacons don't fly in adhoc. AP looks OK and
association
Hello.
Last week ath9k updates broke adhoc. I'm running todays trunk on
RB433AH + RB52n. From
what I can see, beacons don't fly in adhoc. AP looks OK and
association is possible.
Failed:
http://nbd.name/gitweb.cgi?p=openwrt.git;a=commit;h=ba10982e1d9735fab43b38dd6e4f267e9d89d8a9
On 2011-03-28 1:40 PM, Paweł Foremski wrote:
Hello.
Last week ath9k updates broke adhoc. I'm running todays trunk on
RB433AH + RB52n. From
what I can see, beacons don't fly in adhoc. AP looks OK and
association is possible.
You're running AP and Ad-Hoc on one interface?
- Felix
14 matches
Mail list logo
