kbanks
05-27-2008, 08:38 AM
In the LinkQualityRanger.py script, why in the mcastRpc is the ttl = 2 and not 1? Does the rpc come back to the broadcasting node?
I think the use of TTL = 2 was unintentional. If you want to do a "one hop over the air" RPC call from Portal, you use TTL = 2 because getting from Portal to the "bridge" node counts as one hop.
When invoking RPC calls from SNAPpy (not Portal) scripts, TTL = 1 has the same "reach".
With a TTL >= 2, the original broadcasting node will see the "echo" of the original broadcast, however it simply ignores it (he can tell from the source address in the packet that it originated from him).
You cannot invoke functions on yourself via a broadcast RPC call, even with TTL > 1.
I think the use of TTL = 2 was unintentional. If you want to do a "one hop over the air" RPC call from Portal, you use TTL = 2 because getting from Portal to the "bridge" node counts as one hop.
When invoking RPC calls from SNAPpy (not Portal) scripts, TTL = 1 has the same "reach".
With a TTL >= 2, the original broadcasting node will see the "echo" of the original broadcast, however it simply ignores it (he can tell from the source address in the packet that it originated from him).
You cannot invoke functions on yourself via a broadcast RPC call, even with TTL > 1.