Connecting to WEP Encrypted WiFi

Jima jima at beer.tclug.org
Thu May 19 06:21:13 MDT 2005


On Fri, 6 May 2005, Nathan Cashion wrote:
> Error for wireless request "Set Mode" (8B06) :
>      SET failed on device eth0:1 ; Invalid argument.
> Error for wireless request "Set Frequency" (8B04) :
>      SET failed on device eth0:1 ; Operation not supported.
> Determining IP information for eth0:1...SIOCSIFFLAGS: Cannot assign  
> requested address
> SIOCSIFFLAGS: Cannot assign requested address
>   failed.
> 
> I've tried setting the "Mode" as Auto and Managed, neither of which  
> work.

 I see a couple problems.  First off, eth0:1 is an alias device for eth0; 
the point would be to add an IP address on to an already-configured eth0, 
not to create a profile independent of it.  I imagine that's why the Mode 
set failed.
 If you're using Managed mode, you don't need to (and shouldn't!) worry 
about the channel/frequency.  A feature of managed mode is that it allows 
you to roam between different APs with the same ESSID, on different 
channels (frequencies).  The access point dictates the channel.  (Ergo, 
"managed.")

> I have successfully connected to an open network using the regular  
> eth0 configuration that is created by default.
> I'm using a PowerBook G3 Pismo, 500MHz with 768MB RAM, and an AirPort  
> card (not the Extreme of course).
> 
> I hope the problem is clear.  Any ideas??

 This would seem to concur that eth0:1 won't work without a working eth0.

     Jima



More information about the yellowdog-newbie mailing list