Default period is too fast for some ISPs

[bandtank]

I installed vaping and tried to run it using the standalone_dns example, but no results were returned by fping. Having never used either tool, I assumed vaping was the issue because sending a ping is such a benign command that I figured it must have been working. After coming across #22, I decided to check fping and, lo and behold, it was not working. My ISP does not allow ping requests with a 20 ms period and I confirmed that by configuring multiple groups of targets in my config file. Everything inside my LAN worked fine, but anything to the WAN was non-responsive. I changed the period to be 200 ms and it worked as expected.

I think setting the period to 20 ms without really mentioning it could be causing problems for other people as well. It either needs more attention drawn to it in the documentation or a higher default value to make it more compatible with various ISPs.

[marconett]

It's not just ISPs, some firewalls also protect against this amount of echo requests. See: http://dennisk.freeshell.org/cis240dl_ping_flood.mkd.html

+1 to up the default to something less spammy.

[ghost]

@bandtank hello, how did you change the period? (sorry for the mention!)
I was so confused why "fping -u -C10 -p20 -e 8.8.8.8 4.2.2.1 208.67.222.222" results only dashes
I thought there was a problem with my armbian, but then I changed "-p20" to "-p200" it worked!!

which config/file do I edit to change the period? I can change the count and interval from this guide https://vaping.readthedocs.io/en/latest/quickstart/ but no mention about period

sorry for hijacking an old thread

EDIT: AHH, NVM!!! I found it!!
I was testing the "standalone_dns" example, all I had to do was to add "period: 200" in the config.yml file!!
"YourFolder/vaping/examples/standalone_dns/config.yml" for my case

  - name: std_fping
    type: fping
    count: 10
    interval: 3s
    period: 200 << added this!
    output:
      - vodka

sorry if this was so obvious

[grizz]

All good, thanks! I think it's time to change the default as well, I've ran into that a few times too.

[bitclick]

merge #179 has no effect. the is an invisible special char that blocks vaping from reading the setting.

see 9f47d2e#commitcomment-145406618

this affects current release version
commit 8ebc19260540d442d7c1d85f66f301e361bc9f81 (HEAD -> main, tag: 1.5.4, origin/main, origin/HEAD)