-
Notifications
You must be signed in to change notification settings - Fork 330
Default to zero hop advert when booting + STEALTH_MODE flag #1199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
|
This behavior has already been discussed (and the fact that bootlooping repeaters are an issue) Another change that should be included upon @ripplebiz decision ... |
|
tbh I would prefer for repeaters not to issue any adverts during |
|
This would fix the DDOS/advert situation, see issue #1091 |
|
Implements #1217 (comment) |
|
Why is local in minutes and flood in hours? |
|
This pull request updates the advertisement sending logic in the mesh examples to allow for both "flood" and "zero hop" advertisement modes. The changes introduce a new
floodparameter to thesendSelfAdvertisementmethod, making it possible to specify the advertisement type. The initial advertisement sent during setup in all examples is now a zero hop advertisement.The CLI command
"advert"continues to use flood advertisements for backward compatibility, as thefloodparameter is omitted (defaulting totrue).Adds a
STEALTH_MODEswitch to remove automatic node advertisement when booting andDISCOVER_REQprocessing.