My cards can't ping each other in ad hoc mode

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

shirie

29-10-2008 12:40:04

Hello, all.
I am trying to make an ad hoc network with two mechines now.
My usb wireless cards are Edimax 7318Ug and Prolink WG2000/R, both use the rt73 driver.
The os is FC7.

I followed the steps metion in
http//forums.fedoraforum.org/showthread.php?t=159740
to install the driver.

Now the situation is
after the os boots, the command "lsmod" lists
Module Size Used by
i915 25793 2
drm 78037 3 i915
autofs4 24645 2
hidp 26433 2
rfcomm 43481 0
l2cap 30145 10 hidp,rfcomm
bluetooth 57125 5 hidp,rfcomm,l2cap
sunrpc 159133 1
cpufreq_ondemand 11981 1
acpi_cpufreq 14281 1
dm_mirror 24405 0
dm_multipath 21705 0
dm_mod 57485 2 dm_mirror,dm_multipath
video 21065 0
sbs 19173 0
i2c_ec 9281 1 sbs
button 12113 0
bay 10177 0
dock 13669 1 bay
battery 14149 0
ac 9413 0
ipv6 276673 22
lp 15977 0
loop 19785 0
ipw2100 69873 0
ieee80211 35081 1 ipw2100
rt73 195584 1
fw_ohci 19649 0
....

which says that the module rt73 is loaded and is used by another module, but not list which one.

I run the commands

iwconfig wlan0 essid "hoc"
iwconfig wlan0 mode ad-hoc
iwconfig

the result is

wlan0 RT73 WLAN ESSID"hoc"
ModeAd-Hoc Frequency=2.412 GHz Cell 9AFED1A9B9EE
Bit Rate=11 Mb/s
RTS throff Fragment throff
Encryption keyoff
Link Quality=63/100 Signal level-48 dBm Noise level-115 dBm
Rx invalid nwid0 Rx invalid crypt0 Rx invalid frag0
Tx excessive retries0 Invalid misc0 Missed beacon0

there is one thing to metion, after I changed the wireless card mode to "ad-hoc", some kernel messages are printed on the console

Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel Oops 0000 [#1]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel SMP
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel CPU 0
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel EIP 0060[<e056a656>] Not tainted VLI
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel EFLAGS 00010202 (2.6.21-1.3194.fc7 #1)
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel EIP is at MakeOutgoingFrame+0x3f/0x53 [rt73]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel eax ddc5ced8 ebx 00000020 ecx 00000002 edx 00000002
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel esi 00000064 edi c081d020 ebp c081d000 esp ddc5cea0
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel ds 007b es 007b fs 00d8 gs 0000 ss 0068
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel Process wlan0-Mlme (pid 1072, ti=ddc5c000 task=c14c7150 task.ti=ddc5c000)
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel Stack ddc5ced8 ddd40000 74730064 ddc5cf86 ddd405a8 e056e9ff c081d000 ddc5cf90
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel 00000018 ddc5cf64 00000008 ddc5cf7c 00000002 00000064 00000002 ddc5cf9e
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel 00000001 e0592be0 00000001 ddd4abbe 00000006 ddd4ab9e 00000001 e0590b06
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel Call Trace
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<e056e9ff>] PeerProbeReqAction+0x297/0x3e9 [rt73]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<e057597a>] RTUSBRxPacket+0xe6e/0xe8b [rt73]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<c041faf7>] __wake_up_locked+0x1f/0x21
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<e0565cf0>] StateMachinePerformAction+0x19/0x1c [rt73]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<e0569f95>] MlmeHandler+0xc8/0x114 [rt73]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<e056586d>] MlmeThread+0x69/0xac [rt73]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<e0565804>] MlmeThread+0x0/0xac [rt73]
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel [<c0405b3f>] kernel_thread_helper+0x7/0x10
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel =======================
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel Code 8b 34 24 8d 46 04 89 04 24 8b 16 83 fa ff 74 21 8d 46 08 89 d1 89 04 24 c1 e9 02 8b 76 04 8d 7c 1d 00 f3 a5 89 d1 83 e1 03 74 02 <f3> a4 01 d3 eb cf 8b 44 24 1c 89 18 89 d8 5a 5b 5e 5f 5d c3 55
Message from syslogd@ at Mon Oct 27 200016 2008 ...
localhost kernel EIP [<e056a656>] MakeOutgoingFrame+0x3f/0x53 [rt73] SSESP 0068ddc5cea0

I don't know the meaning.....(

command "ifconfig " shows

wlan0 Link encapEthernet HWaddr 00120E5838A7
inet addr192.168.1.10 Bcast192.168.1.255 Mask255.255.255.0
inet6 addr fe80212efffe5838a7/64 ScopeLink
UP BROADCAST RUNNING MULTICAST MTU1500 Metric1
RX packets91374 errors0 dropped0 overruns0 frame0
TX packets439 errors0 dropped0 overruns0 carrier0
collisions0 txqueuelen1000
RX bytes13969101 (13.3 MiB) TX bytes32112 (31.3 KiB)

both cards I use the same configuration except the ip-addr.
if I run "iwlist wlan0 scan"
sometimes both machines can see each other, sometimes not,
but whatever neither mechine can ping each other.
Can anyone help and give me some advice.
Thanks in advance.

Spy84464

29-10-2008 18:16:29

I remember establishing an ad-hoc network using the legacy drivers a while ago. I had to play a bit with iwconfig to make it work, like running several times "iwconfig wlan0 essid [i18ezh3m3]essid[/i18ezh3m3]", and scanning. I know this is very vague but this is all I can come up with at the moment.
If I remember well, the mac address of one of the station appears in "iwconfig" output (which otherwise displays garbage) when the link is established.
Oh yes, and make sure you set both sticks to the exact same channel, that was mandatory for me.

shirie

30-10-2008 06:36:28

I remember establishing an ad-hoc network using the legacy drivers a while ago. I had to play a bit with iwconfig to make it work, like running several times "iwconfig wlan0 essid [i1y01lakh]essid[/i1y01lakh]", and scanning. I know this is very vague but this is all I can come up with at the moment.
If I remember well, the mac address of one of the station appears in "iwconfig" output (which otherwise displays garbage) when the link is established.
Oh yes, and make sure you set both sticks to the exact same channel, that was mandatory for me.[/quote1y01lakh]


Thank you Spy for your reply.
There's one thing I have to metion
the output of the iwconfig is

wlan0 RT73 WLAN ESSID"hoc"
ModeAd-Hoc Frequency=2.412 GHz Cell 9AFED1A9B9EE
Bit Rate=11 Mb/s
RTS throff Fragment throff
Encryption keyoff
Link Quality=63/100 Signal level-48 dBm Noise level-115 dBm
Rx invalid nwid0 Rx invalid crypt0 Rx invalid frag0
Tx excessive retries0 Invalid misc0 Missed beacon0

There's no channel info about my card in mode ad-hoc.
But if in mode managed, there is.
I try to set the channel using " iwconfig wlan0 channel 1"
but again the iwconfig doesn't show the info about the channel.
What's the problem?

btw, I metioned the kernel messages printed on the console. I don't konw the meaning exactly.
Are they normal?
Thanks.

Spy84464

30-10-2008 18:22:25

It doesn't show the channel, but the frequency used, which is the same, so there is no problem here.
I can't help with the kernel messages, I'm not into driver development.

qjantnn

16-12-2008 13:35:55

Hi !

I also have the same problem when the rt73-device tries to connect to an existing AdHoc network.
When the rt73-device initiates the AdHoc network and then joining this network with another device it works fine.
My rt73 device is Edimax 7318USg with driver "Ralink RT73 802.11abg WLAN Driver 1.0.3.6 CVS 2008120103"

Has anybody been able to get rt73 to join an existing AdHoc network ?

Br /Jan Terje


[root@testpeer1 bin]# iwconfig wlan5
wlan5 RT73 WLAN ESSID"AdHocTest"
ModeAd-Hoc Frequency=2.442 GHz Cell CA55F1AB03D0
Bit Rate=11 Mb/s
RTS throff Fragment throff
Encryption keyoff
Link Quality=65/100 Signal level-70 dBm Noise level-115 dBm
Rx invalid nwid0 Rx invalid crypt0 Rx invalid frag0
Tx excessive retries0 Invalid misc0 Missed beacon0

[root@testpeer1 bin]# ifconfig wlan5
wlan5 Link encapEthernet HWaddr 001F1F08E803
inet addr169.254.1.1 Bcast169.254.255.255 Mask255.255.0.0
inet6 addr fe8021f1ffffe08e803/64 ScopeLink
UP BROADCAST RUNNING MULTICAST MTU1500 Metric1
RX packets5322733 errors0 dropped0 overruns0 frame0
TX packets641917 errors0 dropped22322 overruns0 carrier0
collisions0 txqueuelen1000
RX bytes703857095 (671.2 MiB) TX bytes54841936 (52.3 MiB)

Vern

16-12-2008 17:39:38

In my experience, the driver works fine in adhoc mode as long as there are two, and only two, machines on the same channel in range of each other.

This thing seems to have been developed initially to operate as a STA in infrastructure mode. As such, it can only talk properly with only one other machine, either an AP in infrastructure mode, or a single peer IBSS station. Additional peers, or an AP on the same channel, will cause confusion.

If anyone gets an oops using the latest CVS, however (see shirie's post), please compile and run with debug enabled, then attach a gzipped extract of /var/log/kern.log covering the relevant interval to a post here,

Thanks,