It is not an error, just a warning and hcxpcapngtool is able to handle dump files with a faulty time stamp. But you should move latest hcxdumtool (6.3.2).
With release of 6.2.9 hcxdumptool use nanosecond timer resolution, to fix a timestamp related bug when capturing traffic.
With the release of 6.2.9 hcxpcapng followed and use nanosecond timestamps, too.
From now on it is mandatory that the version numbers of hcxdumtool and hcxpcapng tool matches.
Older pcapng files (recorded with hcxpcapngtool < 6.2.9) can't be fixed and you have to live with this warning.
Which version of hcxdumptool have you used to record the traffic?
Which version of hcxpcapngtool have you used to convert them to hc22000?
With release of 6.2.9 hcxdumptool use nanosecond timer resolution, to fix a timestamp related bug when capturing traffic.
With the release of 6.2.9 hcxpcapng followed and use nanosecond timestamps, too.
From now on it is mandatory that the version numbers of hcxdumtool and hcxpcapng tool matches.
Older pcapng files (recorded with hcxpcapngtool < 6.2.9) can't be fixed and you have to live with this warning.
Which version of hcxdumptool have you used to record the traffic?
Which version of hcxpcapngtool have you used to convert them to hc22000?