On Thu, Feb 17, 2005 at 01:18:44PM +0100, Guus Sliepen wrote:
>
> That problem has been reported before, but that is a bug in the drivers.
> The drivers should accept ioctls in any order, but some don't. Also,
> there is not one order that works well with every broken driver. If the
> driver you u
On Thu, Feb 17, 2005 at 01:33:35PM +0100, Hadmut Danisch wrote:
> How does one convince the author of a windows driver (used
> with ndiswrapper) to modify it in order to work with Linux?
>
> How does one find the author of a windows wlan driver?
As the Debian maintainer of the wireless-tools pac
On Thu, Feb 17, 2005 at 12:29:04PM +0100, Hadmut Danisch wrote:
> > If you want to do this kind of stuff, I suggest you add a pre-up command
> > to /etc/network/interfaces, like this:
> >
> > iface eth0 inet dhcp
> > pre-up iwconfig $IFACE key `cat keyfile`
> >
> > I will not add functionali
On Thu, Feb 17, 2005 at 12:07:46PM +0100, Guus Sliepen wrote:
>
> If you want to do this kind of stuff, I suggest you add a pre-up command
> to /etc/network/interfaces, like this:
>
> iface eth0 inet dhcp
> pre-up iwconfig $IFACE key `cat keyfile`
>
> I will not add functionality in the if
tags 295581 + wontfix
thanks
On Wed, Feb 16, 2005 at 09:37:01PM +0100, Hadmut Danisch wrote:
> the if-pre-up script is great, but for setting WEP
> keys it requires them to be included in the interfaces
> file. Would be better to allow a wireless_* command which
> loads them from an external f
Package: wireless-tools
Version: 27-2
Severity: wishlist
Hi,
the if-pre-up script is great, but for setting WEP
keys it requires them to be included in the interfaces
file. Would be better to allow a wireless_* command which
loads them from an external file. That file could be kept
more secret
6 matches
Mail list logo
