Find the answer to your Linux question:
Results 1 to 3 of 3
Hi, I can't seem to get my wireless network working on my ASUS laptop running Debian. It worked under windows ;-s and i've been trying for days to get it ...
  1. #1
    Just Joined!
    Join Date
    Feb 2005
    Posts
    4

    wireless problem Linux Debian 2.6.8-2-686

    Hi,

    I can't seem to get my wireless network working on my ASUS laptop running Debian.
    It worked under windows ;-s
    and i've been trying for days to get it working again... to no avail so far.

    So, any help is appreciated a lot. I don't know what you want / need to know in order to help me, so just ask me if you need to know more.

    ok, i'm running Debian Sarge:
    Linux 2.6.8-2-686 #1 Tue Aug 16 13:22:48 UTC 2005 i686 GNU/Linux

    My wireless card:
    0000:01:03.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05)

    the modules seem to be installed
    $ lsmod | grep ipw
    ipw2200 161000 0
    firmware_class 10176 1 ipw2200
    ieee80211 41156 1 ipw2200
    ieee80211_crypt 6056 3 ieee80211_crypt_wep,ipw2200,ieee80211

    iwlist finds my network:
    eth1 Scan completed :
    Cell 01 - Address: 00:13:F7:16:42:14
    ESSID:"mynetwork"
    Protocol:IEEE 802.11bg
    Mode:Master
    Channel:8
    Encryption key:on
    Bit Rates:54 Mb/s
    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
    Quality=86/100 Signal level=-43 dBm
    Extra: Last beacon: 11ms ago

    ok, there I go,
    my router accepts my laptop macaddress, uses wep encryption.
    then i give these commands to the shell:
    # iwconfig eth1 essid mynetwork enc on key s:mysecretwords
    # ifconfig eth1 up
    # dhclient eth1
    Internet Software Consortium DHCP Client 2.0pl5
    Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
    All rights reserved.

    Please contribute if you find this software useful.
    For info, please visit http://www.isc.org/dhcp-contrib.html

    sit0: unknown hardware address type 776
    eth2: unknown hardware address type 24
    Starting the Firestarter firewall: failed.
    sit0: unknown hardware address type 776
    eth2: unknown hardware address type 24
    Listening on LPF/eth1/00:15:00:4b:48:45
    Sending on LPF/eth1/00:15:00:4b:48:45
    Sending on Socket/fallback/fallback-net
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
    No DHCPOFFERS received.
    No working leases in persistent database.

    Starting the Firestarter firewall: failed.
    Sleeping.

    ------------------------------------------------------------------------------------------------

    So, it seems that it can find my wireless network, but it doesnt receive an ip address.
    Any help?

    Thank you so much.

  2. #2
    Linux User
    Join Date
    Feb 2006
    Posts
    484
    Hi

    I suggest you use ndiswrapper to get working your card.
    http://linux.softpedia.com/get/Syste...per-5040.shtml

    it is worked for me.
    and you must edit your /etc/network/interfaces file

  3. #3
    Linux Engineer Zelmo's Avatar
    Join Date
    Jan 2006
    Location
    Riverton, UT, USA
    Posts
    1,001
    I can tell you what has worked in my experience.

    Passing the essid to your iwconfig isn't necessary; it will take the essid from the AP when it connects.
    Putting 'enc on' in the iwconfig line is also unnecessary. I would presume that it's assumed to be on if you pass a WEP key.
    I've found that I can't connect to my home or school network unless I specify that the WEP key is of the 'open' persuasion. So the iwconfig line includes 'key open 123456789ABCD' (assuming a hexadecimal key).
    I've never tried an ASCII WEP key, so I don't know whether that would be troublesome. It could be that you're mistaking a passphrase for an ASCII key, and passphrase is not supported. If that's the case, try setting the key as a hexadecimal number.
    Stand up and be counted as a Linux user!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •