On Mon, Dec 15, 2008 at 12:16 PM, Bob Copeland wrote:
> On Mon, Dec 15, 2008 at 11:12 AM, Stefanik Gábor
> wrote:
>> That is not the problem - aireplay-ng operates on a monitor interface
>> that is already up. Likely this patch somehow misses monitor
>> interfaces.
>
> Agreed, that is probably th
On Mon, Dec 15, 2008 at 11:12 AM, Stefanik Gábor
wrote:
> That is not the problem - aireplay-ng operates on a monitor interface
> that is already up. Likely this patch somehow misses monitor
> interfaces.
Agreed, that is probably the case. Reverting that hunk makes it come up
with the eeprom mac
On Mon, Dec 15, 2008 at 5:17 PM, Bob Copeland wrote:
> On Mon, 15 Dec 2008 16:47:48 +0100, Stefanik Gábor wrote
>> This patch regressed support for aireplay-ng's "fragmentation attack"
>> feature!
>
> Does reverting just the following hunk make it work again?
>
>> > --- a/drivers/net/wireless/ath
On Mon, 2008-12-15 at 17:12 +0100, Stefanik Gábor wrote:
> On Mon, Dec 15, 2008 at 5:04 PM, Dan Williams wrote:
> > On Mon, 2008-12-15 at 16:47 +0100, Stefanik Gábor wrote:
> >> This patch regressed support for aireplay-ng's "fragmentation attack"
> >> feature!
> >>
> >> Prior to the landing of t
On Mon, 2008-12-15 at 16:47 +0100, Stefanik Gábor wrote:
> This patch regressed support for aireplay-ng's "fragmentation attack" feature!
>
> Prior to the landing of this patch (as commit
> caeb36d73b23b52a0ea2a8368502ef8230fa67b3), applying the patch @
> http://patches.aircrack-ng.org/mac80211_2.
On Mon, 15 Dec 2008 16:47:48 +0100, Stefanik Gábor wrote
> This patch regressed support for aireplay-ng's "fragmentation attack" feature!
Does reverting just the following hunk make it work again?
> > --- a/drivers/net/wireless/ath5k/attach.c
> > +++ b/drivers/net/wireless/ath5k/attach.c
[...]
>
On Mon, Dec 15, 2008 at 5:04 PM, Dan Williams wrote:
> On Mon, 2008-12-15 at 16:47 +0100, Stefanik Gábor wrote:
>> This patch regressed support for aireplay-ng's "fragmentation attack"
>> feature!
>>
>> Prior to the landing of this patch (as commit
>> caeb36d73b23b52a0ea2a8368502ef8230fa67b3), ap
This patch regressed support for aireplay-ng's "fragmentation attack" feature!
Prior to the landing of this patch (as commit
caeb36d73b23b52a0ea2a8368502ef8230fa67b3), applying the patch @
http://patches.aircrack-ng.org/mac80211_2.6.28-rc4-wl_frag+ack_v2.patch
allowed aireplay-ng's fragmentation a
Bob Copeland wrote:
> On Fri, Nov 21, 2008 at 11:45:18PM +0200, Maxim Levitsky wrote:
>>> I double check that I use right kernel (install it again).
>> compiled kernel again, and installed it, same results.
>
> Can you confirm that the proper mac address shows up if you do ifconfig
> or macchanger
On Fri, Nov 21, 2008 at 11:45:18PM +0200, Maxim Levitsky wrote:
>> I double check that I use right kernel (install it again).
>
> compiled kernel again, and installed it, same results.
Can you confirm that the proper mac address shows up if you do ifconfig
or macchanger -s? I think it's just not
Maxim Levitsky wrote:
> Bob Copeland wrote:
>> On Fri, Nov 21, 2008 at 2:49 PM, Maxim Levitsky
>> <[EMAIL PROTECTED]> wrote:
>>> Bob Copeland wrote:
Hi Maxim,
Please try this patch. I didn't have a problem changing the mac
address
after it was set to something else. I d
Bob Copeland wrote:
> On Fri, Nov 21, 2008 at 2:49 PM, Maxim Levitsky <[EMAIL PROTECTED]> wrote:
>> Bob Copeland wrote:
>>> Hi Maxim,
>>>
>>> Please try this patch. I didn't have a problem changing the mac address
>>> after it was set to something else. I did kick it to re-associate with
>>> the
On Fri, Nov 21, 2008 at 2:49 PM, Maxim Levitsky <[EMAIL PROTECTED]> wrote:
> Bob Copeland wrote:
>> Hi Maxim,
>>
>> Please try this patch. I didn't have a problem changing the mac address
>> after it was set to something else. I did kick it to re-associate with
>> the AP, though.
>>
>
> Tested it
Bob Copeland wrote:
> Hi Maxim,
>
> Please try this patch. I didn't have a problem changing the mac address
> after it was set to something else. I did kick it to re-associate with
> the AP, though.
>
Tested it, this still doesn't work:
iwconfig wlan0 down
macchanger wlan0
iwconfig wlan0 up
With my Atheros AR2413 this patch works well.
Connects to the AP and works well in monitor mode with injection.
Before this was not possible
https://lists.ath5k.org/pipermail/ath5k-users/2008-June/81.html
Regards
___
ath5k-devel mailing list
ath5k-
On Tue, Nov 18, 2008 at 2:39 PM, Albert Gall <[EMAIL PROTECTED]> wrote:
> With my Atheros AR2413 this patch works well.
> Connects to the AP and works well in monitor mode with injection.
> Before this was not possible
> https://lists.ath5k.org/pipermail/ath5k-users/2008-June/81.html
Great, th
With my Atheros AR2413 this patch works well.
Connects to the AP and works well in monitor mode with injection.
Before this was not possible
https://lists.ath5k.org/pipermail/ath5k-users/2008-June/81.html
Regards
___
ath5k-devel mailing list
ath5k-d
Hi Maxim,
Please try this patch. I didn't have a problem changing the mac address
after it was set to something else. I did kick it to re-associate with
the AP, though.
Subject: [PATCH] ath5k: set mac address in add_interface
Configure the mac address in add_interface and clear it in
remove_
18 matches
Mail list logo
