> Send Madwifi-devel mailing list submissions to
>
madwifi-devel@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
https://lists.sourceforge.net/lists/listinfo/madwifi-devel
> or, via email, send a message with subject or body 'help' to
>
madwifi-devel-request@lists.sourceforge.net
>
> You can reach the person managing the list at
>
madwifi-devel-owner@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Madwifi-devel digest..."
>
>
> Today's Topics:
>
> 1. Issue with short retries (prateek gangwal)
> 2. Re: R: Re: Rate selection in monitor mode (David Fuste)
> 3. R: Re: R: Re: Rate selection in monitor mode
> (
roberto.riggio@create-net.org)
> 4. Enable WEP Software Encryption (y omar)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 18 Nov 2008 22:58:53 +0000
> From: prateek gangwal <gangwalprateek@hotmail.com>
> Subject: [Madwifi-devel] Issue with short retries
> To: <madwifi-devel@lists.sourceforge.net>
> Message-ID: <BLU102-W5678802B6F775625391C4C6120@phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
>
> I am working on rate adaptation. As per my understanding , in madwifi , the
> number of long retries indicates the number of lost data frames and the
> number of short retries indicates the number of lost RTS/CTS frames. But,
> madwifi gives wrong value of short retries. It is either 0 means no retries
> when RTS is successful or 10. I cannot see any intermediate values. Is it
> some bug in madwifi ???? I checked it with two different cards 1. Linksys
> and 2. D-Link, but I am getting the same kind of results.
>
>
>
> _________________________________________________________________
> Search for videos of Bollywood, Hollywood, Mollywood and every other wood,
> only on Live.com
>
http://www.live.com/?scope=video&form=MICOAL
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Wed, 19 Nov 2008 09:05:29 +0100
> From: David Fuste <dfuste@ac.upc.edu>
> Subject: Re: [Madwifi-devel] R: Re: Rate selection in monitor mode
> To: Roberto Riggio <roberto.riggio@create-net.org>
> Cc:
madwifi-devel@lists.sourceforge.net
> Message-ID: <4923C8C9.2040305@ac.upc.edu>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Roberto.
> Well, I think it is possible to implement rate control modifying the
> code of "ath_tx_startraw" in if_ath.c.
> In fact, there is one peace of code inside this call:
>
> if (ph->try1)
> {
> ath_hal_setupxtxdesc(sc->sc_ah, ds,
> dot11_to_ratecode(sc, rt, ph->rate1), ph->try1,
> /* series 1 */
> dot11_to_ratecode(sc, rt, ph->rate2), ph->try2,
> /* series 2 */
> dot11_to_ratecode(sc, rt, ph->rate3), ph->try3
> /* series 3 */
> );
> }
>
> which is for this purpose. The thing is that ph->try1is always 0 in
> monitor mode.
> But, what do you mean by implementing rate control in user space? do you
> mean via a command line? in this case, I think you are right.
>
> david
>
> Roberto Riggio wrote:it seems that it
> > Hi David,
> >
> > thanks for the feedback. Correct me if I'm wrong, but it seems to me
> > that there is no way to implement rate control in user space using the
> > monitor mode.
> >
> > R.
> >
> > ----- "David Fust?e" <dfuste@ac.upc.edu> ha scritto:
> >
> >
> >> Hi Roberto,
> >> in monitor mode the default retransmission algorithm is 11
> >> retransmissions at the same rate (I cannot remember which version of
> >> madwifi I use). So, if you specify a rate of 11 Mbps and you transmit
> >> a
> >> frame, if the frame is not acknowledged madwifi will send 11 times the
> >>
> >> frame. You can change the rate using the iwconfig command, and the
> >> number of retransmissions by modifying the source code of if_ath.c
> >>
> >> david
> >>
> >> Roberto Riggio wrote:
> >>
> >>> Hi,
> >>>
> >>> I'm using madwifi (0.9.4) in monitor mode with radiotap header.
> >>>
> >>> 802.11 frames are generated with the click router which also adds
> >>> the radiotap header.
> >>>
> >>> As far as I;ve understood from the madwifi chatroom if i do not
> >>> specify a rate in the descriptor a default rate is used
> >>>
> >> (6Mbps?!?!).
> >>
> >>> However it is not clear to me what is happen if i do specify a
> >>>
> >> rate,
> >>
> >>> as for example 11 Mbps, and the the first transmission fails. Is the
> >>>
> >>> frame dropped? Is it transmitted again using the rate control
> >>> algorithm?
> >>>
> >>> Thanks
> >>> R.
> >>>
> >>>
> >>>
> >>
> -------------------------------------------------------------------------
> >>
> >>> This SF.Net email is sponsored by the Moblin Your Move Developer's
> >>>
> >> challenge
> >>
> >>> Build the coolest Linux based applications with Moblin SDK & win
> >>>
> >> great prizes
> >>
> >>> Grand prize is a trip for two to an Open Source event anywhere in
> >>>
> >> the world
> >>
> >>>
http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >>> _______________________________________________
> >>> Madwifi-devel mailing list
> >>>
Madwifi-devel@lists.sourceforge.net
> >>>
https://lists.sourceforge.net/lists/listinfo/madwifi-devel
> >>>
> >>>
> >
> >
> >
>
> --
> ========================================================================
> 0 0 0 David Fust? i Vilella | Dept. of Comp. Architecture
> 0 0 0 Ph.D. Student | UPC-Campus Nord, D6-001
> 0 0 0 email:
dfuste@ac.upc.edu | C/ Jordi Girona, 1-3
> U P C phone: 0034 93 401 67 83 | 08034 Barcelona - SPAIN
> www:
http://personals.ac.upc.edu/dfuste/
> ========================================================================
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Wed, 19 Nov 2008 09:13:01 +0100 (CET)
> From:
roberto.riggio@create-net.org
> Subject: [Madwifi-devel] R: Re: R: Re: Rate selection in monitor mode
> To: David Fuste <dfuste@ac.upc.edu>
> Cc:
madwifi-devel@lists.sourceforge.net
> Message-ID: <20284171.439421227082381621.JavaMail.root@aurora>
> Content-Type: text/plain; charset=utf-8
>
> Hi,
>
> actually i was meaning something totally different. More precisely i wanted
> to know if it is possible to have the built-in rate adaptation in monitor
> mode.
>
> The funny thing is that you helped me discover a feature of the atheros
> descriptor
> that I didn't knew about. Basically in the the ath descriptors is possible
> to
> specify four different tx rate each with its own tx attempt. In my case I'm
> using
> click in userspace so I think that I can implement a rate control using the
> atheros
> radio headers.
>
> Bye
> R.
>
> ----- "David Fuste" <dfuste@ac.upc.edu> ha scritto:
>
> > Hi Roberto.
> > Well, I think it is possible to implement rate control modifying the
> > code of "ath_tx_startraw" in if_ath.c.
> > In fact, there is one peace of code inside this call:
> >
> > if (ph->try1)
> > {
> > ath_hal_setupxtxdesc(sc->sc_ah, ds,
> > dot11_to_ratecode(sc, rt, ph->rate1),
> > ph->try1,
> > /* series 1 */
> > dot11_to_ratecode(sc, rt, ph->rate2),
> > ph->try2,
> > /* series 2 */
> > dot11_to_ratecode(sc, rt, ph->rate3), ph->try3
> >
> > /* series 3 */
> > );
> > }
> >
> > which is for this purpose. The thing is that ph->try1is always 0 in
> > monitor mode.
> > But, what do you mean by implementing rate control in user space? do
> > you
> > mean via a command line? in this case, I think you are right.
> >
> > david
> >
> > Roberto Riggio wrote:it seems that it
> > > Hi David,
> > >
> > > thanks for the feedback. Correct me if I'm wrong, but it seems to
> > me
> > > that there is no way to implement rate control in user space using
> > the
> > > monitor mode.
> > >
> > > R.
> > >
> > > ----- "David Fust?e" <dfuste@ac.upc.edu> ha scritto:
> > >
> > >
> > >> Hi Roberto,
> > >> in monitor mode the default retransmission algorithm is 11
> > >> retransmissions at the same rate (I cannot remember which version
> > of
> > >> madwifi I use). So, if you specify a rate of 11 Mbps and you
> > transmit
> > >> a
> > >> frame, if the frame is not acknowledged madwifi will send 11 times
> > the
> > >>
> > >> frame. You can change the rate using the iwconfig command, and the
> >
> > >> number of retransmissions by modifying the source code of if_ath.c
> > >>
> > >> david
> > >>
> > >> Roberto Riggio wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> I'm using madwifi (0.9.4) in monitor mode with radiotap header.
> > >>>
> > >>> 802.11 frames are generated with the click router which also adds
> >
> > >>> the radiotap header.
> > >>>
> > >>> As far as I;ve understood from the madwifi chatroom if i do not
> > >>> specify a rate in the descriptor a default rate is used
> > >>>
> > >> (6Mbps?!?!).
> > >>
> > >>> However it is not clear to me what is happen if i do specify a
> > >>>
> > >> rate,
> > >>
> > >>> as for example 11 Mbps, and the the first transmission fails. Is
> > the
> > >>>
> > >>> frame dropped? Is it transmitted again using the rate control
> > >>> algorithm?
> > >>>
> > >>> Thanks
> > >>> R.
> > >>>
> > >>>
> > >>>
> > >>
> > -------------------------------------------------------------------------
> > >>
> > >>> This SF.Net email is sponsored by the Moblin Your Move
> > Developer's
> > >>>
> > >> challenge
> > >>
> > >>> Build the coolest Linux based applications with Moblin SDK & win
> > >>>
> > >> great prizes
> > >>
> > >>> Grand prize is a trip for two to an Open Source event anywhere in
> > >>>
> > >> the world
> > >>
> > >>>
http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > >>> _______________________________________________
> > >>> Madwifi-devel mailing list
> > >>>
Madwifi-devel@lists.sourceforge.net
> > >>>
https://lists.sourceforge.net/lists/listinfo/madwifi-devel
> > >>>
> > >>>
> > >
> > >
> > >
> >
> > --
> > ========================================================================
> > 0 0 0 David Fust? i Vilella | Dept. of Comp. Architecture
> > 0 0 0 Ph.D. Student | UPC-Campus Nord, D6-001
> > 0 0 0 email:
dfuste@ac.upc.edu | C/ Jordi Girona, 1-3
> > U P C phone: 0034 93 401 67 83 | 08034 Barcelona - SPAIN
> > www:
http://personals.ac.upc.edu/dfuste/
> > ========================================================================
>
>
> --
> --------------------------------------------------------
> Roberto Riggio, PhD
>
> CREATE-NET
> Via alla Cascata 56/C
> 38100 Trento (Italy)
>
> E-mail:
roberto.riggio@create-net.org
> HomePage:
http://disi.unitn.it/~riggio/ <http://disi.unitn.it/%7Eriggio/>
>
> Tel: +39.0461.40.84.00 (ext. 708)
> Fax: +39.0461.314.972
> --------------------------------------------------------
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 19 Nov 2008 01:25:56 -0800 (PST)
> From: y omar <y_omar_004@yahoo.com>
> Subject: [Madwifi-devel] Enable WEP Software Encryption
> To: madwifi devel <madwifi-devel@lists.sourceforge.net>
> Message-ID: <522438.40118.qm@web44809.mail.sp1.yahoo.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello,
>
> I'm working on a project that intends to modify the code of wep_encrypt()
> in ieee80211_crypto_wep.c. For right now, madwifi does all the encryption
> via hardware, and never calls this function. Anybody knows how to disable
> the hardware encryption?
>
> I'm also a newbie, I'm having some difficulties tracing back function
> calls. If anybody has a good suggestion to a debugging tool that enables me
> to trace function calls in the 80211 module would be great!
>
> Thank you,
> Yara
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
>
http://moblin-contest.org/redirect.php?banner_id=100&url=/
>
> ------------------------------
>
> _______________________________________________
> Madwifi-devel mailing list
>
Madwifi-devel@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/madwifi-devel
>
>
> End of Madwifi-devel Digest, Vol 30, Issue 9
> ********************************************
>