Greetings...
According to this logic in openwisp2 for uptime chart,
DEFAULT_PING_CHECK_CONFIG = { 'count': { 'type':
'integer', 'default': 5, 'minimum': 2, # chosen to avoid slowing down the
queue 'maximum': 20, }, 'interval': { 'type': 'integer', 'default': 25,
'minimum': 10, # chosen to avoid slowing down the queue 'maximum': 1000, },
'bytes': {'type': 'integer', 'default': 56, 'minimum': 12, 'maximum':
65508}, 'timeout': { 'type': 'integer', 'default': 800, 'minimum': 5, #
arbitrary chosen to avoid slowing down the queue 'maximum': 1500, }, }
1. If I am not wrong, the uptime chart is nothing but a PING check chart
ryt. 2. If you see the above logic every 2.5 milliseconds ping is
happening from server to connected device (router) to check if the device
is pingable or not. 3. If it is correct then, Per minute 2400 times
ping will happen according to your logic *(Interval =25, Ping check per min
= 60000/interval) *.
If all the above mentioned points are correct means then the data on the
devices will be used for ping check, so it would consume more data from
device SIM. Because of that SIM data is closing very fast.
Is there any specific reason to ping every 2.5 millisecond? or else my
understanding is wrong. or what's the use of above PING check logic.
Thanks in advance for your valuable time and support to understand this
openwisp2.
[image: image.png]
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to openwisp+unsubscr...@googlegroups.com.
To view this discussion on the web, visit
https://groups.google.com/d/msgid/openwisp/CAG6AGHcPWkxOrvmg18cibN_8KoR9kgxyUeqMYosai_BZwGPVbA%40mail.gmail.com.
