Contact Details
k5ra@verizon.net
Enhancement Type
Graphical interface
What is your idea or what can be improved?
Our tunnel mesh island has suffered corruption recently from messages with bogus epoch times (in year 2431! ). These have propagated to every node on our mesh through the normal meshchatsync process. W have changed our mesh zone name three times to defeat this. They still exist on some nodes that we can access. We all run AREDN nodes running Mesh Chat api, and MeshChat_all running on attached R-Pi computers.
Recommend that the message sync process not pass any message whose epoch time is more that 2047 seconds (34.1 mins) or 1023 (17 mins) ahead of current real time.
Contact Details
k5ra@verizon.net
Enhancement Type
Graphical interface
What is your idea or what can be improved?
Our tunnel mesh island has suffered corruption recently from messages with bogus epoch times (in year 2431! ). These have propagated to every node on our mesh through the normal meshchatsync process. W have changed our mesh zone name three times to defeat this. They still exist on some nodes that we can access. We all run AREDN nodes running Mesh Chat api, and MeshChat_all running on attached R-Pi computers.
Recommend that the message sync process not pass any message whose epoch time is more that 2047 seconds (34.1 mins) or 1023 (17 mins) ahead of current real time.