-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/21/2012 07:46 PM, Zlatin Balevsky wrote: > Are these rate-limited in any way? Do they obey some general > rate-limiting policies together with other messages?
They're limited in that each node will only accept 5 simultaneous probes. For these purposes, probes with equal randomly assigned (in the current code; an adversary could do something different) UIDs are considered to be the same probe. I haven't added any rate limiting myself. If something at the NodeDispatcher level or below has rate limiting for all messages which pass through them then the probes would have it. In checking just now I didn't notice any, but I don't know. > Does fred have any metrics collection system that would allow us to > detect such flooding events? Perhaps I should add a metric like "probe requests accepted in the past hour"? All that occurs to me is logging MHProbe at debug, grepping the logs for "Accepting probe with uid ", counting the lines. > IMHO maximum HTL should be single-digits or you risk flooding. I don't follow. What do you mean? At each hop a probe either stays locally (if a candidate is not accepted) or is routed to another random node. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJPutsVAAoJECLJP19KqmFuf9cQAKPlMhqZ6iYPBORXaYQEAKak Dq8jM4IZVJTv6qpxwgGzEUre6j2SyHU8l6p0ga7EY/A5xLXT8mrc8ykuUWqUnb3d l9ZYqBp++BADrvbL+ETIXXzbD9RjR4uM+HWdVliC8INGoPHUOjZgLuQm7TFMLVI1 Gu4FulIoc1f+9VE+Gai+y+LulrXwplnOSwL8RaKijFJfyDPGCqTNK6JjUV1G7zsw OR7txfcoWv2S5qJkqCW2Kjgfnb9wfvOWZaLz++26OlxWdkQ24GxcBtpH3WEUM1WT HyIwRwEuk/TRsEOkf794LTxpHxtzmbhfkjsogng99u5RL8JfKYeP71Gdj12hiCwr dzO/4fAwsozZaVF7NGqkVGHDJamHfkEHksjv0y90dR5kDD5qi3X/54N3ZvrnlTxi n8DEZi78RlQxdZUngCdC6ZaEF38bJzP5wjqN1deyZ9Lthb1Rx2BfaS5UbTomcN5r EER70mH2Hf6tBxPnT60fZoHw74B02PtL7PrDk7Hpo0MzMWKliI8JEVO9iK9dUNCh bVyLQ9zlWpcJ9uziGsycg7bA4yNUvdWXA3hS2H2LG2x1n6OnQj0IEi+veKT5sJsg uD1yb3Pcxb6MRuRKaz0qPhUzsBpTlQfUot4ihdzQ9kTGy6M1/LIuNAjhezdNjp7M tHiGQsoVbNtr1lHD31Pb =r5oe -----END PGP SIGNATURE-----
