🚀 go-pugleaf

On Tue, 12 May 1998 owner-netblazer-users@itk-tele.com wrote:

> Hi,
> 
> "No chat script" message is displayed in syslog.
> This message is many times displayed for a while.
> 
> What does "no chat script" message mean?
> Is this critical message or not so?
> And if you have any idea, please let me know how long is this
> message displayed.
> 

In this case, "no chat script" probably means that the NetBlazer
tried to make an outgoing call to bring up interface PN036001,
found a dialout record, and then discovered that the dialout record
did not have a chat script set so the NetBlazer could not complete the
call.

The NetBlazer probably tried to bring up the interface because a packet
was routed to it.  If the host at the far side of this interface had any
active connections at the time the interface was brought down by an idle
timeout, the other end of the connection may still transmit packets.  If
you keep routing these packets to interface PN036001, the NetBlazer will
keep trying to bring up that interface. 

There are a couple of things you can do:

1.  If you don't want the NetBlazer to be routing packets to PN036001
    after the interface is down, use the "auto-route" or "auto-arp" 
    command instead of the "route add" command to set up routes on the
    interface.  Routes added by auto-route and auto-arp disappear when the
    interface goes down.

    Using an IP pool and having the NetBlazer assign the IP address to the
    remote host will also result in routes that go away when the interface
    goes down.

2.  If you want the NetBlazer to be able to make an outgoing call on this
    interface when it has packets to deliver, then fix the dialout record
    by adding a chat script.

Thanks,
Mike

> Apr  2 16:55:02 OA_AS syslog: start login on line101
> Apr  2 16:55:03 OA_AS syslog: PPP frame detected on line101
> Apr  2 16:55:03 OA_AS syslog: starting ppp on line101
> Apr  2 16:55:03 OA_AS syslog: PN036001 logged-in from line101
> Apr  2 16:55:03 OA_AS syslog: PPP PAP login PN036001 on line101
> Apr  2 16:55:03 OA_AS syslog: PN036001 PPP/Lcp Protocol Reject (IPXCP);
> please do not use this protocol
> Apr  2 16:55:03 OA_AS syslog: PN036001 PPP/Lcp Protocol Reject (ATCP);
> please do not use this protocol
> Apr  2 16:55:31 OA_AS syslog: inbound PN036001 dial packet on line101
> Apr  2 17:04:19 OA_AS syslog: Dynamic timeout for interface "PN036001"
> exceeded -- dropping line.
> Apr  2 17:04:22 OA_AS syslog: inbound dynamic interface 'PN036001' used
> line101 for 559 seconds 10.36.1.11
> Apr  2 17:04:22 OA_AS syslog: PN036001 on line101 at Apr  2 16:55 for 559
> seconds
> 
> Apr  2 17:04:49 OA_AS syslog: start login on line100
> Apr  2 17:04:50 OA_AS syslog: PPP frame detected on line100
> Apr  2 17:04:50 OA_AS syslog: starting ppp on line100
> Apr  2 17:04:51 OA_AS syslog: PN036001 logged-in from line100
> Apr  2 17:04:51 OA_AS syslog: PPP PAP login PN036001 on line100
> Apr  2 17:04:51 OA_AS syslog: PN036001 PPP/Lcp Protocol Reject (IPXCP);
> please do not use this protocol
> Apr  2 17:04:51 OA_AS syslog: PN036001 PPP/Lcp Protocol Reject (ATCP);
> please do not use this protocol
> Apr  2 17:05:20 OA_AS syslog: inbound PN036001 dial packet on line100
> Apr  2 17:05:29 OA_AS syslog: inbound dynamic interface 'PN036001' used
> line100 for 38 seconds 
> Apr  2 17:05:29 OA_AS syslog: PN036001 on line100 at Apr  2 17:04 for 38
> seconds
> Apr  2 17:05:35 OA_AS syslog: no chat script for PN036001
> Apr  2 17:05:49 OA_AS last message repeated 11 times
> 
> 
> Thanks,
> Hiroshi Yamashita
> 
-- 
Mike Thornburg         |  I do not speak for frigate networks;
mthorn@frigate.com     |  I'm just a guest here now.