[9fans] known working wifi cards

[9fans] known working wifi cards

[Stanley Lieber]

Reading into the record. Please update the list (or the wiki) if
you've verified any other working wifi cards. Please, firsthand
experience only.

-sl


PCI:

none known

PCI Express:

none known

MiniPCI:

Actiontec 800MIP (branded Lucent WaveLAN)

MiniPCI Express:

none known

PCMCIA:

Wavelan PC24E-H-FC

Re: [9fans] known working wifi cards

[Tristan]

> Reading into the record. Please update the list (or the wiki) if
> you've verified any other working wifi cards. Please, firsthand
> experience only.

USB: Marvell 88W8388 aka olpc (probably not what you're looking for)

enjoy,
tristan

-- 
All original matter is hereby placed immediately under the public domain.

[9fans] wifi interface

[Tristan]

> USB: Marvell 88W8388 aka olpc (probably not what you're looking for)

oh, and on that note:

said wireless driver is much nicer now (though far from perfect or
complete) and still in contrib/tristan/libertas.tgz.

the wavelan driver uses the ctl file in the connection (`{cat clone}/ctl)
to manage association and such (if i'm understanding correctly). i find
that fairly annoying to use and generally unintuitive.

i'm inclined to extend the ethernet interface an etherx/ctl file that
accepted commands along the lines of ssid, bssid, and channel to
configure the connection. did the wavelan driver not do this for a reason
beyond changing devether? any better ideas?

my guess is that the strongest argument against that is that wavelan does
it the other way and consistancy is important.

enjoy,
tristan

-- 
All original matter is hereby placed immediately under the public domain.

Re: [9fans] wifi interface

[erik quanstrom]

> i'm inclined to extend the ethernet interface an etherx/ctl file that
> accepted commands along the lines of ssid, bssid, and channel to
> configure the connection. did the wavelan driver not do this for a reason
> beyond changing devether? any better ideas?

there's already a ctl file.  it's in the connection directory.  we use
this to set the hardware mtu.  for example

	echo mtu 9000>/net/ether0/clone

i'm sure you can do this with your wireless commands as well.
you'll need to set ether->ctl to an appropriate function.

- erik

Re: [9fans] wifi interface

[Tristan]

> 	echo mtu 9000>/net/ether0/clone
interesting, i didn't realise clone had been overloaded like that, i just
knew about the ctl file in the connection directory.

that's plenty convenient, if a little strange.

> i'm sure you can do this with your wireless commands as well.
> you'll need to set ether->ctl to an appropriate function.
indeed, i had already.

thanks,
tristan

-- 
All original matter is hereby placed immediately under the public domain.

Re: [9fans] wifi interface

[erik quanstrom]

On Wed Mar 21 03:02:26 EDT 2012, 9p-st@imu.li wrote:
> > 	echo mtu 9000>/net/ether0/clone
> interesting, i didn't realise clone had been overloaded like that, i just
> knew about the ctl file in the connection directory.

it's not overloaded.  when you open the clone file, the fid gets changed
to be that of $nextconv/ctl.  since the operations tend to be one shot,
the idom is to "operate directly on the clone file".

- erik

Re: [9fans] known working wifi cards

[Richard Miller]

> PCMCIA:
>
> Wavelan PC24E-H-FC

  aka Avaya World Card Silver

Re: [9fans] known working wifi cards

[Stanley Lieber]

On Wed, Mar 21, 2012 at 10:42 AM, Richard Miller <9fans@hamnavoe.com> wrote:
>> PCMCIA:
>>
>> Wavelan PC24E-H-FC
>
>  aka Avaya World Card Silver

aka Lucent Orinoco Silver
aka IBM High Rate Wireless LAN
etc.

-sl

Re: [9fans] known working wifi cards

[Richard Miller]

> aka Lucent Orinoco Silver
> aka IBM High Rate Wireless LAN
> etc.

"Firsthand experience only" ?

Re: [9fans] known working wifi cards

[Stanley Lieber]

On Wed, Mar 21, 2012 at 11:02 AM, Richard Miller <9fans@hamnavoe.com> wrote:
>> aka Lucent Orinoco Silver
>> aka IBM High Rate Wireless LAN
>> etc.
>
> "Firsthand experience only" ?

Perhaps it's a faulty assumption that all PC24E-H-FC cards are created
equal. I've seen them branded many different ways.

-sl

Re: [9fans] known working wifi cards

[Jerome Ibanes]

I use a "Vonets USB WiFi Bridge vap11g" I found on ebay for less than
$10, I wrote a little driver to have it set its channel and ssid.
I didn't have any documentation, so I snooped the usb traffic bridged
to a windows instance running in virtualbox.


Jerome

On Wed, Mar 21, 2012 at 9:10 AM, Stanley Lieber
<stanley.lieber@gmail.com> wrote:
> On Wed, Mar 21, 2012 at 11:02 AM, Richard Miller <9fans@hamnavoe.com> wrote:
>>> aka Lucent Orinoco Silver
>>> aka IBM High Rate Wireless LAN
>>> etc.
>>
>> "Firsthand experience only" ?
>
> Perhaps it's a faulty assumption that all PC24E-H-FC cards are created
> equal. I've seen them branded many different ways.
>
> -sl
>

Re: [9fans] known working wifi cards

[Ethan Grammatikidis]

On Wed, 21 Mar 2012 13:08:04 -0700
Jerome Ibanes <jibanes@gmail.com> wrote:

> I use a "Vonets USB WiFi Bridge vap11g" I found on ebay for less than
> $10, I wrote a little driver to have it set its channel and ssid.
> I didn't have any documentation, so I snooped the usb traffic bridged
> to a windows instance running in virtualbox.

Nice! I've thought snooping could help with writing drivers since I
started using Linux, but Linux had drivers for all of my hardware back
then anyway and the ISA bus was just starting to go out of style. ;)
Anyway it's funny you should post this now. Just half an hour ago I was
thinking about patching a Linux driver module to record everything it
does and every command it receives; snooping with driver help.

Re: [9fans] known working wifi cards

[Gorka Guardiola]

> thinking about patching a Linux driver module to record everything it
> does and every command it receives; snooping with driver help.
>

Wireshark can snoop usb traffic. It is easy and gives you all the
information you
probably need.

There is also a similar thing for windows. Can't remember the name.

G.

Re: [9fans] known working wifi cards

[Skip Tavakkolian]

Wireshark is available for windows, osx and linux.

On Thu, Mar 22, 2012 at 8:44 AM, Gorka Guardiola <paurea@gmail.com> wrote:
>> thinking about patching a Linux driver module to record everything it
>> does and every command it receives; snooping with driver help.
>>
>
> Wireshark can snoop usb traffic. It is easy and gives you all the
> information you
> probably need.
>
> There is also a similar thing for windows. Can't remember the name.
>
> G.
>

Re: [9fans] known working wifi cards

[Balwinder S Dheeman]

On 03/22/2012 09:14 PM, Gorka Guardiola wrote:
>> thinking about patching a Linux driver module to record everything it
>> does and every command it receives; snooping with driver help.
>>
>
> Wireshark can snoop usb traffic. It is easy and gives you all the
> information you
> probably need.
>
> There is also a similar thing for windows. Can't remember the name.

Plz check http://sourceforge.net/projects/usbsnoop/

--
Balwinder S "bdheeman" Dheeman
(http://werc.homelinux.net/contact/)

Re: [9fans] known working wifi cards

[Balwinder S Dheeman]

On 03/22/2012 09:14 PM, Gorka Guardiola wrote:
>> thinking about patching a Linux driver module to record everything it
>> does and every command it receives; snooping with driver help.
>>
>
> Wireshark can snoop usb traffic. It is easy and gives you all the
> information you
> probably need.
>
> There is also a similar thing for windows. Can't remember the name.

see also http://usb-robot.sourceforge.net/

--
Balwinder S "bdheeman" Dheeman
(http://werc.homelinux.net/contact/)

Re: [9fans] known working wifi cards

[Ethan Grammatikidis]

On Thu, 22 Mar 2012 16:44:07 +0100
Gorka Guardiola <paurea@gmail.com> wrote:

> > thinking about patching a Linux driver module to record everything it
> > does and every command it receives; snooping with driver help.
> >
>
> Wireshark can snoop usb traffic. It is easy and gives you all the
> information you
> probably need.
>

Neat. I was thinking of the built-in wifi in laptops, myself.