Recently, we faced a lot of problems with BWCTL client related to the 123 port used to sync NTP.
Our edge router does not allow the communication incoming through low ports, such as 123 (NTP).
One workaround is to use NTP client with -u parameter.
This parameter forces NTP to use high-ports for incoming communications, escaping gateways restriction to low ports, such as 123.
For example, executing:
$ sudo ntpdate -u 200.237.196.134
Forces NTP to use destination-port=123 and source-port=5022 (some random high-port).
This issue is particularly important to be fixed for BWCTL clients that are behind network firewalls.
Recently, we faced a lot of problems with BWCTL client related to the 123 port used to sync NTP. Our edge router does not allow the communication incoming through low ports, such as 123 (NTP). One workaround is to use NTP client with -u parameter. This parameter forces NTP to use high-ports for incoming communications, escaping gateways restriction to low ports, such as 123.
For example, executing:
Forces NTP to use destination-port=123 and source-port=5022 (some random high-port).
This issue is particularly important to be fixed for BWCTL clients that are behind network firewalls.
Thank you for your good work and effort.