Il 10/01/2011 09:38, 欧阳鑫 ha scritto: > Thank you very much. I have done the experiment for long time, but always > meet some questions. > If the official mac80211modules do not support the rate and the retries > radiotap fields, the new Atheros wireless cards drived by ath9k cant't work > at Rate 1 and 2, does this have some relation with the > reason(mac80211modules do not support the rate and the retries radiotap > fields)? The attached script is actually using the ExtraEncap/Decal elements, while it looks like that the wireless interface you are using is working in adhoc mode. Roofnet runs over monitor interfaces. This could be one of the problems. > The attachment is my configuration file: gen_config_roofnet.pl. Can you help > me check up if there is some error?
Try to: 1) run the script over an interface operating in monitor mode (created using the iw command) 2) modify the script to use the radiotapencap/decap elements > Thank you very much! > > 2011/1/10 Roberto Riggio <[email protected]> > >> Il 09/01/2011 12:39, 欧阳鑫 ha scritto: >>> Hi everyone, >>> We are running experiments with Roofnet on PCs. I have downloaded >>> click-1.8.0, and configured, make, make install it successfully. Then >>> I run: "./gen_config_roofnet.pl --dev wlan0 | click -" on TWO PCs. The >>> problem is, we cannot ping each other on the 2 PCs. We do not have >>> the old Atheros wireless cards, but use the new Atheros wireless cards >>> (802.11n supported) drived by ath9k. I am not sure if this is ok. >> it should work. However as far as I remember the official mac80211 >> modules do not support the rate and the retries radiotap fields. I >> assume that in this case you are always transmitting at the base rate. >>> The srcr interface's HWaddr is >> Yes >>> On PC1, "./read_handler srcr/es.bcast_stats" shows >>> >>> 200 Read handler 'srcr/es.bcast_stats' OK >>> DATA 360 >>> 5.32.234.144 00-25-86-20-EA-90 seq 1294477713 period 30000 tau 300000 >> sent >>> 45 last_rx 10.843367 >>> 5.32.234.144 00-25-86-20-EA-90 [ 2 60 0 0 -1 -1 ] >>> 5.32.234.144 00-25-86-20-EA-90 [ 2 1500 0 0 -1 -1 ] >>> 5.32.234.144 00-25-86-20-EA-90 [ 4 1500 0 0 -1 -1 ] >>> 5.32.234.144 00-25-86-20-EA-90 [ 11 1500 100 100 0 0 ] >>> 5.32.234.144 00-25-86-20-EA-90 [ 22 1500 100 100 0 0 ] >> this is strange because it looks like you are transmitting and receiving >> probes at both 5.5 and 11 Mbps but not at the lower rates. >>> On PC2, "./read_handler srcr/es.bcast_stats": >>> >>> 200 Read handler 'srcr/es.bcast_stats' OK >>> DATA 352 >>> 5.167.1.211 00-25-86-A7-01-D3 seq 1294477686 period 30000 tau 300000 sent >> 36 >>> last_rx 3.115970 >>> 5.167.1.211 00-25-86-A7-01-D3 [ 2 60 0 100 0 0 ] >>> 5.167.1.211 00-25-86-A7-01-D3 [ 2 1500 0 100 0 0 ] >>> 5.167.1.211 00-25-86-A7-01-D3 [ 4 1500 0 100 0 0 ] >>> 5.167.1.211 00-25-86-A7-01-D3 [ 11 1500 100 100 0 0 ] >>> 5.167.1.211 00-25-86-A7-01-D3 [ 22 1500 85 100 0 0 ] >> this means that you are receiving probes for every rate but you >> are successfully transmitting only at the 5.5. and 11 rates >>> The questions are: >>> (1) Why as neighbors, PC1 and PC2 cannot ping each other? >> because you have no routes and you have no routes because >> the probes at the lowest rate (1 Mbps) are not transmitted >>> (2) srcr/lt.routes shows no data, Is this OK? >> no >>> (3) Each PC has 3 interfaces, srcr, rate and wlan0. Which one should >>> be used to do experiments (like COPE)? >> srcr >>> _______________________________________________ >>> click mailing list >>> [email protected] >>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click >> >> _______________________________________________ >> click mailing list >> [email protected] >> https://amsterdam.lcs.mit.edu/mailman/listinfo/click >> >> >> >> _______________________________________________ >> click mailing list >> [email protected] >> https://amsterdam.lcs.mit.edu/mailman/listinfo/click _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
