problem creating ad-hoc connection in rt61pci

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=5898

roozbeh

02-12-2009 08:45:22

I have problems creating ad-hoc connections with my Dlink_DWA 510 wireless card.
wicd, network manager, kdenetworkmanager, none of them can create an adhoc connection.
Also using iwconfig and ifconfig i find out that you have to run a sequence of them twice to make it work.
Also this only sequnce works.

[codedked44jf]
ifconfig wlan0 down
iwconfig wlan0 key off
iwconfig wlan0 mode ad-hoc
iwconfig wlan0 essid linmint
iwconfig wlan0 key restricted '1234'
ifconfig wlan0 192.168.100.1
ifconfig wlan0 up
[/codedked44jf]

for example this doesnt work
[codedked44jf]
...
ifconfig wlan0 down
iwconfig wlan0 essid linmint
iwconfig wlan0 mode ad-hoc
iwconfig wlan0 key restricted '1234'
...
[/codedked44jf]

And also you have to run it twice always to make it work.
i guess this is related to driver....

more info on my hardware

[codedked44jf]
> modinfo rt61pci
filename: /lib/modules/2.6.31-15-generic/kernel/drivers/net/wireless/rt2x00/rt61pci.ko
license: GPL
firmware: rt2661.bin
firmware: rt2561s.bin
firmware: rt2561.bin
description: Ralink RT61 PCI & PCMCIA Wireless LAN driver.
version: 2.3.0
author: http://rt2x00.serialmonkey.com
srcversion: 801A037A3E53BB7E7E9C627
alias: pci:v00001814d00000401sv*sd*bc*sc*i*
alias: pci:v00001814d00000302sv*sd*bc*sc*i*
alias: pci:v00001814d00000301sv*sd*bc*sc*i*
depends: rt2x00lib,rt2x00pci,eeprom_93cx6,crc-itu-t
vermagic: 2.6.31-15-generic SMP mod_unload modversions 586
parm: nohwcrypt:Disable hardware encryption. (bool)
[/codedked44jf]


[codedked44jf]
> dmesg | grep -i rt61pci
[ 11.356945] rt61pci 0000:02:0b.0: PCI INT A -> Link[APC4] -> GSI 19 (level, low) -> IRQ 19
[ 11.563658] Registered led device: rt61pci-phy0::radio
[ 11.563676] Registered led device: rt61pci-phy0::assoc
[ 23.837784] rt61pci 0000:02:0b.0: firmware: requesting rt2561.bin
[/codedked44jf]

[codedked44jf]
>lspci -vv
02:0b.0 Network controller: RaLink RT2561/RT61 rev B 802.11g
Subsystem: D-Link System Inc Device 3a71
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at eb020000 (32-bit, non-prefetchable) [size=32K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: rt61pci
Kernel modules: rt61pci
[/codedked44jf]

Any more information required?

a-slack

05-12-2009 04:58:26

Ad-hoc mode is working well for me with rt2500pci and rt73usb (and possibly it is working well with all rt2x00 modules).

[code1fanfeh2]ifconfig wlan0 down
iwconfig wlan0 key off
iwconfig wlan0 mode ad-hoc
iwconfig wlan0 essid linmint
iwconfig wlan0 key restricted '1234'
ifconfig wlan0 192.168.100.1
ifconfig wlan0 up[/code1fanfeh2][/quote1fanfeh2]
The WEP key length is wrong, the WEP keys length are (in ASCII) 5 characters in WEP of 64 bits and 13 characters in WEP of 128 bits and the key assignment is wrong, if you do it throught iwconfig you have to type something like this (in ASCII)

[list1fanfeh2][code1fanfeh2]# iwconfig wlan0 key s:"12345"[/code1fanfeh2]
or

[code1fanfeh2]# iwconfig wlan0 key s:"1234567890abc"[/code1fanfeh2][/listu1fanfeh2]
The same in HEXADECIMAL is something like this

[list1fanfeh2][code1fanfeh2]# iwconfig wlan0 key 31:32:33:34:35[/code1fanfeh2]
or

[code1fanfeh2]# iwconfig wlan0 key 31:32:33:34:35:36:37:38:39:30:61:62:63[/code1fanfeh2][/listu1fanfeh2]

The "restricted" parameter is not recommended unless you want to create a wireless network with WEP ( ( and Shared Key Authentication (SKA) cry cry cry cry

Regards.

roozbeh

05-12-2009 21:56:22

well it was my mistake.
my key was 123456789a.


anyway is running iwconfig two times and none of network managers working related to driver or other parts of system, i am asking this maybe nobody filed a bug yet with those developers.