| Key: |
NET-172
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Bob Luse
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows and Linux
|
|
| Resolution Date: |
20/Feb/08 02:26 PM
|
|
NTP client when using UDP should not bind to port 123 on the local system. This renders the software unusable for the very common case where you also have an NTP server running on your system. It should send to port 123 on the server, but the client should not bind to the local port 123.
|
|
Description
|
NTP client when using UDP should not bind to port 123 on the local system. This renders the software unusable for the very common case where you also have an NTP server running on your system. It should send to port 123 on the server, but the client should not bind to the local port 123. |
Show » |
|
NTP client should not bind to the local port when using UDP
"To use the class,
merely open a local datagram socket with open
and call getTime to retrieve the time. Then call
close
to close the connection properly.
Successive calls to getTime are permitted
without re-establishing a connection. That is because UDP is a
connectionless protocol and the Network Time Protocol is stateless."
This is wrong.? There is no need to "establish a connection" at all since UDP is connectionless and NTP is stateless.? You do not need to set up a connection and then close it.? You only need to send the packets.? All this does is slow down the initial call and cause the client to completely fail when there is an NTP Server on the same system as the client since the server will already be bound to port 123..