ORBIT-USER: Where's the WiFi device on sb2?

[Einar Vollset]

Hey,

is there any way I can stop nodehandler from doing that? Essentially  
I'm looking for a way to run an experiment where various bits
gets set (such as the wifi card), then when it (inevitably) doesn't  
do what I want I'd like to be able to ssh into the nodes and try  
executing
the commands manually in the exact environment the script was running  
in..

Cheers,

Einar


On Jul 25, 2006, at 5:14 PM, Kishore Ramachandran wrote:

> Hi Einar:
>
> Nodehandler loads the driver at the beginning of an experiment and  
> unloads it at the end - thats why you don't see the wireless  
> interface AFTER the experiment.
>
> If you use node.net.w0 or node.net.w1, you should pick up the  
> wireless interface...if thats still not the case, can you please  
> send your script to the list?
>
> Thanks,
> Kishore
>
> ---------------------------------------------------------------------- 
> -----
> Kishore Ramachandran
> Graduate Assistant, WINLAB/ECE, Rutgers University.
> WWW  : http://www.winlab.rutgers.edu/~kishore
> ---------------------------------------------------------------------- 
> -----
>
> On Tue, 25 Jul 2006, Einar Vollset wrote:
>
>>
>>
>>
>> Hi,
>>
>> I've been trying to wrestle nodehandler to run my code and was  
>> making progress when I noticed that
>> my experiments were a little too successful; my code was picking  
>> the 1Gbps wired network device
>> instead of the wireless one :-)
>>
>> However, I appear unable to actually locate the device interface  
>> for the wireless card; I simply run
>> `nodehandler -t -k` - which should create me a device ath0, but  
>> when I ssh into the node after the
>> simulation I only see the two wired interfaces:
>>
>> node1-1:~# iwconfig
>> eth0      no wireless extensions.
>>
>> eth1      no wireless extensions.
>>
>> lo        no wireless extensions.
>>
>> It also doesn't like my suggestion to manually ifconfig the ath0  
>> device:
>>
>> node1-1:~# ifconfig ath0 up
>> ath0: ERROR while getting interface flags: No such device
>> node1-1:~#
>>
>>
>> Any thoughts?
>>
>> Cheers,
>>
>> Einar
>>