[Tinyos-help] Snooping the forwarded packets-MultihopOscilloscope in TinyOS2.x ???
Hi Group, I am working on MultihopOscilloscope application(from Tinyos2.x/apps) which is edited to SNOOP the on going traffic in the network. I have setup a small network of three motes(1,2 and 3) and one Base Station( mote 0): Just imagine mote1-sends message -mote 0 mote2- sends message - mote 0 mote 3- sends message - mote2-forwards the same message-mote0 As each mote has ability to snoop their neighbor's traffic. Mote 1 can see the packet from mote 3 that it has sent message(Sender -Id=3) to mote 2. and mote1 can also sees that mote 2 is forwarding the same packet(Sender-id=3) to mote0 ( I am assuming that forwarded packets are not edited by forwarder id.) I am little confused here.As mote 1 sees two packets(with sender-id=3 and same contents) but unable to distinguish between the forwarded packet and the original packet. *Is anyway I can see who is forwarding the packets ? *(I want to see the forwarded packet with not only originator id but also forwarder id ) *Can forwarders edit the packets with their id along with packet originator id?? I guess the MultihopOscilloscope application doesn't has any 'code' to see who is forwarding packets.My understanding is that the CTPForwardingEngine will take care of those things. Am I right ?? * I am sorry for the long mail. Thanks and Regards, Mahesh B. Satharla, University of Memphis. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] VMplayer and TinyOS
Did you download XubunTOS virtual machine image ?? You can get it from here http://sing.stanford.edu/tinyos/dists/xubuntos-2.0-vm.tar.gz For more information on installation of Xubuntos using VMware player, follow this link http://sing.stanford.edu/klueska/installing_xubuntos_vm.html Best, Mahesh. On Fri, Mar 28, 2008 at 8:44 PM, ST [EMAIL PROTECTED] wrote: Hello, I installed VM player and downloaded the vm. However, I get the following error: File not found xubuntos.2.0-s001.vmdk. This file is required to power on this VM. Please let me know what I should do. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] MultihopOscilloscope application with Snooping ???
Hi Everyone,
I setup a network of 4 motes( including basestation) running with
'MultihopOscilloscope' application from TinyOS 2.x.
// MultihopOscilloscope is a simple data-collection demo. It periodically
samples the default sensor and broadcasts a message every few readings //
I want to implement Snooping in this application, because neighboring nodes
needs to snoop
information transmitted to the base station.
According to my understanding, inorder to implement snooping I should use
AMSnoopingReceiveC/AMSnoopingC component instead of AMReceiveC and I need to
disable to address decoding in makefile by
CFLAGS += -DCC2420_NO_ADDRESS_RECOGNITION
When I see this code in MultihopOscilloscope application
// Overhearing other traffic in the network.
//
event message_t*
Snoop.receive(message_t* msg, void* payload, uint8_t len) {
oscilloscope_t *omsg = payload;
///
Is this code mean the Snooping already implemented in this application.??
If so, I didnt find any wiring to AMSnooperC component in configuration
file.
I guess Snoop.receive is called by the nodes which are forwarding messages
to base station.
Will it create any problems if I use AMSnooperC component for 'Receive'
interface.?
Thanks in Advance,
Mahesh Satharla.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Snooping in TinyOS 1.x ??
Hi all, I am able to work it out both in TinyOS 1.x (1.1.15) and TinyOS 2.02 * Snooping in TinyOS 1.x :* As Dr.Omprakash said, we need to use *GenericCommPromiscuous* instead of GenericComm.Not only that, we need call *CommControl.setPromiscuous(TRUE)*to enable the snooping mode.Last but not least, we need to diable ACK's by calling * MacControl.disableAck();* I borrowed this idea from this source: http://sensorweb.vancouver.wsu.edu/wiki/index.php/Cs455 see section 3.3 Lot of Thanks to them ! *Snooping in TinyOS 2.x (2.0.2) :* Snooping made easier in TOS 2.0.2 than TOS 2.0.0/1 I got ideas from this mail... http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-August/027152.html For snooping to work I edited BlinkToRadio application (TOS2.x /apps/tutorials/BlinkToRadio). # 1: In this application I added these two lines in 'Makefile' CFLAGS += -DCC2420_NO_ACKNOWLEDGEMENTS CFLAGS += -DCC2420_NO_ADDRESS_RECOGNITION ( these two lines are in 'Makefile' of Basestation application) # 2: I used AMSnoopingReceiverC instead AMReceiverC for 'Receive' interface *** I used TelosB motes from Crossbow. Hope I am doing correctly.If not please let me know or is there any thing to do snooping in a better way ! Best, Mahesh Satharla. On Feb 16, 2008 12:24 AM, Omprakash Gnawali [EMAIL PROTECTED] wrote: On Feb 15, 2008 10:18 PM, Mahesh Satharla [EMAIL PROTECTED] wrote: Dear Omprakash, Thanks for your early reply. Sir, I dont have much idea about BaseStation( coz I haven't upgraded to TinyOS 2.02) but I understood that, it replaces TOSbase of TinyOS1.x. Then how about TOSbase, I have seen the code but not able to understand clearly and how far it implements the Snooping mechanism I am looking for. ??? I am working on a scenario where in few motes are deployed and running on Delta application. // The Delta application is an example of a multihop data collection system. By installing Delta on Moteiv's motes, the devices will sample their internal temperature sensor and report readings to base station using a Multihop/Mesh topology // the scenario is like , Mote A sends message to Mote B which in turn forwards the message to Base Station , but Mote D should snoop the A's message.( As it is broadcast medium, surely Mote D receives the message from A , but D eventually drops the packet as it is not destined to it. Before dropping the packet, D needs to snoop the packet and see the senderID of the packet .) This is the Snooping mechanism I want to Implement. You want to understand and use GenericCommPromiscuous in TinyOS 1.x. It will be helpful for you to also study GenericComm and understand how it is different from GenericCommPromiscuous. I do not know what the corresponding component in Boomerang is called if you are using Boomerang. - om_p ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Snooping in TinyOS 1.x ??
Hello Everyone,
I am trying to implement Snooping mechanism in TinyOS 1.x *i.e a
node should observe the packets(messages) which are not destined to it*.Using
Snooping,I need to observe the sender ID of the packet.I am using Multihop
routing application ('Delta' from MoteIV) for data collection and routing
purpose.
I guess Multihop routing protocol itself do Snooping for link
estimations(Snoop interface in Multihop component) but I am not able to
figure out how exactly it do.
There is some other Interface called Snoop *( tinyos1.x
/interfaces/Snoop.nc*),but I don't know whether these two Snoop interfaces
are same and don't know how to use this interface ?
So, can any one help me out to *implement Snooping mechanism in TinyOS 1.x*?
Platform : Windows XP/ Cygwin
Motes: TmoteInvent (from MoteIV )
P.S: Somebody said, for Snooping to work I need to upgrade to TinyOS 2.0.2 .
Is it necessary ??? ( I am more familiar with TOS 1.x than TOS 2.x) and how
can I do in TOS 2.0.2 ???
Thanks and Regards,
Mahesh B.Satharla,
University of Memphis.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Reducing Multiple Timers ??
I am a Research Assistant at WiSe MANet Labs in University of Memphis. I am currently working on one project, for which it requires a Sensor mote(Tmote Invent) should monitor all of its neighbors.So i am using Multiple Timers to do so.For Monitoring motes, If a Mote A have 5 neighbors it should maintain 5 timers and if any thing goes wrong or say Timer expired for particular Mote B and didn't received any message from that Mote B, then Mote A should send Message to Base Station regarding Mote B. If a mote have 10 or 20 Neighbors, maintaining 20 timers for monitoring is not feasible i guess. So, is any way i can reduce Multiple Timers ?? Did any work has been done in sensor networks for reducing Multiple Timers or Monitoring Neighbor Motes??? Can anyone Help me out.?? Thanks and Regards, Mahesh Satharla. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
