Hi, about BaseStation, it uses Snoop Component and for that, it snoop all
packets, about the node ids, it shouldn't do it.
2013/1/3 Kumar, Vimal (ST-Student) vk...@mail.mst.edu
Hi,
I was testing DEFAULT_LOCAL_GROUP on TinyOS 2.1.2 for which I wrote a
simple application with two motes
On Fri, Jan 4, 2013 at 12:30 AM, antonio rosa
antoniorosarodrig...@gmail.com wrote:
Hi, about BaseStation, it uses Snoop Component and for that, it snoop all
packets, about the node ids, it shouldn't do it.
Snoop actually is intended to see all packets (its like a packet sniffer).
Are you
Hi,
first sorry for this misunderstanding,
I wanted to say that this phenomenon in the BaseStation is due to the Snoop
Component, but if the applications nodes does not use the Snoop Component,
it must be a filter Group ID. Once years ago, we had the same conversation
with this topic:
: antonio rosa [antoniorosarodrig...@gmail.com]
Sent: Friday, January 04, 2013 5:40 AM
To: Eric Decker
Cc: Kumar, Vimal (ST-Student); tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] Problem with DEFAULT_LOCAL_GROUP on TinyOS 2.1.2
Hi,
first sorry for this misunderstanding,
I wanted to say
Hi,
I was testing DEFAULT_LOCAL_GROUP on TinyOS 2.1.2 for which I wrote a simple
application with two motes bouncing a message back and forth. The motes
received each other's message when they had the same group ID but even when
they had different group IDs. I set the group IDs in the make
Sounds like a bug.
can you submit a bug report at
https://github.com/tinyos/tinyos-release/issues. You'll have to get a
github login if you don't already have one.
There is filtering code that is supposed to deal with that in the AM stack.
So either there is a problem in the documentation
