I've walked arround all the different drivers[most recent drivers](RAlink,Rt61,RT2500), and have only minor success running the hardware on debian etch. therefore several questions
The installation, as such seemed to work, I'm setting it up badly, or I'm missing something from the overall picture.
I'm trying for weeks to install a c54ri conceptronix linux driver (PCMCIA) tried RAlink Driver /Rt61 legacy / and failed a first time installing Rt2500
Now I did install the Rt2500 driver again following rt2500Wiki. Using apt-get install rt2500-sources
the end result does not work (or clearly I'm doing something wrong)
Installing -building the driver all seems to work I get the (a) driver up and running
but no usable -relyable connection.(WPA2)
Although I notice no error messages nor complaints and statistics (ifconfig/iwconfig) seem to be rather ok.
----------------------------------Problems : ------------------------------------
Problem 1) I used rmod to unload all drivers as cleanup from previous installs
But I see after rebuilding rt2500 the driver showing up as wlan0 not as eth1 as
described in the Wiki, for that reason I did not execute ifrename...
Wlan0 as name is fine for me as long as I'm not working with an old (non rt2500 driver)
Is there any way to check??? eliminating a doubth is advancing to.
Problem 2) My wifi device and Ethernet is in use
both devices are in the same networks
10.0.0.xxx mask 255.255.255.0
to avoid rooter problems I need to plug/unplug the network cards
not very nice but for me it worked so far:
I used both static IP and DHCP based on mac address
both resulting in the same IP, for simplicity & speed currently
all is static.
eth0 (hard wired) ip=10.0.0.204 (static) mac address &&
dchcp offer same Ip address
wlan0 (wifi) ip=10.0.0.214(static)
DHCP (if used .. same Ip offered)
I beleive the above is not a problem since I switch PCMCI cards for tests
but I beleive I needed to add this for clarity
Given I'm not wrong in the above, as far as seen from wlan0 driver messages
(ifconfig/iwconfig)the world is perfect and all should be working ???!!!!!
except it does not. I had once a situation where I could ping my router.
>># ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:80:5A:4D:B6:2C
inet addr:10.0.0.214 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::280:5aff:fe4d:b62c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14167 errors:0 dropped:0 overruns:0 frame:0
TX packets:842 errors:25 dropped:25 overruns:0 carrier:0
RX bytes:2394628 (2.2 MiB) TX bytes:0 (0.0 b)
all is marked as if I'm receiving and transmitting packets, the packages
seem theoretical since hardly any messages get through
or is this a problem at a higher level ?
>># iwconfig wlan0
wlan0 RT61 Wireless ESSID:"okperfect" Nickname:"toshibaTecra"
Mode:Managed Frequency:2.472 GHz Bit Rate=54 Mb/s
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level:-78 dBm Noise level:-79 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon
some times link Quality RX/TX is filled using same configuration
but I get no connection except for a Ping on IP address
No DNS no real connection ??? UDP not working ?
tecra:# iwpriv wlan0
wlan0 Available private ioctls :
set (8BE2) : set 1024 char & get 0
bbp (8BE3) : set 1024 char & get 1024 char
mac (8BE5) : set 1024 char & get 1024 char
stat (8BE9) : set 1024 char & get 1024 char
rfmontx (8BEA) : set 2 int & get 0
get_rfmontx (8BEB) : set 0 & get 1 int
get_site_survey (8BED) : set 1024 char & get 1024 char
get_RaAP_Cfg (8BEF) : set 1024 char & get 0
tecra:# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:80:5A:5B:20:79
Channel:13 (correct is my ap
Bit Rates:0 kb/s
Quality:0/100 Signal level:-77 dBm Noise level:-256 dBm
Cell 02 - Address: 00:80:5A:60:7C:6B
Channel:13 (secondary AP placed much further)
Bit Rates:44 Mb/s
Quality:0/100 Signal level:-37 dBm Noise level:-256 dBm
For your information, all my config files
I use I think pretty standard /etc/network/interfaces
loopback && Eth0 standard-static
#iface wlan0 inet dhcp wireless-essid okperfect wireless-key s:correct
iface wlan0 inet static
#iface wlan0 inet static address=10.0.0.214 netmask=255.255.255.0 dns=10.0.0.10$
pre-up iwconfig wlan0 mode managed
pre-up iwconfig wlan0 channel auto
pre-up iwconfig wlan0 nick toshibaTecra
#not supported pre-up iwconfig wlan0 power on
pre-up iwconfig wlan0 key s:correct
#pre-up ifconfig wlan0 up
pre-up iwconfig wlan0 essid <perfectok>
pre-up iwpriv wlan0 set AuthMode=WPA2PSK
pre-up iwpriv wlan0 set WPAPSK=the textual key (cut/pasted from working XPwifi on same ap)
pre-up iwpriv wlan0 set EncrypType=AES
#iface wlan0 inet dhcp
pre-up ifconfig wlan0 up
as far as I know the above should work ???!!!! comments
are there problems with order ???
are there problems setting essid in down state ??
I did the same in a script file, but results are not different
as I'm only using wlan0 and eth0 as network devices; do I need to do something extra to get the device used in my Debian system ????
I noticed older problems with the network manager ? do I need to adapt
nothing seems to get through using dcmpx X11 no broadcast answer even ..
i often use networking restart since I switch PCMCIA cards
somethimes a ping works UDP does not seem to work
as far as I realize i've no firewall up (minimum debian etch, since the machine is not very powerfull)
as bottom line nothing usable works after weeks of trying I feel a bit dissapointed
but please help me or give a hint to get this thing up and running
lets hope I'm just doing something wrong .....
First, you should make sure you do not have several driver loaded at the same time. Apparently, you need the rt61 driver, and nothing else. You can check by running "lsmod". The name of the interface is not a problem.
Your problem sounds like a configuration issue, try to use "post-up" stanza, the legacy drivers usually only work when configured while the interface is up.
You could also try, first, to configure the card manually until it works, before automatizing the process.
Please don't hijack threads with replies about different problems.
Your error comes from insmod itself and tells you the module is already loaded.