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.

[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.