What does netdate want back from udp-37 server?
I'm trying to write a mainframe (MVS) timserver (udp-37 only). I test it with a Debian 2.0 cmd netdate udp mvs.ip.address, which sends a 1-byte 0x0A message. My server sends back a 32-bit unsigned number (# of seconds since 1900-01-01, per RFC868), but the Debian netdate command times out. 1. Why doesn't the netdate command send an empty datagram, per RFC868? 2. What exactly is netdate expecting back from udp port-37? 3. Why does RFC868 mention negative 32-bit values: -1,297,728,000 17 Nov 1858 GMT? I would appreciate any help (or where I might find the netdate source).
Re: What does netdate want back from udp-37 server?
Are you sure your server is replying with a correct destination port? The server needs to send a packet back to the same port which the client used. [EMAIL PROTECTED] wrote: I'm trying to write a mainframe (MVS) timserver (udp-37 only). I test it with a Debian 2.0 cmd netdate udp mvs.ip.address, which sends a 1-byte 0x0A message. My server sends back a 32-bit unsigned number (# of seconds since 1900-01-01, per RFC868), but the Debian netdate command times out. 1. Why doesn't the netdate command send an empty datagram, per RFC868? 2. What exactly is netdate expecting back from udp port-37? 3. Why does RFC868 mention negative 32-bit values: -1,297,728,000 17 Nov 1858 GMT? I would appreciate any help (or where I might find the netdate source). -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED]
RE: What does netdate want back from udp-37 server?
The server 'send' command references the incoming ip-port address, and completes successfully, but no, I'm not exactly sure that the datagram makes it back to the Debian box. Is there a simple way for me to verify that a datagram came back (i/o count or something)? -- From: Jens B. Jorgensen To: [EMAIL PROTECTED] Subject: Re: What does netdate want back from udp-37 server? Date: Friday, February 12, 1999 11:29AM Are you sure your server is replying with a correct destination port? The server needs to send a packet back to the same port which the client used. [EMAIL PROTECTED] wrote: I'm trying to write a mainframe (MVS) timserver (udp-37 only). I test it with a Debian 2.0 cmd netdate udp mvs.ip.address, which sends a 1-byte 0x0A message. My server sends back a 32-bit unsigned number (# of seconds since 1900-01-01, per RFC868), but the Debian netdate command times out. 1. Why doesn't the netdate command send an empty datagram, per RFC868? 2. What exactly is netdate expecting back from udp port-37? 3. Why does RFC868 mention negative 32-bit values: -1,297,728,000 17 Nov 1858 GMT? I would appreciate any help (or where I might find the netdate source). -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
