Back off default multicast limit just a little.

This commit is contained in:
Adam Ierymenko 2014-10-29 18:25:24 -07:00
parent 4923ab2945
commit 0e84eb3852
2 changed files with 3 additions and 3 deletions

View File

@ -250,9 +250,9 @@
#define ZT_MULTICAST_TRANSMIT_TIMEOUT 5000
/**
* Default maximum number of peers to address with a single multicast (if unspecified in network)
* Default maximum number of peers to address with a single multicast (if unspecified in network config)
*/
#define ZT_MULTICAST_DEFAULT_LIMIT 64
#define ZT_MULTICAST_DEFAULT_LIMIT 32
/**
* Delay between scans of the topology active peer DB for peers that need ping

View File

@ -27,7 +27,7 @@ That will do a unicast all-to-all test and report results. At first latencies mi
multicast <some node's 10-digit ZT address> * ffffffffffffffff 24 60
This will send a multicast packet to ff:ff:ff:ff:ff:ff (broadcast) and report back who receives it. You should see multicast propagation limited to 64 nodes, since this is the setting for multicast limit on the fake test network (and the default if not overridden in netconf). Multicast will show the same "warm up" behavior as unicast.
This will send a multicast packet to ff:ff:ff:ff:ff:ff (broadcast) and report back who receives it. You should see multicast propagation limited to 32 nodes, since this is the setting for multicast limit on the fake test network (and the default if not overridden in netconf). Multicast will show the same "warm up" behavior as unicast.
Typing just "." will execute the same testnet command again.