ACTS Problem with Internal Modem - NTP

This is a discussion on ACTS Problem with Internal Modem - NTP ; I'm having a problem with the use of the ACTS driver in association with an internal modem. I'm running FreeBSD 6.2 with a 3COM internal modem. This is definitely not a "winmodem". For some reason when NTPD attempts to dial ...

+ Reply to Thread
Results 1 to 20 of 20

Thread: ACTS Problem with Internal Modem

  1. ACTS Problem with Internal Modem

    I'm having a problem with the use of the ACTS driver in association
    with an internal modem. I'm running FreeBSD 6.2 with a 3COM internal
    modem. This is definitely not a "winmodem". For some reason when NTPD
    attempts to dial the modem it appears to fail every time logging no
    modem in the ntp.log file.

    I've tried to adjust the modem setup string and recompile NTPD to no
    avail. The odd part is I can use the "tip" command to the com port
    associated with the modem and using the exact values specified in the
    modem setup string everything works. I can dial the phone number
    manually without issue. Only NTPD fails to successfully use the modem.

    In the particular server I'm using I don't have a "spare" come port to
    use just for the backup ACTS service as the 1 that's available is
    connected to a GPS receiver.

    Any assistance is greatly appreciated.

    Taro L. Johnson

  2. Re: ACTS Problem with Internal Modem

    IIRC, some versions of ntp required the ATDT in the config file and some
    didn't. Did you try both versions? I would recommend running in
    foreground mode using -ddd to see the actual modem exchange. It might
    give you a clue.


    Greg Dowd
    gdowd at symmetricom dot com (antispam format)
    Symmetricom, Inc.
    www.symmetricom.com
    "Everything should be made as simple as possible, but no simpler" Albert
    Einstein

    -----Original Message-----
    From: questions-bounces+gdowd=symmetricom.com@lists.ntp.org
    [mailto:questions-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf
    Of taro.johnson@gmail.com
    Sent: Sunday, May 25, 2008 2:30 PM
    To: questions@lists.ntp.org
    Subject: ACTS Problem with Internal Modem

    I'm having a problem with the use of the ACTS driver in association with
    an internal modem. I'm running FreeBSD 6.2 with a 3COM internal modem.
    This is definitely not a "winmodem". For some reason when NTPD attempts
    to dial the modem it appears to fail every time logging no modem in the
    ntp.log file.

    I've tried to adjust the modem setup string and recompile NTPD to no
    avail. The odd part is I can use the "tip" command to the com port
    associated with the modem and using the exact values specified in the
    modem setup string everything works. I can dial the phone number
    manually without issue. Only NTPD fails to successfully use the modem.

    In the particular server I'm using I don't have a "spare" come port to
    use just for the backup ACTS service as the 1 that's available is
    connected to a GPS receiver.

    Any assistance is greatly appreciated.

    Taro L. Johnson

    _______________________________________________
    questions mailing list
    questions@lists.ntp.org
    https://lists.ntp.org/mailman/listinfo/questions

  3. Re: ACTS Problem with Internal Modem

    Greg,

    Unless somebody else changed it, the ACTS driver refclock_acts.c that
    left me always did require the full explicit Hayes string. If the only
    message was "acts: no modem", the modem did not respond to the
    MODEM_SETUP string. I have not yet found a modem that does not respond
    to that string, but this might be the first.

    Dave

    Greg Dowd wrote:
    > IIRC, some versions of ntp required the ATDT in the config file and some
    > didn't. Did you try both versions? I would recommend running in
    > foreground mode using -ddd to see the actual modem exchange. It might
    > give you a clue.
    >
    >
    > Greg Dowd
    > gdowd at symmetricom dot com (antispam format)
    > Symmetricom, Inc.
    > www.symmetricom.com
    > "Everything should be made as simple as possible, but no simpler" Albert
    > Einstein
    >
    > -----Original Message-----
    > From: questions-bounces+gdowd=symmetricom.com@lists.ntp.org
    > [mailto:questions-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf
    > Of taro.johnson@gmail.com
    > Sent: Sunday, May 25, 2008 2:30 PM
    > To: questions@lists.ntp.org
    > Subject: ACTS Problem with Internal Modem
    >
    > I'm having a problem with the use of the ACTS driver in association with
    > an internal modem. I'm running FreeBSD 6.2 with a 3COM internal modem.
    > This is definitely not a "winmodem". For some reason when NTPD attempts
    > to dial the modem it appears to fail every time logging no modem in the
    > ntp.log file.
    >
    > I've tried to adjust the modem setup string and recompile NTPD to no
    > avail. The odd part is I can use the "tip" command to the com port
    > associated with the modem and using the exact values specified in the
    > modem setup string everything works. I can dial the phone number
    > manually without issue. Only NTPD fails to successfully use the modem.
    >
    > In the particular server I'm using I don't have a "spare" come port to
    > use just for the backup ACTS service as the 1 that's available is
    > connected to a GPS receiver.
    >
    > Any assistance is greatly appreciated.
    >
    > Taro L. Johnson
    >
    > _______________________________________________
    > questions mailing list
    > questions@lists.ntp.org
    > https://lists.ntp.org/mailman/listinfo/questions


  4. Re: ACTS Problem with Internal Modem

    Sorry for the delay in getting back but I've been very busy lately.
    Thanks for the replies but I've tried using the debug mode to see what
    was going on and I still can't tell why its not working under ntpd's
    control. I've tried this in both FreeBSD 6.2 & 7.0 with 2 different
    3com modem, both however the same modem.

    Here are the lines produced concerning the modem when pciconf -l -v is
    executed.

    sio4@pci0:3:3:0: class=0x070002 card=0x00d312b9 chip=0x100812b9
    rev=0x01 hdr=0x00
    vendor = '3COM Corp, Modem Division (Formerly US Robotics)'
    device = 'USR5610B USR5610B (0005610-02) 56K Performance Pro
    Modem (PCI Internal)'
    class = simple comms
    subclass = UART

    When I run ntpd -ddd here is what I get. (I've modified the IP
    addresses within the log to keep it a bit more anonymous.)

    ntpd 4.2.4p5-RC1@1.1531-o Sat Jun 7 20:40:01 UTC 2008 (1)
    addto_syslog: set_process_priority: Leave priority alone:
    priority_done is <2>
    addto_syslog: precision = 1.955 usec
    create_sockets(123)
    addto_syslog: ntp_io: estimated max descriptors: 7322, initial socket
    boundary: 20
    addto_syslog: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    update_interfaces(123)
    addto_syslog: no IPv6 interfaces found
    addto_syslog: no IPv6 interfaces found
    create_interface(192.168.161.104#123)
    addto_syslog: Listening on interface #1 em0, 192.168.161.104#123
    Enabled
    created interface #1: fd=21, bfd=-1, name=em0, flags=0x19, scope=0,
    ifindex=0, sin=192.168.161.104, bcast=192.168.161.255,,
    mask=255.255.255.0, Enabled:
    updating interface #1: fd=21, bfd=-1, name=em0, flags=0x19, scope=0,
    ifindex=0, sin=192.168.161.104, bcast=192.168.161.255,,
    mask=255.255.255.0, Enabled: new - created
    create_interface(192.167.113.32#123)
    addto_syslog: Listening on interface #2 em1, 192.167.113.32#123
    Enabled
    created interface #2: fd=22, bfd=-1, name=em1, flags=0x19, scope=0,
    ifindex=0, sin=192.167.113.32, bcast=192.167.113.255,,
    mask=255.255.255.0, Enabled:
    updating interface #2: fd=22, bfd=-1, name=em1, flags=0x19, scope=0,
    ifindex=0, sin=192.167.113.32, bcast=192.167.113.255,,
    mask=255.255.255.0, Enabled: new - created
    create_interface(127.0.0.1#123)
    addto_syslog: Listening on interface #3 lo0, 127.0.0.1#123 Enabled
    created interface #3: fd=23, bfd=-1, name=lo0, flags=0x15, scope=0,
    ifindex=0, sin=127.0.0.1, mask=255.0.0.0, Enabled:
    updating interface #3: fd=23, bfd=-1, name=lo0, flags=0x15, scope=0,
    ifindex=0, sin=127.0.0.1, mask=255.0.0.0, Enabled: new - created
    create_sockets: Total interfaces = 4
    addto_syslog: Listening on routing socket on fd #24 for interface
    updates
    init_io: maxactivefd 24
    local_clock: time 0 offset 0.000000 freq 0.000 state 0
    addto_syslog: kernel time sync status 2040
    getnetnum given 127.127.18.1, got 127.127.18.1 (t_UNK/0)
    newpeer: cast flags: 0x1 for address: 127.127.18.1
    newpeer: using fd 23 and our addr 127.0.0.1
    peer_crypto_clear: at 0 next 0 assoc ID 60972
    key_expire: at 0
    peer_clear: at 0 next 1 assoc ID 60972 refid INIT
    newpeer: 127.0.0.1->127.127.18.1 mode 3 vers 4 poll 11 15 flags 0x21
    0x1 ttl 0 key 00000000
    getnetnum given 127.127.18.1, got 127.127.18.1 (t_REF/1)
    addto_syslog: frequency initialized 0.000 PPM from /var/ntp/ntp.drift
    authtrust: keyid 0000ffff life 1
    local_clock: time 0 offset 0.000000 freq 0.000 state 1
    report_event: system event 'event_restart' (0x01) status 'sync_alarm,
    sync_unspec, 1 event, event_unspec' (0xc010)
    refclock_setup fd 4 modem status: 0x127
    refclock_ioctl: fd 4 flags 0xa4
    acts: setup ATB1&C0&D2E0L1M1Q0V1
    refclock_transmit: at 1 127.127.18.1
    poll_update: at 1 127.127.18.1 flags 0021 poll 11 burst 0 last 1 next
    2051
    auth_agekeys: at 1 keys 1 expired 0
    timer: refresh ts 0
    timer: interface update
    update_interfaces(123)
    addto_syslog: no IPv6 interfaces found

    addto_syslog: no IPv6 interfaces found

    refclock_gtraw: fd 4 time 3421861508.760820 timecode 1 Q
    refclock_gtraw: fd 4 time 3421861508.769643 timecode 4 0V1
    addto_syslog: acts: no modem

    refclock_gtraw: fd 4 time 3421861511.761957 timecode 2 AT
    refclock_gtraw: fd 4 time 3421861511.770210 timecode 8 H OK

    acts: 0125 (6 3) 7 Q0V1ATH
    acts: 0125 (6 3) 2 OK
    refclock_setup fd 4 modem status: 0x127
    refclock_ioctl: fd 4 flags 0xa4
    acts: setup ATB1&C0&D2E0L1M1Q0V1
    refclock_gtraw: fd 4 time 3421861517.760812 timecode 1 Q
    refclock_gtraw: fd 4 time 3421861517.769699 timecode 4 0V1
    addto_syslog: acts: no modem

    refclock_gtraw: fd 4 time 3421861520.762703 timecode 3 ATH
    refclock_gtraw: fd 4 time 3421861520.769703 timecode 6 OK
    acts: 0125 (6 3) 7 Q0V1ATH
    refclock_gtraw: fd 4 time 3421861520.772693 timecode 1

    acts: 0125 (6 3) 2 OK
    refclock_setup fd 4 modem status: 0x127
    refclock_ioctl: fd 4 flags 0xa4
    acts: setup ATB1&C0&D2E0L1M1Q0V1
    refclock_gtraw: fd 4 time 3421861526.760847 timecode 1 Q
    refclock_gtraw: fd 4 time 3421861526.762709 timecode 2 0V
    refclock_gtraw: fd 4 time 3421861526.769710 timecode 2 1
    addto_syslog: ntpd exiting on signal 2


    I know the modem is working just fine as I'm able to do the following
    at a simple terminal

    ntp# tip com5
    connected
    AT
    OK
    ATI
    5601

    OK
    ATB1&C0&D2E0L1M1Q0V1
    OK
    <--THERE WAS AN ATZ ISSUED HERE
    OK
    ATB1&C0&D2L3M1Q0V1 <-- SAME SETUP STRING MINUS THE E0 AS I WANTED TO
    SEE THE STRING
    OK
    ATDT9,13034944774
    CONNECT 14400/ARQ/V32/LAPM/V42BIS

    National Institute of Standards and Technology
    Telephone Time Service, Generator 1b
    Enter the question mark character for HELP
    D L
    MJD YR MO DA HH MM SS ST S UT1 msADV

    54624 08-06-07 21:17:24 50 0 -.4 045.0 UTC(NIST) *
    54624 08-06-07 21:17:25 50 0 -.4 045.0 UTC(NIST) *
    54624 08-06-07 21:17:26 50 0 -.4 045.0 UTC(NIST) *
    54624 08-06-07 21:17:27 50 0 -.4 045.0 UTC(NIST) *
    54624 08-06-07 21:17:28 50 0 -.4 045.0 UTC(NIST) *
    54624 08-06-07 21:17:29 50 0 -.4 045.0 UTC(NIST) *
    54624 08-06-07 21:17:30 50 0 -.4 045.0 UTC(NIST) *

    Any more assistance is greatly appreciated.

  5. Re: ACTS Problem with Internal Modem

    John,

    In the modem string ATB1&C0&D2E0L1M1Q0V1 the E0 turns off command
    echoing. However, I see apparent echoicing anyway. In response to that
    string, the program expects an OK and nothing else. What came back
    appears to be a broken fragment of the setup string. You may need to
    fiddle the modem registers or revert to factory defaults.

    Dave

    taro.johnson@gmail.com wrote:
    > Sorry for the delay in getting back but I've been very busy lately.
    > Thanks for the replies but I've tried using the debug mode to see what
    > was going on and I still can't tell why its not working under ntpd's
    > control. I've tried this in both FreeBSD 6.2 & 7.0 with 2 different
    > 3com modem, both however the same modem.
    >
    > Here are the lines produced concerning the modem when pciconf -l -v is
    > executed.
    >
    > sio4@pci0:3:3:0: class=0x070002 card=0x00d312b9 chip=0x100812b9
    > rev=0x01 hdr=0x00
    > vendor = '3COM Corp, Modem Division (Formerly US Robotics)'
    > device = 'USR5610B USR5610B (0005610-02) 56K Performance Pro
    > Modem (PCI Internal)'
    > class = simple comms
    > subclass = UART
    >
    > When I run ntpd -ddd here is what I get. (I've modified the IP
    > addresses within the log to keep it a bit more anonymous.)
    >
    > ntpd 4.2.4p5-RC1@1.1531-o Sat Jun 7 20:40:01 UTC 2008 (1)
    > addto_syslog: set_process_priority: Leave priority alone:
    > priority_done is <2>
    > addto_syslog: precision = 1.955 usec
    > create_sockets(123)
    > addto_syslog: ntp_io: estimated max descriptors: 7322, initial socket
    > boundary: 20
    > addto_syslog: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    > update_interfaces(123)
    > addto_syslog: no IPv6 interfaces found
    > addto_syslog: no IPv6 interfaces found
    > create_interface(192.168.161.104#123)
    > addto_syslog: Listening on interface #1 em0, 192.168.161.104#123
    > Enabled
    > created interface #1: fd=21, bfd=-1, name=em0, flags=0x19, scope=0,
    > ifindex=0, sin=192.168.161.104, bcast=192.168.161.255,,
    > mask=255.255.255.0, Enabled:
    > updating interface #1: fd=21, bfd=-1, name=em0, flags=0x19, scope=0,
    > ifindex=0, sin=192.168.161.104, bcast=192.168.161.255,,
    > mask=255.255.255.0, Enabled: new - created
    > create_interface(192.167.113.32#123)
    > addto_syslog: Listening on interface #2 em1, 192.167.113.32#123
    > Enabled
    > created interface #2: fd=22, bfd=-1, name=em1, flags=0x19, scope=0,
    > ifindex=0, sin=192.167.113.32, bcast=192.167.113.255,,
    > mask=255.255.255.0, Enabled:
    > updating interface #2: fd=22, bfd=-1, name=em1, flags=0x19, scope=0,
    > ifindex=0, sin=192.167.113.32, bcast=192.167.113.255,,
    > mask=255.255.255.0, Enabled: new - created
    > create_interface(127.0.0.1#123)
    > addto_syslog: Listening on interface #3 lo0, 127.0.0.1#123 Enabled
    > created interface #3: fd=23, bfd=-1, name=lo0, flags=0x15, scope=0,
    > ifindex=0, sin=127.0.0.1, mask=255.0.0.0, Enabled:
    > updating interface #3: fd=23, bfd=-1, name=lo0, flags=0x15, scope=0,
    > ifindex=0, sin=127.0.0.1, mask=255.0.0.0, Enabled: new - created
    > create_sockets: Total interfaces = 4
    > addto_syslog: Listening on routing socket on fd #24 for interface
    > updates
    > init_io: maxactivefd 24
    > local_clock: time 0 offset 0.000000 freq 0.000 state 0
    > addto_syslog: kernel time sync status 2040
    > getnetnum given 127.127.18.1, got 127.127.18.1 (t_UNK/0)
    > newpeer: cast flags: 0x1 for address: 127.127.18.1
    > newpeer: using fd 23 and our addr 127.0.0.1
    > peer_crypto_clear: at 0 next 0 assoc ID 60972
    > key_expire: at 0
    > peer_clear: at 0 next 1 assoc ID 60972 refid INIT
    > newpeer: 127.0.0.1->127.127.18.1 mode 3 vers 4 poll 11 15 flags 0x21
    > 0x1 ttl 0 key 00000000
    > getnetnum given 127.127.18.1, got 127.127.18.1 (t_REF/1)
    > addto_syslog: frequency initialized 0.000 PPM from /var/ntp/ntp.drift
    > authtrust: keyid 0000ffff life 1
    > local_clock: time 0 offset 0.000000 freq 0.000 state 1
    > report_event: system event 'event_restart' (0x01) status 'sync_alarm,
    > sync_unspec, 1 event, event_unspec' (0xc010)
    > refclock_setup fd 4 modem status: 0x127
    > refclock_ioctl: fd 4 flags 0xa4
    > acts: setup ATB1&C0&D2E0L1M1Q0V1
    > refclock_transmit: at 1 127.127.18.1
    > poll_update: at 1 127.127.18.1 flags 0021 poll 11 burst 0 last 1 next
    > 2051
    > auth_agekeys: at 1 keys 1 expired 0
    > timer: refresh ts 0
    > timer: interface update
    > update_interfaces(123)
    > addto_syslog: no IPv6 interfaces found
    >
    > addto_syslog: no IPv6 interfaces found
    >
    > refclock_gtraw: fd 4 time 3421861508.760820 timecode 1 Q
    > refclock_gtraw: fd 4 time 3421861508.769643 timecode 4 0V1
    > addto_syslog: acts: no modem
    >
    > refclock_gtraw: fd 4 time 3421861511.761957 timecode 2 AT
    > refclock_gtraw: fd 4 time 3421861511.770210 timecode 8 H OK
    >
    > acts: 0125 (6 3) 7 Q0V1ATH
    > acts: 0125 (6 3) 2 OK
    > refclock_setup fd 4 modem status: 0x127
    > refclock_ioctl: fd 4 flags 0xa4
    > acts: setup ATB1&C0&D2E0L1M1Q0V1
    > refclock_gtraw: fd 4 time 3421861517.760812 timecode 1 Q
    > refclock_gtraw: fd 4 time 3421861517.769699 timecode 4 0V1
    > addto_syslog: acts: no modem
    >
    > refclock_gtraw: fd 4 time 3421861520.762703 timecode 3 ATH
    > refclock_gtraw: fd 4 time 3421861520.769703 timecode 6 OK
    > acts: 0125 (6 3) 7 Q0V1ATH
    > refclock_gtraw: fd 4 time 3421861520.772693 timecode 1
    >
    > acts: 0125 (6 3) 2 OK
    > refclock_setup fd 4 modem status: 0x127
    > refclock_ioctl: fd 4 flags 0xa4
    > acts: setup ATB1&C0&D2E0L1M1Q0V1
    > refclock_gtraw: fd 4 time 3421861526.760847 timecode 1 Q
    > refclock_gtraw: fd 4 time 3421861526.762709 timecode 2 0V
    > refclock_gtraw: fd 4 time 3421861526.769710 timecode 2 1
    > addto_syslog: ntpd exiting on signal 2
    >
    >
    > I know the modem is working just fine as I'm able to do the following
    > at a simple terminal
    >
    > ntp# tip com5
    > connected
    > AT
    > OK
    > ATI
    > 5601
    >
    > OK
    > ATB1&C0&D2E0L1M1Q0V1
    > OK
    > <--THERE WAS AN ATZ ISSUED HERE
    > OK
    > ATB1&C0&D2L3M1Q0V1 <-- SAME SETUP STRING MINUS THE E0 AS I WANTED TO
    > SEE THE STRING
    > OK
    > ATDT9,13034944774
    > CONNECT 14400/ARQ/V32/LAPM/V42BIS
    >
    > National Institute of Standards and Technology
    > Telephone Time Service, Generator 1b
    > Enter the question mark character for HELP
    > D L
    > MJD YR MO DA HH MM SS ST S UT1 msADV
    >
    > 54624 08-06-07 21:17:24 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:25 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:26 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:27 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:28 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:29 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:30 50 0 -.4 045.0 UTC(NIST) *
    >
    > Any more assistance is greatly appreciated.


  6. Re: ACTS Problem with Internal Modem

    Aah. Good point Dave. I remember that USRobotics Sportster external
    modems had dip switches. That was always an issue for us as the
    switches took precedence over software commands. Maybe that's the case
    here John?


    Greg Dowd
    gdowd at symmetricom dot com (antispam format)
    Symmetricom, Inc.
    www.symmetricom.com
    "Everything should be made as simple as possible, but no simpler" Albert
    Einstein
    -----Original Message-----
    From: questions-bounces+gdowd=symmetricom.com@lists.ntp.org
    [mailto:questions-bounces+gdowd=symmetricom.com@lists.ntp.org] On Behalf
    Of David L. Mills
    Sent: Monday, June 09, 2008 9:29 AM
    To: questions@lists.ntp.org
    Subject: Re: ACTS Problem with Internal Modem

    John,

    In the modem string ATB1&C0&D2E0L1M1Q0V1 the E0 turns off command
    echoing. However, I see apparent echoicing anyway. In response to that
    string, the program expects an OK and nothing else. What came back
    appears to be a broken fragment of the setup string. You may need to
    fiddle the modem registers or revert to factory defaults.

    Dave

    taro.johnson@gmail.com wrote:
    > Sorry for the delay in getting back but I've been very busy lately.
    > Thanks for the replies but I've tried using the debug mode to see what
    > was going on and I still can't tell why its not working under ntpd's
    > control. I've tried this in both FreeBSD 6.2 & 7.0 with 2 different
    > 3com modem, both however the same modem.
    >
    > Here are the lines produced concerning the modem when pciconf -l -v is
    > executed.
    >
    > sio4@pci0:3:3:0: class=0x070002 card=0x00d312b9 chip=0x100812b9
    > rev=0x01 hdr=0x00
    > vendor = '3COM Corp, Modem Division (Formerly US Robotics)'
    > device = 'USR5610B USR5610B (0005610-02) 56K Performance Pro
    > Modem (PCI Internal)'
    > class = simple comms
    > subclass = UART
    >
    > When I run ntpd -ddd here is what I get. (I've modified the IP
    > addresses within the log to keep it a bit more anonymous.)
    >
    > ntpd 4.2.4p5-RC1@1.1531-o Sat Jun 7 20:40:01 UTC 2008 (1)
    > addto_syslog: set_process_priority: Leave priority alone:
    > priority_done is <2>
    > addto_syslog: precision = 1.955 usec
    > create_sockets(123)
    > addto_syslog: ntp_io: estimated max descriptors: 7322, initial socket
    > boundary: 20
    > addto_syslog: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    > update_interfaces(123)
    > addto_syslog: no IPv6 interfaces found
    > addto_syslog: no IPv6 interfaces found
    > create_interface(192.168.161.104#123)
    > addto_syslog: Listening on interface #1 em0, 192.168.161.104#123
    > Enabled
    > created interface #1: fd=21, bfd=-1, name=em0, flags=0x19, scope=0,
    > ifindex=0, sin=192.168.161.104, bcast=192.168.161.255,,
    > mask=255.255.255.0, Enabled:
    > updating interface #1: fd=21, bfd=-1, name=em0, flags=0x19, scope=0,
    > ifindex=0, sin=192.168.161.104, bcast=192.168.161.255,,
    > mask=255.255.255.0, Enabled: new - created
    > create_interface(192.167.113.32#123)
    > addto_syslog: Listening on interface #2 em1, 192.167.113.32#123
    > Enabled
    > created interface #2: fd=22, bfd=-1, name=em1, flags=0x19, scope=0,
    > ifindex=0, sin=192.167.113.32, bcast=192.167.113.255,,
    > mask=255.255.255.0, Enabled:
    > updating interface #2: fd=22, bfd=-1, name=em1, flags=0x19, scope=0,
    > ifindex=0, sin=192.167.113.32, bcast=192.167.113.255,,
    > mask=255.255.255.0, Enabled: new - created
    > create_interface(127.0.0.1#123)
    > addto_syslog: Listening on interface #3 lo0, 127.0.0.1#123 Enabled
    > created interface #3: fd=23, bfd=-1, name=lo0, flags=0x15, scope=0,
    > ifindex=0, sin=127.0.0.1, mask=255.0.0.0, Enabled:
    > updating interface #3: fd=23, bfd=-1, name=lo0, flags=0x15, scope=0,
    > ifindex=0, sin=127.0.0.1, mask=255.0.0.0, Enabled: new - created
    > create_sockets: Total interfaces = 4
    > addto_syslog: Listening on routing socket on fd #24 for interface
    > updates
    > init_io: maxactivefd 24
    > local_clock: time 0 offset 0.000000 freq 0.000 state 0
    > addto_syslog: kernel time sync status 2040
    > getnetnum given 127.127.18.1, got 127.127.18.1 (t_UNK/0)
    > newpeer: cast flags: 0x1 for address: 127.127.18.1
    > newpeer: using fd 23 and our addr 127.0.0.1
    > peer_crypto_clear: at 0 next 0 assoc ID 60972
    > key_expire: at 0
    > peer_clear: at 0 next 1 assoc ID 60972 refid INIT
    > newpeer: 127.0.0.1->127.127.18.1 mode 3 vers 4 poll 11 15 flags 0x21
    > 0x1 ttl 0 key 00000000
    > getnetnum given 127.127.18.1, got 127.127.18.1 (t_REF/1)
    > addto_syslog: frequency initialized 0.000 PPM from /var/ntp/ntp.drift
    > authtrust: keyid 0000ffff life 1
    > local_clock: time 0 offset 0.000000 freq 0.000 state 1
    > report_event: system event 'event_restart' (0x01) status 'sync_alarm,
    > sync_unspec, 1 event, event_unspec' (0xc010)
    > refclock_setup fd 4 modem status: 0x127
    > refclock_ioctl: fd 4 flags 0xa4
    > acts: setup ATB1&C0&D2E0L1M1Q0V1
    > refclock_transmit: at 1 127.127.18.1
    > poll_update: at 1 127.127.18.1 flags 0021 poll 11 burst 0 last 1 next
    > 2051
    > auth_agekeys: at 1 keys 1 expired 0
    > timer: refresh ts 0
    > timer: interface update
    > update_interfaces(123)
    > addto_syslog: no IPv6 interfaces found
    >
    > addto_syslog: no IPv6 interfaces found
    >
    > refclock_gtraw: fd 4 time 3421861508.760820 timecode 1 Q
    > refclock_gtraw: fd 4 time 3421861508.769643 timecode 4 0V1
    > addto_syslog: acts: no modem
    >
    > refclock_gtraw: fd 4 time 3421861511.761957 timecode 2 AT
    > refclock_gtraw: fd 4 time 3421861511.770210 timecode 8 H OK
    >
    > acts: 0125 (6 3) 7 Q0V1ATH
    > acts: 0125 (6 3) 2 OK
    > refclock_setup fd 4 modem status: 0x127
    > refclock_ioctl: fd 4 flags 0xa4
    > acts: setup ATB1&C0&D2E0L1M1Q0V1
    > refclock_gtraw: fd 4 time 3421861517.760812 timecode 1 Q
    > refclock_gtraw: fd 4 time 3421861517.769699 timecode 4 0V1
    > addto_syslog: acts: no modem
    >
    > refclock_gtraw: fd 4 time 3421861520.762703 timecode 3 ATH
    > refclock_gtraw: fd 4 time 3421861520.769703 timecode 6 OK
    > acts: 0125 (6 3) 7 Q0V1ATH
    > refclock_gtraw: fd 4 time 3421861520.772693 timecode 1
    >
    > acts: 0125 (6 3) 2 OK
    > refclock_setup fd 4 modem status: 0x127
    > refclock_ioctl: fd 4 flags 0xa4
    > acts: setup ATB1&C0&D2E0L1M1Q0V1
    > refclock_gtraw: fd 4 time 3421861526.760847 timecode 1 Q
    > refclock_gtraw: fd 4 time 3421861526.762709 timecode 2 0V
    > refclock_gtraw: fd 4 time 3421861526.769710 timecode 2 1
    > addto_syslog: ntpd exiting on signal 2
    >
    >
    > I know the modem is working just fine as I'm able to do the following
    > at a simple terminal
    >
    > ntp# tip com5
    > connected
    > AT
    > OK
    > ATI
    > 5601
    >
    > OK
    > ATB1&C0&D2E0L1M1Q0V1
    > OK
    > <--THERE WAS AN ATZ ISSUED HERE
    > OK
    > ATB1&C0&D2L3M1Q0V1 <-- SAME SETUP STRING MINUS THE E0 AS I WANTED TO
    > SEE THE STRING
    > OK
    > ATDT9,13034944774
    > CONNECT 14400/ARQ/V32/LAPM/V42BIS
    >
    > National Institute of Standards and Technology
    > Telephone Time Service, Generator 1b
    > Enter the question mark character for HELP
    > D L
    > MJD YR MO DA HH MM SS ST S UT1 msADV
    >
    > 54624 08-06-07 21:17:24 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:25 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:26 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:27 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:28 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:29 50 0 -.4 045.0 UTC(NIST) *
    > 54624 08-06-07 21:17:30 50 0 -.4 045.0 UTC(NIST) *
    >
    > Any more assistance is greatly appreciated.


    _______________________________________________
    questions mailing list
    questions@lists.ntp.org
    https://lists.ntp.org/mailman/listinfo/questions

  7. Re: ACTS Problem with Internal Modem

    Greg Dowd wrote:
    > Aah. Good point Dave. I remember that USRobotics Sportster external
    > modems had dip switches. That was always an issue for us as the
    > switches took precedence over software commands. Maybe that's the case
    > here John?
    >


    My recollection (It's been almost ten years since I needed a modem), is
    that the DIP switches set the modem's defaults. The commands could
    override most, if not all, of the DIP switch settings.

    Most modems supported the Hayes command set.

    YMMV

  8. Re: ACTS Problem with Internal Modem

    Taro,

    Just to ask, have you seen http://bugs.ntp.org/367 ?
    --
    Harlan Stenn
    http://ntpforum.isc.org - be a member!

  9. Re: ACTS Problem with Internal Modem

    On 2008-06-10, Harlan Stenn wrote:

    >Attribution Missing wrote:
    >
    >> Quoted context omitted

    >
    > Just to ask, have you seen http://bugs.ntp.org/367 ?


    Bug 367 concerns an ACTS driver problem:

    | ACTS driver hangs up after header receipt
    |
    | Is this driver still in a state of flux? My latest build happily calls
    | NIST ACTS, sees the header and then hangs up without waiting for the
    | timing strings. The same system runs an older 4.1.0 build successfully.

    Please see the bug report for additional log information as well as
    on-going discussion.

    --
    Steve Kostecke
    NTP Public Services Project - http://support.ntp.org/

  10. Re: ACTS Problem with Internal Modem

    On Jun 10, 5:08 am, Steve Kostecke wrote:
    > On 2008-06-10, Harlan Stenn wrote:
    >
    > >Attribution Missing wrote:

    >
    > >> Quoted context omitted

    >
    > > Just to ask, have you seenhttp://bugs.ntp.org/367?

    >
    > Bug 367 concerns an ACTS driver problem:
    >
    > | ACTS driver hangs up after header receipt
    > |
    > | Is this driver still in a state of flux? My latest build happily calls
    > | NIST ACTS, sees the header and then hangs up without waiting for the
    > | timing strings. The same system runs an older 4.1.0 build successfully.
    >
    > Please see the bug report for additional log information as well as
    > on-going discussion.
    >
    > --
    > Steve Kostecke
    > NTP Public Services Project -http://support.ntp.org/hat


    No I hadn't seen the bug provided but after reading over it, I would
    say that it doesn't apply the problem I'm having. This modem doesn't
    have any dip switches to set but I will see if there is a method to
    reset the modem to its factory defaults. I as well saw what appears to
    be the modem string being echoed back. The odd thing about that is
    that the same results were not seem when just using tip. In the logs I
    provided I issued a ATB1&C0&D2E0L1M1Q0V1 to which the modem replied
    with OK. The next command that was sent was ATZ but in the log that
    wasn't seen because the modem did just as it was instructed and didn't
    echo it.

  11. Re: ACTS Problem with Internal Modem

    Steve,

    As the author of the driver I attempted to access the bug system you
    linked, but the bug system refused to access based on certificate
    issues. Therefore, I will require direct mail to resolve any bug reports.

    Dave

    Steve Kostecke wrote:
    > On 2008-06-10, Harlan Stenn wrote:
    >
    >
    >>Attribution Missing wrote:
    >>
    >>
    >>>Quoted context omitted

    >>
    >>Just to ask, have you seen http://bugs.ntp.org/367 ?

    >
    >
    > Bug 367 concerns an ACTS driver problem:
    >
    > | ACTS driver hangs up after header receipt
    > |
    > | Is this driver still in a state of flux? My latest build happily calls
    > | NIST ACTS, sees the header and then hangs up without waiting for the
    > | timing strings. The same system runs an older 4.1.0 build successfully.
    >
    > Please see the bug report for additional log information as well as
    > on-going discussion.
    >


  12. Re: ACTS Problem with Internal Modem

    On 2008-06-11, David L. Mills wrote:

    > As the author of the driver I attempted to access the bug system you
    > linked, but the bug system refused to access based on certificate
    > issues. Therefore, I will require direct mail to resolve any bug reports.


    You have been on the CC: list for this bug since (at least) early
    December, 2007, and should be receiving all bug comments via direct
    e-mail.

    Please see my direct e-mail for more information.

    --
    Steve Kostecke
    NTP Public Services Project - http://support.ntp.org/

  13. Re: ACTS Problem with Internal Modem

    Dave,

    David L. Mills wrote:
    > Steve,
    >
    > As the author of the driver I attempted to access the bug system you
    > linked, but the bug system refused to access based on certificate
    > issues. Therefore, I will require direct mail to resolve any bug reports.


    AFAIK the certificate is renewed from time to time, and the certificate
    signed by the CAcert organisation, see http://www.cacert.org

    Maybe you just have to import the CAcert root certificate once to your
    browser. See: http://www.cacert.org/index.php?id=3

    After this your browser should be able to verify the certificate from
    support.ntp.org automatically in the future.

    Martin
    --
    Martin Burnicki

    Meinberg Funkuhren
    Bad Pyrmont
    Germany

  14. Re: ACTS Problem with Internal Modem

    >>> In article , taro.johnson@gmail.com writes:

    > On Jun 10, 5:08 am, Steve Kostecke wrote:
    >> On 2008-06-10, Harlan Stenn wrote:
    >>
    >> > Just to ask, have you seenhttp://bugs.ntp.org/367?

    >>
    >> Bug 367 concerns an ACTS driver problem:
    >>
    >> | ACTS driver hangs up after header receipt
    >>
    >> Please see the bug report for additional log information as well as
    >> on-going discussion.
    >>
    >> -- Steve Kostecke NTP Public Services Project
    >> -http://support.ntp.org/hat


    taro> No I hadn't seen the bug provided but after reading over it, I would
    taro> say that it doesn't apply the problem I'm having. This modem doesn't
    taro> have any dip switches to set but I will see if there is a method to
    taro> reset the modem to its factory defaults. I as well saw what appears to
    taro> be the modem string being echoed back.

    The issue is not about DIP switches, it is about a timing issue on some
    machines where Greg says adding a small delay greatly improves the ability
    of the ACTS driver to successfully complete a call to get the time.

    --
    Harlan Stenn
    http://ntpforum.isc.org - be a member!

  15. Re: ACTS Problem with Internal Modem

    Martin Burnicki wrote:

    >
    > Maybe you just have to import the CAcert root certificate once to your
    > browser. See: http://www.cacert.org/index.php?id=3


    I believe that Dr Mills is on record as effectively saying: "If
    Microsoft won't trust cacert.org, why should I". In reality, part of
    Microsoft's reasons will be that cacert.org doesn't operate on the basis
    of generating revenue from their service.

    I think you are facing an effective boycott of cacert.org.

  16. Re: ACTS Problem with Internal Modem

    On 2008-06-11, David Woolley
    wrote:

    > I believe that Dr Mills is on record as effectively saying: "If
    > Microsoft won't trust cacert.org, why should I". In reality, part of
    > Microsoft's reasons will be that cacert.org doesn't operate on the
    > basis of generating revenue from their service.


    Like everything else SSL, this has nothing to do with security and
    eveything to do with monetization. CAs must pay Microsoft a substantial
    sum to have their Root Cert distributed with internet explorer.

    --
    Steve Kostecke
    NTP Public Services Project - http://support.ntp.org/

  17. Re: ACTS Problem with Internal Modem

    Martin,

    I will not import anything. If folks want me to help, I would be
    delighted to provide it. I will not import anything or provide personal
    information or even feedback that I have imported anything to anybody.
    You want help, those are my conditions.

    Dave

    Martin Burnicki wrote:
    > Dave,
    >
    > David L. Mills wrote:
    >
    >>Steve,
    >>
    >>As the author of the driver I attempted to access the bug system you
    >>linked, but the bug system refused to access based on certificate
    >>issues. Therefore, I will require direct mail to resolve any bug reports.

    >
    >
    > AFAIK the certificate is renewed from time to time, and the certificate
    > signed by the CAcert organisation, see http://www.cacert.org
    >
    > Maybe you just have to import the CAcert root certificate once to your
    > browser. See: http://www.cacert.org/index.php?id=3
    >
    > After this your browser should be able to verify the certificate from
    > support.ntp.org automatically in the future.
    >
    > Martin


  18. Re: ACTS Problem with Internal Modem

    David Woolley wrote:

    > Martin Burnicki wrote:
    >
    >>
    >> Maybe you just have to import the CAcert root certificate once to your
    >> browser. See: http://www.cacert.org/index.php?id=3

    >
    > I believe that Dr Mills is on record as effectively saying: "If
    > Microsoft won't trust cacert.org, why should I". In reality, part of
    > Microsoft's reasons will be that cacert.org doesn't operate on the basis
    > of generating revenue from their service.
    >
    > I think you are facing an effective boycott of cacert.org.


    It's not only related to Microsoft. In fact, not even the latest version of
    firefox I've installed here comes with CAcert's root certificate
    pre-installed.

    Don't know what's going on there.

    Martin
    --
    Martin Burnicki

    Meinberg Funkuhren
    Bad Pyrmont
    Germany

  19. Re: ACTS Problem with Internal Modem

    Dave,

    David L. Mills wrote:
    > Martin,
    >
    > I will not import anything. If folks want me to help, I would be
    > delighted to provide it. I will not import anything or provide personal
    > information or even feedback that I have imported anything to anybody.


    I'm assuming you're more familiar than me with signing certificates. Did you
    ever hear about CAcert.org which is a well-known certification authority
    since several years?

    You can either trust the certificates signed by CAcert, or you don't and
    stay outside all https pages using certificates signed by CAcert (not only
    support.ntp.org). It's your decision.

    > You want help, those are my conditions.


    Please note in this case I tried to help *you*.


    Martin
    --
    Martin Burnicki

    Meinberg Funkuhren
    Bad Pyrmont
    Germany

  20. Re: ACTS Problem with Internal Modem

    In article

    taro.johnson@gmail.com writes:

    >ATB1&C0&D2E0L1M1Q0V1
    >OK
    > <--THERE WAS AN ATZ ISSUED HERE
    >OK
    >ATB1&C0&D2L3M1Q0V1 <-- SAME SETUP STRING MINUS THE E0 AS I WANTED TO
    >SEE THE STRING


    I have long since forgotten what most of that stuff does, I just thought
    that I should point out that you didn't just remove E0, you also changed
    L1 to L3 - might be significant?

    --Per Hedeland
    per@hedeland.org

+ Reply to Thread