rtap mode.

[Michail Bletsas]

David Woodhouse <dwmw2 at infradead.org> wrote on 12/09/2007 11:11:50 PM:

> 
> On Sun, 2007-12-09 at 22:20 -0500, Michail Bletsas wrote:
> > The rtap interface wasn't supposed to do anything else but sniff...
> 
> That's fair enough (well, almost. Actually it would be useful to be able
> to inject packets).

I agree and its something that we are working on it. The goal is to have a 
"thin mac" firmware that will move all operations to the host.
Useful for things like a SoftAP or just plain experimentation with the 
radio.


> 
> However, I cannot use the _normal_ interfaces (eth0, msh0) while the
> rtap interface exists. The transmit and receive paths are both broken --
> and if I attempt to fix them, I think I crash the firmware. It doesn't
> seem to like me attempting to transmit while it's in rtap mode, and
> certainly doesn't seem to manage to scan or associate.
That is a bug and it wasn't always like that.


> 
> It would be nice to get that working -- although it isn't a high
> priority right now. But if we _can't_ get it working, then I return to
> my previous question: what's wrong with 'iwconfig eth1 mode monitor'?

Obviously if you have to choose between monitor and infra modes, it makes 
no sense to have to configure another interface instance.

M.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infradead.org/pipermail/libertas-dev/attachments/20071210/b0508c43/attachment-0001.html