Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    WAN periodically Rebooting

    Scheduled Pinned Locked Moved General pfSense Questions
    184 Posts 5 Posters 31.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      diyhouse @diyhouse
      last edited by

      @diyhouse,.. Well spoke to soon,.. had numerous reboots,.. around 5:30am this morning,.. and its been off several times since,.. These are the most recent PPP down... Any thoughts..

      Aug 13 13:52:42	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 13:52:41	ppp	71373	[wan] IFACE: Add description "1_WAN"
Aug 13 13:52:41	ppp	71373	[wan] IFACE: Rename interface ng0 to pppoe0
Aug 13 13:52:41	ppp	71373	[wan] IFACE: Up event
Aug 13 13:52:40	ppp	71373	[wan] 109.147.50.193 -> 172.16.12.102
Aug 13 13:52:40	ppp	71373	[wan] IPCP: LayerUp
Aug 13 13:52:40	ppp	71373	[wan] IPCP: state change Ack-Sent --> Opened
Aug 13 13:52:40	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 13:52:40	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 13:52:40	ppp	71373	[wan] IPADDR 109.147.50.193
Aug 13 13:52:40	ppp	71373	[wan] IPCP: rec'd Configure Ack #47 (Ack-Sent)
Aug 13 13:52:40	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 13:52:40	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 13:52:40	ppp	71373	[wan] IPADDR 109.147.50.193
Aug 13 13:52:40	ppp	71373	[wan] IPCP: SendConfigReq #47
Aug 13 13:52:40	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 13:52:40	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 13:52:40	ppp	71373	[wan] 109.147.50.193 is OK
Aug 13 13:52:40	ppp	71373	[wan] IPADDR 109.147.50.193
Aug 13 13:52:40	ppp	71373	[wan] IPCP: rec'd Configure Nak #46 (Ack-Sent)
Aug 13 13:52:40	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 13:52:40	ppp	71373	[wan] SECDNS 0.0.0.0
Aug 13 13:52:40	ppp	71373	[wan] PRIDNS 0.0.0.0
Aug 13 13:52:40	ppp	71373	[wan] IPADDR 0.0.0.0
Aug 13 13:52:40	ppp	71373	[wan] IPCP: SendConfigReq #46
Aug 13 13:52:40	ppp	71373	[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Aug 13 13:52:40	ppp	71373	[wan] IPCP: rec'd Configure Reject #45 (Ack-Sent)
Aug 13 13:52:40	ppp	71373	[wan] IPCP: state change Req-Sent --> Ack-Sent
Aug 13 13:52:40	ppp	71373	[wan] IPADDR 172.16.12.102
Aug 13 13:52:40	ppp	71373	[wan] IPCP: SendConfigAck #81
Aug 13 13:52:40	ppp	71373	[wan] 172.16.12.102 is OK
Aug 13 13:52:40	ppp	71373	[wan] IPADDR 172.16.12.102
Aug 13 13:52:40	ppp	71373	[wan] IPCP: rec'd Configure Request #81 (Req-Sent)
Aug 13 13:52:40	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 13:52:40	ppp	71373	[wan] SECDNS 0.0.0.0
Aug 13 13:52:40	ppp	71373	[wan] PRIDNS 0.0.0.0
Aug 13 13:52:40	ppp	71373	[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Aug 13 13:52:40	ppp	71373	[wan] IPADDR 0.0.0.0
Aug 13 13:52:40	ppp	71373	[wan] IPCP: SendConfigReq #45
Aug 13 13:52:40	ppp	71373	[wan] IPCP: state change Starting --> Req-Sent
Aug 13 13:52:40	ppp	71373	[wan] IPCP: Up event
Aug 13 13:52:40	ppp	71373	[wan] IPCP: LayerStart
Aug 13 13:52:40	ppp	71373	[wan] IPCP: state change Initial --> Starting
Aug 13 13:52:40	ppp	71373	[wan] IPCP: Open event
Aug 13 13:52:40	ppp	71373	[wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Aug 13 13:52:40	ppp	71373	[wan_link0] Link: Join bundle "wan"
Aug 13 13:52:40	ppp	71373	[wan_link0] Link: Matched action 'bundle "wan" ""'
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: authorization successful
Aug 13 13:52:40	ppp	71373	[wan_link0] MESG: CHAP authentication success
Aug 13 13:52:40	ppp	71373	[wan_link0] CHAP: rec'd SUCCESS #1 len: 31
Aug 13 13:52:40	ppp	71373	[wan_link0] CHAP: sending RESPONSE #1 len: 52
Aug 13 13:52:40	ppp	71373	[wan_link0] CHAP: Using authname "green-light@service.btclick.com"
Aug 13 13:52:40	ppp	71373	[wan_link0] Name: "acc-aln2.tbs"
Aug 13 13:52:40	ppp	71373	[wan_link0] CHAP: rec'd CHALLENGE #1 len: 60
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: LayerUp
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: auth: peer wants CHAP, I want nothing
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: state change Ack-Sent --> Opened
Aug 13 13:52:40	ppp	71373	[wan_link0] MAGICNUM 0x2128a255
Aug 13 13:52:40	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: rec'd Configure Ack #40 (Ack-Sent)
Aug 13 13:52:40	ppp	71373	[wan_link0] MAGICNUM 0x2128a255
Aug 13 13:52:40	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: SendConfigReq #40
Aug 13 13:52:40	ppp	71373	[wan_link0] PROTOCOMP
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: rec'd Configure Reject #39 (Ack-Sent)
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: state change Req-Sent --> Ack-Sent
Aug 13 13:52:40	ppp	71373	[wan_link0] MAGICNUM 0x04a69d35
Aug 13 13:52:40	ppp	71373	[wan_link0] AUTHPROTO CHAP MD5
Aug 13 13:52:40	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: SendConfigAck #159
Aug 13 13:52:40	ppp	71373	[wan_link0] MAGICNUM 0x04a69d35
Aug 13 13:52:40	ppp	71373	[wan_link0] AUTHPROTO CHAP MD5
Aug 13 13:52:40	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:52:40	ppp	71373	[wan_link0] LCP: rec'd Configure Request #159 (Req-Sent)
Aug 13 13:52:39	ppp	71373	[wan_link0] MAGICNUM 0x2128a255
Aug 13 13:52:39	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:52:39	ppp	71373	[wan_link0] PROTOCOMP
Aug 13 13:52:39	ppp	71373	[wan_link0] LCP: SendConfigReq #39
Aug 13 13:52:39	ppp	71373	[wan_link0] LCP: state change Starting --> Req-Sent
Aug 13 13:52:39	ppp	71373	[wan_link0] LCP: Up event
Aug 13 13:52:39	ppp	71373	[wan_link0] Link: UP event
Aug 13 13:52:39	ppp	71373	[wan_link0] PPPoE: connection successful
Aug 13 13:52:39	ppp	71373	PPPoE: rec'd ACNAME "acc-aln2.tbs"
Aug 13 13:52:33	ppp	71373	[wan_link0] PPPoE: Connecting to ''
Aug 13 13:52:33	ppp	71373	[wan_link0] Link: reconnection attempt 2
Aug 13 13:52:32	ppp	71373	[wan_link0] Link: reconnection attempt 2 in 1 seconds
Aug 13 13:52:32	ppp	71373	[wan_link0] LCP: Down event
Aug 13 13:52:32	ppp	71373	[wan_link0] Link: DOWN event
Aug 13 13:52:32	ppp	71373	[wan_link0] PPPoE connection timeout after 9 seconds
Aug 13 13:52:23	ppp	71373	[wan_link0] PPPoE: Connecting to ''
Aug 13 13:52:23	ppp	71373	[wan_link0] Link: reconnection attempt 1
Aug 13 13:52:21	ppp	71373	[wan_link0] Link: reconnection attempt 1 in 2 seconds
Aug 13 13:52:21	ppp	71373	[wan_link0] LCP: LayerDown
Aug 13 13:52:21	ppp	71373	[wan] Bundle: Last link has gone, no links for bw-manage defined
Aug 13 13:52:21	ppp	71373	[wan] IPCP: state change Closing --> Initial
Aug 13 13:52:21	ppp	71373	[wan] Bundle: No NCPs left. Closing links...
Aug 13 13:52:21	ppp	71373	[wan] IPCP: LayerFinish
Aug 13 13:52:21	ppp	71373	[wan] IPCP: Down event
Aug 13 13:52:21	ppp	71373	[wan] IFACE: Set description "1_WAN"
Aug 13 13:52:21	ppp	71373	[wan] IFACE: Rename interface pppoe0 to pppoe0
Aug 13 13:52:21	ppp	71373	[wan] IFACE: Down event
Aug 13 13:52:21	ppp	71373	[wan] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
Aug 13 13:52:21	ppp	71373	[wan] IPCP: LayerDown
Aug 13 13:52:21	ppp	71373	[wan] IPCP: SendTerminateReq #44
Aug 13 13:52:21	ppp	71373	[wan] IPCP: state change Opened --> Closing
Aug 13 13:52:21	ppp	71373	[wan] IPCP: Close event
Aug 13 13:52:21	ppp	71373	[wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Aug 13 13:52:21	ppp	71373	[wan_link0] Link: Leave bundle "wan"
Aug 13 13:52:21	ppp	71373	[wan_link0] LCP: state change Opened --> Starting
Aug 13 13:52:21	ppp	71373	[wan_link0] LCP: Down event
Aug 13 13:52:21	ppp	71373	[wan_link0] Link: DOWN event
Aug 13 13:52:21	ppp	71373	[wan_link0] PPPoE: connection closed
Aug 13 13:52:16	ppp	71373	[wan_link0] LCP: no reply to 1 echo request(s)
Aug 13 13:21:58	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 13:21:56	ppp	71373	[wan] IFACE: Add description "1_WAN"
Aug 13 13:21:56	ppp	71373	[wan] IFACE: Rename interface ng0 to pppoe0
Aug 13 13:21:56	ppp	71373	[wan] IFACE: Up event
Aug 13 13:21:55	ppp	71373	[wan] 109.147.50.193 -> 172.16.12.102
Aug 13 13:21:55	ppp	71373	[wan] IPCP: LayerUp
Aug 13 13:21:55	ppp	71373	[wan] IPCP: state change Ack-Sent --> Opened
Aug 13 13:21:55	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 13:21:55	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 13:21:55	ppp	71373	[wan] IPADDR 109.147.50.193
Aug 13 13:21:55	ppp	71373	[wan] IPCP: rec'd Configure Ack #43 (Ack-Sent)
Aug 13 13:21:55	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 13:21:55	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 13:21:55	ppp	71373	[wan] IPADDR 109.147.50.193
Aug 13 13:21:55	ppp	71373	[wan] IPCP: SendConfigReq #43
Aug 13 13:21:55	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 13:21:55	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 13:21:55	ppp	71373	[wan] 109.147.50.193 is OK
Aug 13 13:21:55	ppp	71373	[wan] IPADDR 109.147.50.193
Aug 13 13:21:55	ppp	71373	[wan] IPCP: rec'd Configure Nak #42 (Ack-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 13:21:55	ppp	71373	[wan] SECDNS 0.0.0.0
Aug 13 13:21:55	ppp	71373	[wan] PRIDNS 0.0.0.0
Aug 13 13:21:55	ppp	71373	[wan] IPADDR 0.0.0.0
Aug 13 13:21:55	ppp	71373	[wan] IPCP: SendConfigReq #42
Aug 13 13:21:55	ppp	71373	[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Aug 13 13:21:55	ppp	71373	[wan] IPCP: rec'd Configure Reject #41 (Ack-Sent)
Aug 13 13:21:55	ppp	71373	[wan] IPCP: state change Req-Sent --> Ack-Sent
Aug 13 13:21:55	ppp	71373	[wan] IPADDR 172.16.12.102
Aug 13 13:21:55	ppp	71373	[wan] IPCP: SendConfigAck #224
Aug 13 13:21:55	ppp	71373	[wan] 172.16.12.102 is OK
Aug 13 13:21:55	ppp	71373	[wan] IPADDR 172.16.12.102
Aug 13 13:21:55	ppp	71373	[wan] IPCP: rec'd Configure Request #224 (Req-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 13:21:55	ppp	71373	[wan] SECDNS 0.0.0.0
Aug 13 13:21:55	ppp	71373	[wan] PRIDNS 0.0.0.0
Aug 13 13:21:55	ppp	71373	[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Aug 13 13:21:55	ppp	71373	[wan] IPADDR 0.0.0.0
Aug 13 13:21:55	ppp	71373	[wan] IPCP: SendConfigReq #41
Aug 13 13:21:55	ppp	71373	[wan] IPCP: state change Starting --> Req-Sent
Aug 13 13:21:55	ppp	71373	[wan] IPCP: Up event
Aug 13 13:21:55	ppp	71373	[wan] IPCP: LayerStart
Aug 13 13:21:55	ppp	71373	[wan] IPCP: state change Initial --> Starting
Aug 13 13:21:55	ppp	71373	[wan] IPCP: Open event
Aug 13 13:21:55	ppp	71373	[wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Aug 13 13:21:55	ppp	71373	[wan_link0] Link: Join bundle "wan"
Aug 13 13:21:55	ppp	71373	[wan_link0] Link: Matched action 'bundle "wan" ""'
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: authorization successful
Aug 13 13:21:55	ppp	71373	[wan_link0] MESG: CHAP authentication success
Aug 13 13:21:55	ppp	71373	[wan_link0] CHAP: rec'd SUCCESS #1 len: 31
Aug 13 13:21:55	ppp	71373	[wan_link0] CHAP: sending RESPONSE #1 len: 52
Aug 13 13:21:55	ppp	71373	[wan_link0] CHAP: Using authname "green-light@service.btclick.com"
Aug 13 13:21:55	ppp	71373	[wan_link0] Name: "acc-aln2.tbs"
Aug 13 13:21:55	ppp	71373	[wan_link0] CHAP: rec'd CHALLENGE #1 len: 55
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: LayerUp
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: auth: peer wants CHAP, I want nothing
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: state change Ack-Sent --> Opened
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0xfead80b7
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: rec'd Configure Ack #38 (Ack-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0xfead80b7
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: SendConfigReq #38
Aug 13 13:21:55	ppp	71373	[wan_link0] PROTOCOMP
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: rec'd Configure Reject #37 (Ack-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: state change Req-Sent --> Ack-Sent
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0x554ebe8a
Aug 13 13:21:55	ppp	71373	[wan_link0] AUTHPROTO CHAP MD5
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: SendConfigAck #190
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0x554ebe8a
Aug 13 13:21:55	ppp	71373	[wan_link0] AUTHPROTO CHAP MD5
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: rec'd Configure Request #190 (Req-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0xfead80b7
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] PROTOCOMP
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: SendConfigReq #37
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: state change Starting --> Req-Sent
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: Up event
Aug 13 13:21:55	ppp	71373	[wan_link0] Link: UP event
Aug 13 13:21:55	ppp	71373	[wan_link0] PPPoE: connection successful
Aug 13 13:21:55	ppp	71373	PPPoE: rec'd ACNAME "acc-aln2.tbs"
Aug 13 13:21:55	ppp	71373	[wan_link0] PPPoE: Connecting to ''
Aug 13 13:21:55	ppp	71373	[wan_link0] Link: reconnection attempt 2
Aug 13 13:21:53	ppp	71373	[wan_link0] Link: reconnection attempt 2 in 2 seconds
Aug 13 13:21:53	ppp	71373	[wan_link0] LCP: Down event
Aug 13 13:21:53	ppp	71373	[wan_link0] Link: DOWN event
Aug 13 13:21:53	ppp	71373	[wan_link0] PPPoE connection timeout after 9 seconds
Aug 13 13:21:44	ppp	71373	[wan_link0] PPPoE: Connecting to ''
Aug 13 13:21:44	ppp	71373	[wan_link0] Link: reconnection attempt 1
Aug 13 13:21:40	ppp	71373	[wan_link0] Link: reconnection attempt 1 in 4 seconds
Aug 13 13:21:40	ppp	71373	[wan_link0] LCP: LayerDown
Aug 13 13:21:40	ppp	71373	[wan] Bundle: Last link has gone, no links for bw-manage defined
Aug 13 13:21:40	ppp	71373	[wan] IPCP: state change Closing --> Initial
Aug 13 13:21:40	ppp	71373	[wan] Bundle: No NCPs left. Closing links...
Aug 13 13:21:40	ppp	71373	[wan] IPCP: LayerFinish
Aug 13 13:21:40	ppp	71373	[wan] IPCP: Down event
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Set description "1_WAN"
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Rename interface pppoe0 to pppoe0
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Down event
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
Aug 13 13:21:39	ppp	71373	[wan] IPCP: LayerDown
Aug 13 13:21:39	ppp	71373	[wan] IPCP: SendTerminateReq #40
Aug 13 13:21:39	ppp	71373	[wan] IPCP: state change Opened --> Closing
Aug 13 13:21:39	ppp	71373	[wan] IPCP: Close event
Aug 13 13:21:39	ppp	71373	[wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Aug 13 13:21:39	ppp	71373	[wan_link0] Link: Leave bundle "wan"
Aug 13 13:21:39	ppp	71373	[wan_link0] LCP: state change Opened --> Starting
Aug 13 13:21:39	ppp	71373	[wan_link0] LCP: Down event
Aug 13 13:21:39	ppp	71373	[wan_link0] Link: DOWN event
Aug 13 13:21:39	ppp	71373	[wan_link0] PPPoE: connection closed
Aug 13 12:31:49	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 12:31:47	ppp	71373	[wan] IFACE: Add description "1_WAN"
Aug 13 12:31:47	ppp	71373	[wan] IFACE: Rename interface ng0 to pppoe0
Aug 13 12:31:47	ppp	71373	[wan] IFACE: Up event
Aug 13 12:31:46	ppp	71373	[wan] 86.153.138.131 -> 172.16.12.102
Aug 13 12:31:46	ppp	71373	[wan] IPCP: LayerUp
Aug 13 12:31:46	ppp	71373	[wan] IPCP: state change Ack-Sent --> Opened
Aug 13 12:31:46	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 12:31:46	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 12:31:46	ppp	71373	[wan] IPADDR 86.153.138.131
Aug 13 12:31:46	ppp	71373	[wan] IPCP: rec'd Configure Ack #39 (Ack-Sent)
Aug 13 12:31:46	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 12:31:46	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 12:31:46	ppp	71373	[wan] IPADDR 86.153.138.131
Aug 13 12:31:46	ppp	71373	[wan] IPCP: SendConfigReq #39
Aug 13 12:31:46	ppp	71373	[wan] SECDNS 81.139.57.100
Aug 13 12:31:46	ppp	71373	[wan] PRIDNS 81.139.56.100
Aug 13 12:31:46	ppp	71373	[wan] 86.153.138.131 is OK
Aug 13 12:31:46	ppp	71373	[wan] IPADDR 86.153.138.131
Aug 13 12:31:46	ppp	71373	[wan] IPCP: rec'd Configure Nak #38 (Ack-Sent)
Aug 13 12:31:46	ppp	71373	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 13 12:31:46	ppp	71373	[wan] SECDNS 0.0.0.0
Aug 13 12:31:46	ppp	71373	[wan] PRIDNS 0.0.0.0
Aug 13 12:31:46	ppp	71373	[wan] IPADDR 0.0.0.0
Aug 13 12:31:46	ppp	71373	[wan] IPCP: SendConfigReq #38
      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        @diyhouse said in WAN periodically Rebooting:

        Aug 13 13:21:39 ppp 71373 [wan_link0] Link: DOWN event
        Aug 13 13:21:39 ppp 71373 [wan_link0] PPPoE: connection closed

        Well it doesn't appear to be LCP echo requests timing out. In each case the first thing logged is the connection closing. Hmm. Nothing in the main log at that point?

        D 1 Reply Last reply Reply Quote 0
        • D
          diyhouse @stephenw10
          last edited by

          @stephenw10 The Main system=>General Log looks as follows just prior to the connection lost..
          Just in passing what does this mean,

          Aug 13 13:21:40	ppp	71373	[wan] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address

          Thankyou,....
          and main system log:-

          Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: LayerUp
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: auth: peer wants CHAP, I want nothing
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: state change Ack-Sent --> Opened
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0xfead80b7
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: rec'd Configure Ack #38 (Ack-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0xfead80b7
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: SendConfigReq #38
Aug 13 13:21:55	ppp	71373	[wan_link0] PROTOCOMP
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: rec'd Configure Reject #37 (Ack-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: state change Req-Sent --> Ack-Sent
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0x554ebe8a
Aug 13 13:21:55	ppp	71373	[wan_link0] AUTHPROTO CHAP MD5
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: SendConfigAck #190
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0x554ebe8a
Aug 13 13:21:55	ppp	71373	[wan_link0] AUTHPROTO CHAP MD5
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: rec'd Configure Request #190 (Req-Sent)
Aug 13 13:21:55	ppp	71373	[wan_link0] MAGICNUM 0xfead80b7
Aug 13 13:21:55	ppp	71373	[wan_link0] MRU 1492
Aug 13 13:21:55	ppp	71373	[wan_link0] PROTOCOMP
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: SendConfigReq #37
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: state change Starting --> Req-Sent
Aug 13 13:21:55	ppp	71373	[wan_link0] LCP: Up event
Aug 13 13:21:55	ppp	71373	[wan_link0] Link: UP event
Aug 13 13:21:55	ppp	71373	[wan_link0] PPPoE: connection successful
Aug 13 13:21:55	ppp	71373	PPPoE: rec'd ACNAME "acc-aln2.tbs"
Aug 13 13:21:55	ppp	71373	[wan_link0] PPPoE: Connecting to ''
Aug 13 13:21:55	ppp	71373	[wan_link0] Link: reconnection attempt 2
Aug 13 13:21:53	ppp	71373	[wan_link0] Link: reconnection attempt 2 in 2 seconds
Aug 13 13:21:53	ppp	71373	[wan_link0] LCP: Down event
Aug 13 13:21:53	ppp	71373	[wan_link0] Link: DOWN event
Aug 13 13:21:53	ppp	71373	[wan_link0] PPPoE connection timeout after 9 seconds
Aug 13 13:21:44	ppp	71373	[wan_link0] PPPoE: Connecting to ''
Aug 13 13:21:44	ppp	71373	[wan_link0] Link: reconnection attempt 1
Aug 13 13:21:40	ppp	71373	[wan_link0] Link: reconnection attempt 1 in 4 seconds
Aug 13 13:21:40	ppp	71373	[wan_link0] LCP: LayerDown
Aug 13 13:21:40	ppp	71373	[wan] Bundle: Last link has gone, no links for bw-manage defined
Aug 13 13:21:40	ppp	71373	[wan] IPCP: state change Closing --> Initial
Aug 13 13:21:40	ppp	71373	[wan] Bundle: No NCPs left. Closing links...
Aug 13 13:21:40	ppp	71373	[wan] IPCP: LayerFinish
Aug 13 13:21:40	ppp	71373	[wan] IPCP: Down event
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Set description "1_WAN"
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Rename interface pppoe0 to pppoe0
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Down event
Aug 13 13:21:40	ppp	71373	[wan] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
Aug 13 13:21:40	check_reload_status	430	Rewriting resolv.conf
Aug 13 13:21:39	ppp	71373	[wan] IPCP: LayerDown
Aug 13 13:21:39	ppp	71373	[wan] IPCP: SendTerminateReq #40
Aug 13 13:21:39	ppp	71373	[wan] IPCP: state change Opened --> Closing
Aug 13 13:21:39	ppp	71373	[wan] IPCP: Close event
Aug 13 13:21:39	ppp	71373	[wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Aug 13 13:21:39	ppp	71373	[wan_link0] Link: Leave bundle "wan"
Aug 13 13:21:39	ppp	71373	[wan_link0] LCP: state change Opened --> Starting
Aug 13 13:21:39	ppp	71373	[wan_link0] LCP: Down event
Aug 13 13:21:39	ppp	71373	[wan_link0] Link: DOWN event
Aug 13 13:21:39	ppp	71373	[wan_link0] PPPoE: connection closed
Aug 13 13:18:00	sshguard	19745	Now monitoring attacks.
Aug 13 13:18:00	sshguard	9383	Exiting on signal.
Aug 13 13:15:13	php	41056	[pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
Aug 13 13:15:00	php	41056	[pfBlockerNG] Starting cron process.
Aug 13 13:07:00	sshguard	9383	Now monitoring attacks.
Aug 13 13:07:00	sshguard	23133	Exiting on signal.
Aug 13 12:57:00	sshguard	23133	Now monitoring attacks.
          D 1 Reply Last reply Reply Quote 0
          • D
            diyhouse @diyhouse
            last edited by

            @diyhouse Looking in General=> Gateways...
            I get the following errors...
            I don't know if this is a 'red herring',.. but here it is

            Aug 13 13:52:24	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:52:24	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:52:23	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:52:23	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:52:22	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:52:22	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:22:03	dpinger	19013	1_WAN_PPPOE 172.16.12.102: Alarm latency 0us stddev 0us loss 100%
Aug 13 13:22:01	dpinger	19013	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr 172.16.12.102 bind_addr 109.147.50.193 identifier "1_WAN_PPPOE "
Aug 13 13:22:01	dpinger	69150	exiting on signal 15
Aug 13 13:21:55	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:54	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:54	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:53	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:53	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:52	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:52	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:51	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:50	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:50	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:49	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:49	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:48	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:48	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:47	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:47	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:46	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:46	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:45	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:45	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:44	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:44	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:43	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:43	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:21:42	dpinger	69150	1_WAN_PPPOE 172.16.12.102: sendto error: 65
            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Hmm, all that looks like it's caused by the PPPoE connection closing. Really feels like the server is closing it. Might need to turn up the logging to see it which is not something I've ever tried for PPP. Let me see...

              D 1 Reply Last reply Reply Quote 0
              • D
                diyhouse @stephenw10
                last edited by

                @stephenw10
                Stephen,... In desperation,... I have just tried to setup an 'original BT Modem',.. and found the credentials I was using to access the broadband servers,.. were incorrect.!!
                The credentials I have been using for maybe 6yrs+.... are old,..
                Rang BT support,.. and they supplied a completely different set of credentials, which are ( as they say ) in line with my updated line,

                Needless to say I am running with the new line config and credentials on pfsense,.. lets see how this pans out
                upload/ download is now at 60/10,. which is in line with what I recall were the speeds when i 1st went pfsense FTTC....

                So lets see how this pans out,... hopeful,.. but not holding my breath..

                D 1 Reply Last reply Reply Quote 0
                • D
                  diyhouse @diyhouse
                  last edited by

                  @diyhouse
                  Since use of new credentials..1hr 7mins . none of the following error: 65's...in Gateways logs... and PPP is also silent..
                  fingers crossed..

                  Aug 13 13:52:29	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:52:28	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
Aug 13 13:52:28	dpinger	19013	1_WAN_PPPOE 172.16.12.102: sendto error: 65
                  VioletDragonV 1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, well that would be interesting!

                    As far as I know BT don't care what the login is, they use the physical link to authenticate you. Maybe that varies. I use bthomehub@btbroadband.com/1234 and it works fine.

                    I guess we'll see. 🤞

                    D 1 Reply Last reply Reply Quote 0
                    • D
                      diyhouse @stephenw10
                      last edited by

                      @stephenw10
                      Yes indeed,. I transitioned to BT back in 2013,.. ( I've just discovered ),..
                      at this transition point they gave me an account:-

                      green-light@service.btclick.com/Passwd to play with,..

                      which I have used ever since.

                      today they have said I need to use something similiar to :-N025134@hg70.btclick.com/Passwd

                      But as you say we shall see...

                      D 1 Reply Last reply Reply Quote 1
                      • D
                        diyhouse @diyhouse
                        last edited by

                        @diyhouse Update:..
                        Although runnning 'smoother',.. I only seem to be able to get run times on the WAN of around 15hrs...
                        Looking in system=>general log.. filtered by layer down...I have the following... is my issue related to suricata, they seem to occur and each layer down,.. but appreciate could just be a consequence of the WAN failure...

                        Aug 13 05:28:03	ppp	71373	[wan] IPCP: LayerDown
Aug 13 00:24:36	kernel		igb1: link state changed to DOWN
Aug 13 00:24:30	kernel		igb1: link state changed to DOWN
Aug 13 00:23:46	suricata	38573	[100852] <Error> -- error parsing signature "alert tcp $EXTERNAL_NET $HTTP_PORTS -> $HOME_NET any (msg:"MALWARE-OTHER Win.Trojan.Zeus Spam 2013 dated zip/exe HTTP Response - potential malware download"; flow:to_client,established; content:"-2013.zip|0D 0A|"; fast_pattern:only; content:"-2013.zip|0D 0A|"; http_header; content:"-"; within:1; distance:-14; http_header; file_data; content:"-2013.exe"; content:"-"; within:1; distance:-14; metadata:impact_flag red, policy balanced-ips drop, policy max-detect-ips drop, policy security-ips drop, ruleset community, service http; reference:url,www.virustotal.com/en/file/2eff3ee6ac7f5bf85e4ebcbe51974d0708cef666581ef1385c628233614b22c0/analysis/; classtype:trojan-activity; sid:26470; rev:2;)" from file /usr/local/etc/suricata/suricata_41945_igb1/rules/suricata.rules at line 162
Aug 13 00:23:26	php-cgi	21038	[Suricata] ERROR: Snort VRT rules md5 download failed...
Aug 13 00:23:25	php-cgi	21038	[Suricata] Emerging Threats Open rules file update downloaded successfully.
Aug 13 00:23:24	php-cgi	21038	[Suricata] There is a new set of Emerging Threats Open rules posted. Downloading emerging.rules.tar.gz...
Aug 12 19:23:14	ppp	71373	[wan_link0] LCP: LayerDown
Aug 12 19:23:14	ppp	71373	[wan] IPCP: Down event
Aug 12 19:23:14	ppp	71373	[wan] IFACE: Down event
Aug 12 19:23:13	ppp	71373	[wan] IPCP: LayerDown
Aug 12 19:23:13	ppp	71373	[wan_link0] LCP: Down event
Aug 12 19:23:13	ppp	71373	[wan_link0] Link: DOWN event
Aug 12 18:42:07	kernel		igb1: link state changed to DOWN
Aug 12 18:42:01	kernel		igb1: link state changed to DOWN
Aug 12 18:41:14	suricata	67299	[100333] <Error> -- error parsing signature "alert tcp $EXTERNAL_NET $HTTP_PORTS -> $HOME_NET any (msg:"MALWARE-OTHER Win.Trojan.Zeus Spam 2013 dated zip/exe HTTP Response - potential malware download"; flow:to_client,established; content:"-2013.zip|0D 0A|"; fast_pattern:only; content:"-2013.zip|0D 0A|"; http_header; content:"-"; within:1; distance:-14; http_header; file_data; content:"-2013.exe"; content:"-"; within:1; distance:-14; metadata:impact_flag red, policy balanced-ips drop, policy max-detect-ips drop, policy security-ips drop, ruleset community, service http; reference:url,www.virustotal.com/en/file/2eff3ee6ac7f5bf85e4ebcbe51974d0708cef666581ef1385c628233614b22c0/analysis/; classtype:trojan-activity; sid:26470; rev:2;)" from file /usr/local/etc/suricata/suricata_41945_igb1/rules/suricata.rules at line 162
Aug 12 18:40:54	kernel		igb1: link state changed to DOWN
Aug 12 18:37:28	kernel		igb1: link state changed to DOWN
Aug 12 18:37:22	kernel		igb1: link state changed to DOWN
Aug 12 18:36:35	suricata	85777	[100429] <Error> -- error parsing signature "alert tcp $EXTERNAL_NET $HTTP_PORTS -> $HOME_NET any (msg:"MALWARE-OTHER Win.Trojan.Zeus Spam 2013 dated zip/exe HTTP Response - potential malware download"; flow:to_client,established; content:"-2013.zip|0D 0A|"; fast_pattern:only; content:"-2013.zip|0D 0A|"; http_header; content:"-"; within:1; distance:-14; http_header; file_data; content:"-2013.exe"; content:"-"; within:1; distance:-14; metadata:impact_flag red, policy balanced-ips drop, policy max-detect-ips drop, policy security-ips drop, ruleset community, service http; reference:url,www.virustotal.com/en/file/2eff3ee6ac7f5bf85e4ebcbe51974d0708cef666581ef1385c628233614b22c0/analysis/; classtype:trojan-activity; sid:26470; rev:2;)" from file /usr/local/etc/suricata/suricata_41945_igb1/rules/suricata.rules at line 162
Aug 12 18:36:16	kernel		igb1: link state changed to DOWN
Aug 12 18:34:32	shutdown	18862	power-down by root:
Aug 12 18:13:02	ppp	19091	[wan_link0] LCP: Down event
Aug 12 18:13:02	ppp	19091	[wan_link0] Link: DOWN event
                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          That seems more likely to be a symptom rather than a cause. I assume you have Suricata running on LAN there and it's igb1? If it's running in in-line mode that will cause the re-link on igb1 when Suricata reloads. Suricata will be reloaded when the WAN reconnects. It still looks like the WAN disconnecting is the first thing that happens.

                          D 1 Reply Last reply Reply Quote 0
                          • D
                            diyhouse @stephenw10
                            last edited by diyhouse

                            @stephenw10
                            Yes,.. that's what I wondered,. but was not sure,...
                            Thinking about connectivity,.. and stability,... A year or so ago,.. my system would run for months,.. even during power cuts,.. so 100+ day of run time was no issue,..
                            the WAN on the other hand would run for a week or so,.. maybe 3,.. then reboot,... which I took/assumed was BT enforcing their ( you cannot keep the same IP ),..
                            But now I wonder if this was a symptom,.. of the line performance degrading,... as it is now happening more and more,..
                            I was hoping that a 'weekly' WAN reboot would keep 'BT happy',.. and stop them forcing reboots an inopportune moments,.. during the day... but no.
                            The frequency of WAN reboots has over the last several months increased,.. and ( like things that change slowly ) you don't seem to notice the trend..
                            So looking at the big picture as they say,.. I think I need to contact BT support for some 'line performance help'... as things seem to point to line degradation,.. over the last 6+ months... or do you think i'm barking up the wrong tree....
                            pls feel free to disagree

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              Well I've never had that issue. BT only disconnects their end when there's a problem. So I wouldn't expect you to have to reconnect at all.

                              So, yes, it could be some upstream issue. It's odd though that it doesn't just time out. It would be nice to get some logs showing whatever triggers it. Somehow.

                              Ah OK edit the mpd custom conf file you created and uncomment the 'log' line there. If you change it to log +all you will see a lot of logging. Possibly too much!
                              But you should be able enable or disable the options there to get reasonable logging and see what's happening.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                And by a lot I mean it logs every second:

                                Aug 15 22:27:27 	ppp 	4348 	EVENT: Processing timer "BundBm" BundBmTimeout()
Aug 15 22:27:27 	ppp 	4348 	EVENT: Processing event EVENT_TIMEOUT TimerExpires()
Aug 15 22:27:26 	ppp 	4348 	EVENT: Processing event EVENT_TIMEOUT TimerExpires() done
Aug 15 22:27:26 	ppp 	4348 	EVENT: Processing timer "BundBm" BundBmTimeout() done
Aug 15 22:27:26 	ppp 	4348 	EVENT: Registering event EVENT_TIMEOUT TimerExpires() done at timer.c:50
Aug 15 22:27:26 	ppp 	4348 	EVENT: Registering event EVENT_TIMEOUT TimerExpires() at timer.c:50
Aug 15 22:27:26 	ppp 	4348 	EVENT: Starting timer "BundBm" BundBmTimeout() for 1000 ms at bund.c:1678
Aug 15 22:27:26 	ppp 	4348 	[opt4] OUT util: total 6% 0% 1% 0% 1% 36% 1%
Aug 15 22:27:26 	ppp 	4348 	[opt4] IN util: total 18% 0% 1% 0% 1% 103% 3%
Aug 15 22:27:26 	ppp 	4348 	[opt4] 1 1 1 1 1 1
Aug 15 22:27:26 	ppp 	4348 	EVENT: Processing timer "BundBm" BundBmTimeout()
Aug 15 22:27:26 	ppp 	4348 	EVENT: Processing event EVENT_TIMEOUT TimerExpires()
Aug 15 22:27:25 	ppp 	4348 	EVENT: Processing event EVENT_TIMEOUT TimerExpires() done
Aug 15 22:27:25 	ppp 	4348 	EVENT: Processing timer "BundBm" BundBmTimeout() done
Aug 15 22:27:25 	ppp 	4348 	EVENT: Registering event EVENT_TIMEOUT TimerExpires() done at timer.c:50
Aug 15 22:27:25 	ppp 	4348 	EVENT: Registering event EVENT_TIMEOUT TimerExpires() at timer.c:50
Aug 15 22:27:25 	ppp 	4348 	EVENT: Starting timer "BundBm" BundBmTimeout() for 1000 ms at bund.c:1678
Aug 15 22:27:25 	ppp 	4348 	[opt4] OUT util: total 6% 1% 0% 1% 0% 1% 36%
Aug 15 22:27:25 	ppp 	4348 	[opt4] IN util: total 18% 1% 0% 1% 0% 1% 103%
Aug 15 22:27:25 	ppp 	4348 	[opt4] 1 1 1 1 1 1
                                D 1 Reply Last reply Reply Quote 0
                                • D
                                  diyhouse @stephenw10
                                  last edited by

                                  @stephenw10
                                  Tx Stephen,.. File edited,.. and logging enabled... WAN re-started 8:30am

                                  
Aug 16 09:17:24	ppp	9394	EVENT: Processing event EVENT_TIMEOUT TimerExpires() done
Aug 16 09:17:24	ppp	9394	EVENT: Processing timer "BundBm" BundBmTimeout() done
Aug 16 09:17:24	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() done at timer.c:50
Aug 16 09:17:24	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() at timer.c:50
Aug 16 09:17:24	ppp	9394	EVENT: Starting timer "BundBm" BundBmTimeout() for 1000 ms at bund.c:1678
Aug 16 09:17:24	ppp	9394	[wan] OUT util: total 32% 30% 15% 60% 33% 3% 50%
Aug 16 09:17:24	ppp	9394	[wan] IN util: total 207% 11% 5% 1119% 21% 2% 84%
Aug 16 09:17:24	ppp	9394	[wan] 1 1 1 1 1 1
Aug 16 09:17:24	ppp	9394	EVENT: Processing timer "BundBm" BundBmTimeout()
Aug 16 09:17:24	ppp	9394	EVENT: Processing event EVENT_TIMEOUT TimerExpires()
Aug 16 09:17:23	ppp	9394	EVENT: Processing event EVENT_TIMEOUT TimerExpires() done
Aug 16 09:17:23	ppp	9394	EVENT: Processing timer "BundBm" BundBmTimeout() done
Aug 16 09:17:23	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() done at timer.c:50
Aug 16 09:17:23	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() at timer.c:50
Aug 16 09:17:23	ppp	9394	EVENT: Starting timer "BundBm" BundBmTimeout() for 1000 ms at bund.c:1678
Aug 16 09:17:23	ppp	9394	[wan] OUT util: total 25% 6% 30% 15% 60% 33% 3%
Aug 16 09:17:23	ppp	9394	[wan] IN util: total 196% 21% 11% 5% 1119% 21% 2%
Aug 16 09:17:23	ppp	9394	[wan] 1 1 1 1 1 1
                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Nothing else shown? Nothing at 8.30? I imagine there are a massive amount of logs!

                                    D 1 Reply Last reply Reply Quote 0
                                    • D
                                      diyhouse @stephenw10
                                      last edited by

                                      @stephenw10
                                      Yes I had an event at 4:05pm this afternoon,.. unfortunately I was out,.. just got back and extened log length. to 20000 lines,.. and this still only takes me back 15 mins,.. 😊 😊 😊 😁
                                      So will have to wait a little longer... dam

                                      D GertjanG 2 Replies Last reply Reply Quote 0
                                      • D
                                        diyhouse @diyhouse
                                        last edited by

                                        @diyhouse
                                        This is a typical log throughput ATM,...

                                        Aug 16 18:19:03	ppp	9394	[wan] 1 1 1 1 1 1
Aug 16 18:19:03	ppp	9394	EVENT: Processing timer "BundBm" BundBmTimeout()
Aug 16 18:19:03	ppp	9394	EVENT: Processing event EVENT_TIMEOUT TimerExpires()
Aug 16 18:19:02	ppp	9394	EVENT: Processing event EVENT_TIMEOUT TimerExpires() done
Aug 16 18:19:02	ppp	9394	EVENT: Processing timer "BundBm" BundBmTimeout() done
Aug 16 18:19:02	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() done at timer.c:50
Aug 16 18:19:02	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() at timer.c:50
Aug 16 18:19:02	ppp	9394	EVENT: Starting timer "BundBm" BundBmTimeout() for 1000 ms at bund.c:1678
Aug 16 18:19:02	ppp	9394	[wan] OUT util: total 132% 32% 5% 350% 41% 27% 337%
Aug 16 18:19:02	ppp	9394	[wan] IN util: total 8052% 821% 6% 30182% 108% 6% 17191%
Aug 16 18:19:02	ppp	9394	[wan] 1 1 1 1 1 1
Aug 16 18:19:02	ppp	9394	EVENT: Processing timer "BundBm" BundBmTimeout()
Aug 16 18:19:02	ppp	9394	EVENT: Processing event EVENT_TIMEOUT TimerExpires()
Aug 16 18:19:01	ppp	9394	EVENT: Processing event EVENT_TIMEOUT TimerExpires() done
Aug 16 18:19:01	ppp	9394	EVENT: Processing timer "BundBm" BundBmTimeout() done
Aug 16 18:19:01	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() done at timer.c:50
Aug 16 18:19:01	ppp	9394	EVENT: Registering event EVENT_TIMEOUT TimerExpires() at timer.c:50
Aug 16 18:19:01	ppp	9394	EVENT: Starting timer "BundBm" BundBmTimeout() for 1000 ms at bund.c:1678
Aug 16 18:19:01	ppp	9394	[wan] OUT util: total 82% 37% 32% 5% 350% 41% 27%
Aug 16 18:19:01	ppp	9394	[wan] IN util: total 5191% 26% 821% 6% 30182% 108% 6%
Aug 16 18:19:01	ppp	9394	[wan] 1 1 1 1 1 1
                                        1 Reply Last reply Reply Quote 0
                                        • stephenw10S
                                          stephenw10 Netgate Administrator
                                          last edited by

                                          Yeah +all is probably more than you need. You should be able to enable those things individually. Though I'm not sure which one you would need.

                                          1 Reply Last reply Reply Quote 0
                                          • GertjanG
                                            Gertjan @diyhouse
                                            last edited by

                                            @diyhouse said in WAN periodically Rebooting:

                                            and this still only takes me back 15 mins

                                            IF you have some disk space left, you could goto Status > System Logs > Settings and make the log files (way) bigger :

                                            fceb8876-8bba-498b-8943-f0ad79ba7e23-image.png

                                            No "help me" PM's please. Use the forum, the community will thank you.
                                            Edit : and where are the logs ??

                                            D 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.