You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attached are two pcap files you can open in wireshark.
This issue seems to only affect one Danish ISP, however I think it is worth reporting to see if it can be fixed.
The built in busybox-ntpd does not work (see packet in sysntpd.pcap)
However, if I install ntpdate instead then ntp is able to update (using the same ntp server).
You can see difference in the packets by comparing the two pcap files.
My best bet is that the ISP is blocking specific data in NTPv4 Packets that busybox-ntp is sending.
The text was updated successfully, but these errors were encountered:
What makes the difference is likely the source port of the request, not the UDP payload. The busybox ntpd uses a random port, but ntpdate and the ntp.org ntpd use the port 123. This needs to be fixed in the ISP's firewall.
barhom:
Attached are two pcap files you can open in wireshark.
This issue seems to only affect one Danish ISP, however I think it is worth reporting to see if it can be fixed.
The built in busybox-ntpd does not work (see packet in sysntpd.pcap)
However, if I install ntpdate instead then ntp is able to update (using the same ntp server).
You can see difference in the packets by comparing the two pcap files.
My best bet is that the ISP is blocking specific data in NTPv4 Packets that busybox-ntp is sending.
The text was updated successfully, but these errors were encountered: