Wed Mar 15, 2017 4:04 pm
Thanks for the info, I was going to do wireshark, but I did find the logging option in system tab, and set it to log 65000 lines for a total of 75 files. I finally found what might be causing the drop, but not sure how to fix it in mikrotik. In my log I am seeing this:
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <magic 0xb97fa656>
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <13b4>: sent LCP EchoRep id=0xba
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <magic 0x4e28f69f>
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <13e5>: rcvd LCP TermReq id=0xc
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet Peer not responding
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: LCP closed
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: CCP lowerdown
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: BCP lowerdown
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: BCP down event in starting state
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: IPCP lowerdown
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: IPCP closed
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: IPV6CP lowerdown
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: IPV6CP down event in starting state
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: MPLSCP lowerdown
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: MPLSCP down event in starting state
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <13e5>: sent LCP TermAck id=0xc
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: LCP lowerdown
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: LCP lowerdown
Mar/15/2017 05:49:12 pppoe,ppp,debug <13e5>: LCP down event in starting state
Mar/15/2017 05:49:12 pppoe,debug,packet vlan-110: sent PADT to 60:31:97:48:0F:80
Mar/15/2017 05:49:12 pppoe,debug,packet session-id=0x13e5
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <12bc>: rcvd LCP EchoReq id=0xa0
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <magic 0x1b9dda27>
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <12bc>: sent LCP EchoRep id=0xa0
Mar/15/2017 05:49:12 pppoe,ppp,debug,packet <magic 0x2df7eb22>
So I guess I am to assume that the modem is not responding to the echo request from the mikrotik in a timely manner. Is there a way to set the mikrotik to tolerate more missed echo requests before killing the ppp connection and trying to re-establish a new one.