patrick
04-05-2007, 11:15 AM
This is a pretty fresh install of etch from the 3/17/07 installer. I followed the instructions from SourceForge rtl-wifi project to build the drivers as per instructions at SourceForge.
Everything seems to work OK up until I request an IP address with dhclient. The access point is a Linksys BEFW11S4. It doesn't seem to matter if WEP is on or off.
If I manually assign an IP address to wlan0, I can ping that assigned IP address from another computer on the network. If I then bring down the wired interface (eth0) to try to isolate the wireless (wlan0) interface so I can try to ping via wlan0, the network "becomes unreachable".
====
install sequence:
cd /usr/src/rtl-wifi/
insmod ieee80211/ieee80211_crypt-rtl.ko
insmod ieee80211/ieee80211_crypt_wep-rtl.ko
insmod ieee80211/ieee80211_crypt_tkip-rtl.ko
insmod ieee80211/ieee80211_crypt_ccmp-rtl.ko
insmod ieee80211/ieee80211-rtl.ko
insmod rtl818x-newstack/r8180.ko
ifconfig wlan0 up
dmesg displays:
Linux kernel driver for RTL8180 / RTL8185 based WLAN cards
Copyright (c) 2004-2005, Andrea Merello
rtl8180: Initializing module
rtl8180: Wireless extensions version 20
rtl8180: Initializing proc filesystem
rtl8180: Configuring chip resources
PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [C150] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:02:00.0 to 64
rtl8180: Memory mapped space @ 0x12000000
rtl8180: MAC controller is a RTL8180 (v. F)
rtl8180: This is a CARDBUS NIC
rtl8180: Reported EEPROM chip is a 93c56 (2Kbit)
rtl8180: Card MAC address is 00:13:10:21:09:d5
rtl8180: EEPROM version 102
rtl8180: RfParam: 4
rtl8180: WW:Card reports RF frontend by MAXIM.
rtl8180: WW:This driver has EXPERIMENTAL support for this chipset.
rtl8180: WW:use it with care and at your own risk and
rtl8180: WW:**PLEASE** REPORT SUCCESS/INSUCCESS TO andreamrl@tiscali.it
rtl8180: Energy threshold: a
rtl8180: PAPE from CONFIG2: 2
rtl8180: Antenna A is default antenna
rtl8180: Antenna diversity is enabled
rtl8180: Carrier sense 1
rtl8180: 40-bit WEP is NOT supported in hardware
rtl8180: 104-bit WEP is NOT supported in hardware
rtl8180: IRQ 11
rtl8180: Driver probe completed
rtl8180: Bringing up iface
rtl8180: Card successfully reset
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mike:/home/pat# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
wlan0 802.11b linked ESSID:"blah"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0C:41:AF:16:56
Bit Rate=11 Mb/s
Retry:on Fragment thr:off
Encryption key:blah-blah-blah Security mode:open
Power Management:off
Link Quality:96/100 Signal level:-38 dBm Noise level:-252 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Mike:/usr/src/rtl-wifi# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/wlan0/00:13:10:21:09:d5
Sending on LPF/wlan0/00:13:10:21:09:d5
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
=====
Could I get this far and still have a kernel that needs changes compiled in? Thanks for any suggestions!
[edit -- 4/9/07] I had heard good things about SimplyMEPIS ability to correctly identify all hardware, so I gave the latest 6.5 disk a spin. After several days without success I finally got the card to connect.
I booted up from the disk on my Compaq Armada e500 with only the WPC11v4 installed (no wired ethernet plugged in) then ran the commands
# iwconfig wlan0 essid <myessid>
# iwconfig wlan0 key <my64bitkeyinhex-tenbytes> open
# /etc/init.d/networking restart
[edit -- 4/19/07] the command I use to get the IP address assigned is
~# dhclient wlan0 -- NOT ~# /etc/init.d/networking restart
voila -- an IP address is attached to the wlan0 interface by the ap.
I'm marking this [SOLVED].
[end of edit]
Everything seems to work OK up until I request an IP address with dhclient. The access point is a Linksys BEFW11S4. It doesn't seem to matter if WEP is on or off.
If I manually assign an IP address to wlan0, I can ping that assigned IP address from another computer on the network. If I then bring down the wired interface (eth0) to try to isolate the wireless (wlan0) interface so I can try to ping via wlan0, the network "becomes unreachable".
====
install sequence:
cd /usr/src/rtl-wifi/
insmod ieee80211/ieee80211_crypt-rtl.ko
insmod ieee80211/ieee80211_crypt_wep-rtl.ko
insmod ieee80211/ieee80211_crypt_tkip-rtl.ko
insmod ieee80211/ieee80211_crypt_ccmp-rtl.ko
insmod ieee80211/ieee80211-rtl.ko
insmod rtl818x-newstack/r8180.ko
ifconfig wlan0 up
dmesg displays:
Linux kernel driver for RTL8180 / RTL8185 based WLAN cards
Copyright (c) 2004-2005, Andrea Merello
rtl8180: Initializing module
rtl8180: Wireless extensions version 20
rtl8180: Initializing proc filesystem
rtl8180: Configuring chip resources
PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [C150] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:02:00.0 to 64
rtl8180: Memory mapped space @ 0x12000000
rtl8180: MAC controller is a RTL8180 (v. F)
rtl8180: This is a CARDBUS NIC
rtl8180: Reported EEPROM chip is a 93c56 (2Kbit)
rtl8180: Card MAC address is 00:13:10:21:09:d5
rtl8180: EEPROM version 102
rtl8180: RfParam: 4
rtl8180: WW:Card reports RF frontend by MAXIM.
rtl8180: WW:This driver has EXPERIMENTAL support for this chipset.
rtl8180: WW:use it with care and at your own risk and
rtl8180: WW:**PLEASE** REPORT SUCCESS/INSUCCESS TO andreamrl@tiscali.it
rtl8180: Energy threshold: a
rtl8180: PAPE from CONFIG2: 2
rtl8180: Antenna A is default antenna
rtl8180: Antenna diversity is enabled
rtl8180: Carrier sense 1
rtl8180: 40-bit WEP is NOT supported in hardware
rtl8180: 104-bit WEP is NOT supported in hardware
rtl8180: IRQ 11
rtl8180: Driver probe completed
rtl8180: Bringing up iface
rtl8180: Card successfully reset
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mike:/home/pat# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
wlan0 802.11b linked ESSID:"blah"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0C:41:AF:16:56
Bit Rate=11 Mb/s
Retry:on Fragment thr:off
Encryption key:blah-blah-blah Security mode:open
Power Management:off
Link Quality:96/100 Signal level:-38 dBm Noise level:-252 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Mike:/usr/src/rtl-wifi# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/wlan0/00:13:10:21:09:d5
Sending on LPF/wlan0/00:13:10:21:09:d5
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
=====
Could I get this far and still have a kernel that needs changes compiled in? Thanks for any suggestions!
[edit -- 4/9/07] I had heard good things about SimplyMEPIS ability to correctly identify all hardware, so I gave the latest 6.5 disk a spin. After several days without success I finally got the card to connect.
I booted up from the disk on my Compaq Armada e500 with only the WPC11v4 installed (no wired ethernet plugged in) then ran the commands
# iwconfig wlan0 essid <myessid>
# iwconfig wlan0 key <my64bitkeyinhex-tenbytes> open
# /etc/init.d/networking restart
[edit -- 4/19/07] the command I use to get the IP address assigned is
~# dhclient wlan0 -- NOT ~# /etc/init.d/networking restart
voila -- an IP address is attached to the wlan0 interface by the ap.
I'm marking this [SOLVED].
[end of edit]