[ntp:questions] Re: using ACTS modem time service

Giuseppe vizio at ien.it
Thu Nov 4 18:55:25 UTC 2004


I've downloaded the latest ntp-dev tarball (20041102) this morning and
I'm doing some tests on a PC (PIII - 550 MHz) with Linux (kernel
2.2.20).

/etc/ntp.conf is:
   driftfile /var/lib/ntp/ntp.drift
  
   statsdir /var/log/ntpstats/
   statistics loopstats peerstats clockstats
   filegen loopstats file loopstats type day enable
   filegen peerstats file peerstats type day enable
   filegen clockstats file clockstats type day enable
  
   server 127.127.18.1 prefer
   phone ATDT263


If I start the ntpd daemon, I see an abnormal behaviour of the modem:
when the daemon call the refclock_transmit procedure and then send to
the modem the dial command ... nothing happens! one minute later, the
modem open the connection and try to dial the phone number but a
couple of seconds later the daemon send the hangup command to the
modem ad so the call is interrupted. This sequence is repeated whith a
period of about one minute.

I've tryed to customize the config string of the modem, without
success.
I think this behaviour may be due to the combination of host computer
HW and OS type, the modem; or I'm missing something in the
configuration.

I can supply more information, if usefull to solve the problem.

Giuseppe


----------------------------------------------
this is the output of the command ntpd -d:

ntpd 4.2.0a at 1.1250 Thu Nov  4 17:50:43 UTC 2004 (1)
addto_syslog: ntpd 4.2.0a at 1.1250 Thu Nov  4 17:50:43 UTC 2004 (1)
addto_syslog: signal_no_reset: signal 13 had flags 4000000
addto_syslog: precision = 1.000 usec
create_sockets(123)
addto_syslog: no IPv6 interfaces found
bind() fd 4, family 2, port 123, addr 0.0.0.0, flags=8
Added addr 0.0.0.0 to list of addresses
addto_syslog: Listening on interface wildcard, 0.0.0.0#123
bind() fd 5, family 2, port 123, addr 127.0.0.1, flags=0
Added addr 127.0.0.1 to list of addresses
addto_syslog: Listening on interface lo, 127.0.0.1#123
...
init_io: maxactivefd 6
local_clock: time 0 base 0.000000 offset 0.000000 freq 0.000 state 0
peer_clear: at 0 assoc ID 17388 refid INIT
newpeer: 127.0.0.1->127.127.18.1 mode 3 vers 4 poll 6 10 flags 0xa1
0x1 ttl 0 ke
y 00000000
report_event: system event 'event_restart' (0x01) status 'sync_alarm,
sync_unspe
c, 1 event, event_unspec' (0xc010)
refclock_transmit: at 1 127.127.18.1
auth_agekeys: at 1 keys 1 expired 0
refclock_setup fd 7 modem status: 0x4126
refclock_ioctl: fd 7 flags 0x24
acts: setup ATB1&C1&D2E0L1M1Q0V1
acts: (2 3) 2 OK
filegen  2 3308580471 0 3308515200
acts: dial 0 ATDT263

********** modem does not dial the number ! ****************

auth_agekeys: at 60 keys 1 expired 0
addto_syslog: acts: no answer
acts: call failed
acts: hangup


********** the modem try now to dial the number, but a couple of
second later ********** the daemon send the modem the hangup command !

refclock_transmit: at 66 127.127.18.1
acts: (1 1) 10 NO CARRIER
acts: setup ATB1&C1&D2E0L1M1Q0V1
acts: (2 3) 2 OK
acts: dial 0 ATDT263
auth_agekeys: at 120 keys 1 expired 0
addto_syslog: acts: no answer
acts: call failed
acts: hangup
refclock_transmit: at 130 127.127.18.1
acts: setup ATB1&C1&D2E0L1M1Q0V1
acts: (2 3) 10 NO CARRIER
addto_syslog: acts: no modem
acts: call failed
acts: hangup
acts: (0 3) 2 OK
...



stenn at maccarony.ntp.org (Harlan Stenn) wrote in message news:<cmca3u$gs2$1 at dewey.udel.edu>...
> You need to be using an ntp-dev tarball snapshot, not ntp-stable.
> 
> H



More information about the questions mailing list