Debian + WEP problem

aphex™

Hi,
I've set up Debian Sarge. I've got 3 wireless cards (one build in- 2 PCMCIA). I can get on the network when i disable WEP on the router, but not with WEP enabled.

I was wondering if anybody could share their network scripts so i can edit them and merge them with my own, specifically the parts where WEP keys are specified.

I use a string based WEP password. So i'm looking for somebody who does the same, but can change their password before sending it to me (if you dont wanna share your real password- change it- but keep the format the same!).

Would i be right in saying the file i need is /etc/network/interfaces ???

Thanks

tomk

Yep, /etc/network/interfaces is where you'll be going, but let's back up to the WEP string for a minute. I expect your router uses this for simplicity - mine does anyway. Debian, however, will require the hex codes that the string is translated into - these should be available in the router's config.

Here's mine, with the essential parameters changed:

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

auto eth0

mapping eth0
      script ifscheme-mapping

iface eth0-home inet dhcp
      wireless_mode managed
      wireless_essid your_essid_here
      wireless_ap auto
      wireless_keymode restricted
      wireless_key 8D53EE9AC67F215B (or whatever)
      wireless_defaultkey 1

iface eth0-away inet dhcp
      wireless_mode managed
      wireless_essid any
      wireless_ap auto
      wireless_keymode off

aphex™

Hey Tom,
that worked! I'm now on the net on my debian installation, brilliant.

What i find weird is- on fedora, Suse, & Debian i used graphical utils like kwifimonitor, Yast on suse and a command line progy (ndiswrapper instructions told me to use iwconfig, i think) to pass the WEP key in STRING form. None worked for me, ever, as far as i can remember. I had to switch off WEP on the router for a while there too :eek:

Anyways, thanks alot for your help there

tomk

I'm not sure how the string is encoded into hex, or if there's even a standard. Chances are your router was doing it one way, and yast etc another way.

Glad you're sorted anyway.