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

    WAN periodically Rebooting

    Scheduled Pinned Locked Moved
    General pfSense Questions
    5
    175
    6.4k
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Some of those older HG612s have seen a lot of hours and become unreliable. I have two waiting to be recycled here.

      BT bouncing the connection (PPPoE) should not cause a loss of link on the NIC connected to the modem. So filter the logs for: link state changed

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

        @stephenw10 Many tx for replies,.. How do I search for 'link state changed',..
        I am in the status > system logs,...
        I do not see any search option from the top level list of :- system, firewall, DHCP, Authentication, IPSEC, PPP,.. etc..

        Yes my HG612 has served me well,.. and yes it does run hot sometimes,.. is anyone able to offer suggestions on a good replacement,.. as I do feel a little vulnerable as I have no replacement for the Modem... my provider is BT, with a standard FTTC,.. 72Mbit type copper connection,.. ie NOT FTTP..
        Tx

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

          @Gertjan said in WAN periodically Rebooting:
          Many tx for your replay,...

          Start by putting a simple switch between your pfSense and the modem.

          How exactly do you mean,.. something that will enable to power cycle the modem???

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

            The ECI equivalent modem is often more reliable. The HG612 is usually better if the upstream equipment in the cab is Huawei.

            The g.fast modems (MT992) that were very expensive at one time are now cheap as BT stopped rolling out g.fast. Don't ask how much I paid for one! 🙄
            They will do standard VDSL2 too and seem pretty good. Never had an issue with the one I have.

            Search the logs like this:
            Screenshot from 2024-07-30 15-14-31.png

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

              @stephenw10 Got-it,.. Never got to that menu before,. Thankyou..
              I get the following:-

              Jul 30 00:24:34 kernel igb1: link state changed to UP
              Jul 30 00:24:30 kernel igb1: link state changed to DOWN
              Jul 30 00:24:29 kernel igb1: link state changed to UP
              Jul 30 00:24:24 kernel igb1: link state changed to DOWN

              and I have 24 events, 12 ( up-down ) cycles at 24 seconds past midnight..
              although WAN 'last reset' just over 12:38hrs ago which does not correlate time wise with these event,.. which occured 15:38hrs ago

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

                @diyhouse said in WAN periodically Rebooting:

                and I have 24 events, 12 ( up-down ) cycles at 24 seconds past midnight..

                All from the same day or are you saying the NIC bounces everyday at the same?

                Also I assume igb1 is actually the parent interface for the PPPOe connection?

                It's possible to unlock those modems which then gives you access to useful data such as uptime which would tell you if the modem is rebooting:

                Product type 	EchoLife HG612  
Device ID 	10C61F-21530315408K23024294
Hardware version 	VER.B
Software version 	V100R001C01B030SP08
Firmware version 	A2pv6C038m.d24j
Batch number 	BC1P6.030.A2pv6C038m.d24j
System up time 	231 days 10 hours 23 minutes 50 seconds

                The MT992 cannot be accessed unfortunately. 😞

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

                  @stephenw10 said in WAN periodically Rebooting:

                  Also I assume igb1 is actually the parent interface for the PPPOe connection?

                  Humm,.. just checked,.. No,.. PPPOe is on igb0,..
                  and LAN1 is on igb1,.. which connects to a single 8port netgear switch...
                  Not saying this happens every night at just gone midnight,.. its just the last events it filtered...

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

                    Ah, OK well if there are no events for igb0 then the modem is not rebooting.

                    Filtering by newwanip should show you every time the PPPoE reconnected.

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

                      @stephenw10
                      Ah yes that filter finds the events

                      Aug 1 13:15:52	php-fpm	88740	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 109.151.224.138 -> 109.151.224.138 - Restarting packages.
Aug 1 13:15:50	php-fpm	88740	/rc.newwanip: Creating rrd update script
Aug 1 13:15:50	php-fpm	88740	/rc.newwanip: Resyncing OpenVPN instances for interface 1_WAN.
Aug 1 13:15:50	php-fpm	88740	/rc.newwanip: Gateway, none 'available' for inet6, use the first one configured. 'LAN1_DHCP6'
Aug 1 13:15:50	php-fpm	88740	/rc.newwanip: Default gateway setting Interface 1_WAN_PPPOE Gateway as default.
Aug 1 13:15:50	php-fpm	88740	/rc.newwanip: Gateway, none 'available' for inet, use the first one configured. '1_WAN_PPPOE'
Aug 1 13:15:45	php-fpm	88740	/rc.newwanip: rc.newwanip: on (IP address: 109.151.224.138) (interface: 1_WAN[wan]) (real interface: pppoe0).
Aug 1 13:15:45	php-fpm	88740	/rc.newwanip: rc.newwanip: Info: starting on pppoe0.
Aug 1 13:15:44	check_reload_status	430	rc.newwanip starting pppoe0
Jul 31 02:31:41	php-fpm	34142	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 109.145.193.70 -> 109.151.224.138 - Restarting packages.
Jul 31 02:31:39	php-fpm	34142	/rc.newwanip: Creating rrd update script
Jul 31 02:31:39	php-fpm	34142	/rc.newwanip: Resyncing OpenVPN instances for interface 1_WAN.
Jul 31 02:31:39	php-fpm	34142	/rc.newwanip: IP Address has changed, killing states on former IP Address 109.145.193.70.
Jul 31 02:31:39	php-fpm	34142	/rc.newwanip: Gateway, none 'available' for inet6, use the first one configured. 'LAN1_DHCP6'
Jul 31 02:31:39	php-fpm	34142	/rc.newwanip: Default gateway setting Interface 1_WAN_PPPOE Gateway as default.
Jul 31 02:31:39	php-fpm	34142	/rc.newwanip: Gateway, none 'available' for inet, use the first one configured. '1_WAN_PPPOE'
Jul 31 02:31:33	php-fpm	34142	/rc.newwanip: rc.newwanip: on (IP address: 109.151.224.138) (interface: 1_WAN[wan]) (real interface: pppoe0).
Jul 31 02:31:33	php-fpm	34142	/rc.newwanip: rc.newwanip: Info: starting on pppoe0.
Jul 31 02:31:32	check_reload_status	430	rc.newwanip starting pppoe0

                      Although looking deeper at 'link state changed',..
                      This event,.. seems to occur every morning at 24seconds + or - past midnight,.. and lasts approx 4 or 5 seconds... but not sure how this is related...

                      
Aug 2 00:24:12	kernel		igb1: link state changed to UP
Aug 2 00:24:08	kernel		igb1: link state changed to DOWN
                      D stephenw10S 2 Replies Last reply Reply Quote 0
                      • D
                        diyhouse @diyhouse
                        last edited by

                        @diyhouse
                        also,.. the MT992
                        @stephenw10 said in WAN periodically Rebooting:

                        The g.fast modems (MT992) that were very expensive at one time are now cheap as BT stopped rolling out g.fast. Don't ask how much I paid for one!
                        They will do standard VDSL2 too and seem pretty good. Never had an issue with the one I have.
                        Tx for the suggestion,..

                        Do they need a firmware update like the 612 did?,.. or is this really just PnP...
                        Seems like a good option,.. and at £20,.. just as easy to try one, in the fault finding exercise..
                        Thankyou for the help advice

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

                          @diyhouse
                          Just looking at log more,.. and using the filter,.. :-) ( love it )
                          It seems to happen quite a lot,.. sometimes twice a day,... but what causes this,.. is this 'me' or a BT driven event?

                          Aug 1 13:15:44	check_reload_status	430	rc.newwanip starting pppoe0
Jul 31 02:31:32	check_reload_status	430	rc.newwanip starting pppoe0
Jul 31 02:23:55	check_reload_status	430	rc.newwanip starting pppoe0
Jul 31 02:19:56	check_reload_status	430	rc.newwanip starting pppoe0
Jul 31 01:19:43	check_reload_status	430	rc.newwanip starting pppoe0
Jul 30 19:59:49	check_reload_status	430	rc.newwanip starting pppoe0
Jul 30 02:56:35	check_reload_status	430	rc.newwanip starting pppoe0
Jul 29 22:41:06	check_reload_status	430	rc.newwanip starting pppoe0
Jul 29 20:33:10	check_reload_status	430	rc.newwanip starting pppoe0
Jul 29 05:27:56	check_reload_status	430	rc.newwanip starting pppoe0
Jul 28 21:00:39	check_reload_status	430	rc.newwanip starting pppoe0
Jul 28 18:36:59	check_reload_status	430	rc.newwanip starting pppoe0
Jul 28 00:00:05	check_reload_status	430	rc.newwanip starting pppoe0
Jul 27 01:57:13	check_reload_status	430	rc.newwanip starting pppoe0
Jul 26 02:07:46	check_reload_status	430	rc.newwanip starting pppoe0
Jul 25 22:41:01	check_reload_status	430	rc.newwanip starting pppoe0
Jul 25 21:53:02	check_reload_status	430	rc.newwanip starting pppoe0
Jul 25 14:49:49	check_reload_status	430	rc.newwanip starting pppoe0
Jul 25 14:41:52	check_reload_status	430	rc.newwanip starting pppoe0
Jul 25 14:38:56	check_reload_status	430	rc.newwanip starting pppoe0
Jul 25 14:36:25	check_reload_status	430	rc.newwanip starting pppoe0
Jul 24 22:51:35	check_reload_status	430	rc.newwanip starting pppoe0
Jul 24 14:23:00	check_reload_status	430	rc.newwanip starting pppoe0
Jul 24 10:58:26	check_reload_status	430	rc.newwanip starting pppoe0
Jul 24 10:21:06	check_reload_status	430	rc.newwanip starting pppoe0
Jul 22 21:54:20	check_reload_status	430	rc.newwanip starting pppoe0
Jul 22 19:41:35	check_reload_status	430	rc.newwanip starting pppoe0
Jul 22 19:36:55	check_reload_status	430	rc.newwanip starting pppoe0
Jul 22 19:13:09	check_reload_status	430	rc.newwanip starting pppoe0
Jul 22 18:55:55	check_reload_status	430	rc.newwanip starting pppoe0
Jul 22 18:53:17	check_reload_status	430	rc.newwanip starting pppoe0
Jul 22 18:19:39	check_reload_status	430	rc.newwanip starting pppoe0
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator @diyhouse
                            last edited by

                            @diyhouse said in WAN periodically Rebooting:

                            Although looking deeper at 'link state changed',..
                            This event,.. seems to occur every morning at 24seconds + or - past midnight,.. and lasts approx 4 or 5 seconds... but not sure how this is related...

                            That seems suspicious. What is that connected to? Is that device resetting?
                            That interface flapping will trigger a bunch of stuff even if it's not the WAN.

                            @diyhouse said in WAN periodically Rebooting:

                            Do they need a firmware update like the 612 did?,.. or is this really just PnP...

                            I've never seen a firmware update but they don't have a user accessible interface either. AFAIK is really is PNP. There was another user here testing it if I could fine it. At one time those were all >£200!

                            @diyhouse said in WAN periodically Rebooting:

                            It seems to happen quite a lot,.. sometimes twice a day,... but what causes this,.. is this 'me' or a BT driven event?

                            Check the ppp logs. It should show what drove the disconnect event. It's usually the remote side.
                            For example this is something local closing it:

                            Jul 29 19:17:41 	ppp 	41282 	caught fatal signal TERM
Jul 29 19:17:41 	ppp 	41282 	[opt4] IFACE: Close event
Jul 29 19:17:41 	ppp 	41282 	[opt4] IPCP: Close event
Jul 29 19:17:41 	ppp 	41282 	[opt4] IPCP: state change Opened --> Closing
Jul 29 19:17:41 	ppp 	41282 	[opt4] IPCP: SendTerminateReq #4
Jul 29 19:17:41 	ppp 	41282 	[opt4] IPCP: LayerDown

                            This is some upstream problem:

                            Nov 23 08:19:16 	ppp 	14046 	[opt4_link0] LCP: no reply to 5 echo request(s)
Nov 23 08:19:16 	ppp 	14046 	[opt4_link0] LCP: peer not responding to echo requests
Nov 23 08:19:16 	ppp 	14046 	[opt4_link0] LCP: state change Opened --> Stopping
Nov 23 08:19:16 	ppp 	14046 	[opt4_link0] Link: Leave bundle "opt4"
Nov 23 08:19:16 	ppp 	14046 	[opt4] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Nov 23 08:19:16 	ppp 	14046 	[opt4] IPCP: Close event

                            Note I had to go back to November to find one. 😉

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

                              @stephenw10 said in WAN periodically Rebooting:
                              Looking into logs around 13:15 today,.. things look like this,
                              where there are many things happening,.. none of which look good, WAN failing up down layerup etc etc.. even to my untrained eye,.. but I hope will mean something to a 'trained eye of pfsense,..
                              ..Back to November,.. do you have a fixed IP,.. and are you maybe with another provider ( Not BT),.. as my last reboot, was intentional some 110days ago,.. any other 'house failures' as long as there less than 10hrs do not cause an issue... ( as Big battery on UPS )
                              I seek your advice,.. etc ,.. should I just buy an MT992? and replace modem?
                              Many Tx

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

                                Well the modem is not losing link to pfSense so it's not rebooting.

                                Those logs show it stops seeing responses from upstream but not the count of 5 missed replies that would trigger a reconnect. However the connection is them promptly closed which implies something was sent from upstream. If so a different modem might not make any difference.

                                However given the age of the HG612 I would probably try replacing it. An MT992 is likely to be better at using the available line conditions anyway.
                                What sort of connections speeds do you get?

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

                                  @stephenw10
                                  Well using webtool 'speedtest',.. I get 40Mbps download, ( I am surprised ) and 15Mps up,.. with a ping of 15ms. No other traffic as far as I can see,.. but who knows what is up stream. at 9PM at night

                                  Now many moons ago when I 1st setup pfsense I seem to recall getting 56Mbps,.. and prob 20Mbps Up,..

                                  compared to 72Mbps the the offical BT, Modem,.. but I was happy with '56',.. as the 72 was only BT reporting on itself,...

                                  Having 'lost' 16Mbps download,.. something would seem to be Off,...
                                  .... off to order MT992....

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

                                    @diyhouse MT992 order,.. brand new one!!,.. just no power block,..
                                    But have spare for old one if required,.. and I supply it from a UPS anyway...
                                    So should be good for a few years,.. of 24/7 running.
                                    Thinking about it the HG612 must have been running for 3 or 4 yrs,.. solid,.. and it does sometimes run warm, especially during hot summers,.. like ATM in the UK.. 40C ambient in loft, (must find invoice to see how long),.. Hummm

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

                                      Could also be your line conditions have deteriorated. The unlocked HG612 gives nice stats for that:

                                      Screenshot from 2024-08-02 21-40-50.png

                                      It really is a shame the MT992 is locked down. I'm sure all that data is in there.

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

                                        @stephenw10
                                        Hi Steve,.. My new MT992 has just arrived,... minus power supply as stated before,,,.
                                        Just covering the 'idiot guide question',.. supply requirements 12v @1amp,... I ASSUME,... centre pin is plus,.. and barrel outer is -Ve... as per normal convention,.. as it does not state on MT992...
                                        Many Tx

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

                                          Yup I assume so. I used the same battery backup unit I was using with the HG612. (So, yes, it must be!)

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

                                            @stephenw10 Hi Stephen,.. well MT992 installed... and although speed test seems to have some improvements ( but this could just be time of day etc ), ..'uptime' on the other hand does not seem to be much better,... as my 1st disconnect occurred 50mins after 1st boot and connect of modem,.. logs as follows

                                            I see at 13:59:51 connection is lost,.. but how do I see what caused the the event...?
                                            Many Tx

                                            Aug 12 14:15:17	php	31129	[pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
Aug 12 14:15:00	php	31129	[pfBlockerNG] Starting cron process.
Aug 12 14:15:00	sshguard	32443	Now monitoring attacks.
Aug 12 14:15:00	sshguard	54598	Exiting on signal.
Aug 12 14:06:00	sshguard	54598	Now monitoring attacks.
Aug 12 14:06:00	sshguard	28085	Exiting on signal.
Aug 12 14:04:00	sshguard	28085	Now monitoring attacks.
Aug 12 14:04:00	sshguard	94791	Exiting on signal.
Aug 12 14:01:00	sshguard	94791	Now monitoring attacks.
Aug 12 14:01:00	sshguard	18557	Exiting on signal.
Aug 12 14:00:56	ppp	19091	[wan_link0] LCP: no reply to 2 echo request(s)
Aug 12 14:00:46	ppp	19091	[wan_link0] LCP: no reply to 1 echo request(s)
Aug 12 14:00:30	php_pfb	85217	[pfBlockerNG] filterlog daemon started
Aug 12 14:00:30	php	84813	[pfBlockerNG] DNSBL parser daemon started
Aug 12 14:00:29	vnstatd	85867	Error: pidfile "/var/run/vnstat/vnstat.pid" lock failed (Resource temporarily unavailable), exiting.
Aug 12 14:00:29	vnstatd	81408	Monitoring (11): pppoe0 (1000 Mbit) pfsync0 (1000 Mbit) pflog0 (1000 Mbit) igb3.30 (1000 Mbit) igb3.20 (1000 Mbit) igb3.10 (1000 Mbit) igb3 (1000 Mbit) igb2 (10 Mbit) igb1 (1000 Mbit) igb0 (1000 Mbit) enc0 (1000 Mbit)
Aug 12 14:00:29	vnstatd	81408	Data retention: 48 5MinuteHours, 4 HourlyDays, 62 DailyDays, 25 MonthlyMonths, -1 YearlyYears, 20 TopDayEntries
Aug 12 14:00:29	vnstatd	81408	vnStat daemon 2.11 (pid:81408 uid:0 gid:0, SQLite 3.43.1)
Aug 12 14:00:29	tail_pfb	84427	[pfBlockerNG] Firewall Filter Service started
Aug 12 14:00:29	lighttpd_pfb	81906	[pfBlockerNG] DNSBL Webserver started
Aug 12 14:00:29	php_pfb	80281	[pfBlockerNG] filterlog daemon stopped
Aug 12 14:00:29	tail_pfb	78860	[pfBlockerNG] Firewall Filter Service stopped
Aug 12 14:00:29	lighttpd_pfb	77070	[pfBlockerNG] DNSBL Webserver stopped
Aug 12 14:00:29	vnstatd	22588	SIGTERM received, exiting.
Aug 12 14:00:19	vnstatd	49205	Error: pidfile "/var/run/vnstat/vnstat.pid" lock failed (Resource temporarily unavailable), exiting.
Aug 12 14:00:19	bandwidthd	49002	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	48834	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	49002	Opening igb1
Aug 12 14:00:19	bandwidthd	48764	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	48834	Opening igb1
Aug 12 14:00:19	bandwidthd	49176	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	49176	Opening igb1
Aug 12 14:00:19	bandwidthd	48764	Opening igb1
Aug 12 14:00:19	bandwidthd	48227	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	48227	Opening igb1
Aug 12 14:00:19	bandwidthd	48477	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	47880	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	48649	Packet Encoding: Ethernet
Aug 12 14:00:19	bandwidthd	48477	Opening igb1
Aug 12 14:00:19	bandwidthd	48649	Opening igb1
Aug 12 14:00:19	bandwidthd	47880	Opening igb1
Aug 12 14:00:19	bandwidthd	46528	Monitoring subnet 192.168.3.0 with netmask 255.255.255.0
Aug 12 14:00:19	bandwidthd	46381	Monitoring subnet 192.168.3.0 with netmask 255.255.255.0
Aug 12 14:00:19	php-fpm	18605	/rc.start_packages: The command '/usr/local/etc/rc.d/bandwidthd.sh stop' returned exit code '1', the output was 'killall: warning: kill -TERM 63951: No such process killall: warning: kill -TERM 65017: No such process'
Aug 12 14:00:18	php-fpm	18605	/rc.start_packages: Restarting/Starting all packages.
Aug 12 14:00:17	check_reload_status	430	Reloading filter
Aug 12 14:00:17	check_reload_status	430	Starting packages
Aug 12 14:00:17	php-fpm	88053	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 86.146.217.76 -> 86.168.50.162 - Restarting packages.
Aug 12 14:00:16	php-fpm	62823	/rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. 'LAN1_DHCP6'
Aug 12 14:00:16	php-fpm	62823	/rc.openvpn: Gateway, none 'available' for inet, use the first one configured. '1_WAN_PPPOE'
Aug 12 14:00:14	php-fpm	88053	/rc.newwanip: Creating rrd update script
Aug 12 14:00:14	php-fpm	88053	/rc.newwanip: Resyncing OpenVPN instances for interface 1_WAN.
Aug 12 14:00:14	php-fpm	88053	/rc.newwanip: IP Address has changed, killing states on former IP Address 86.146.217.76.
Aug 12 14:00:14	php-fpm	88053	/rc.newwanip: Gateway, none 'available' for inet6, use the first one configured. 'LAN1_DHCP6'
Aug 12 14:00:14	check_reload_status	430	Reloading filter
Aug 12 14:00:14	check_reload_status	430	Restarting OpenVPN tunnels/interfaces
Aug 12 14:00:14	check_reload_status	430	Restarting IPsec tunnels
Aug 12 14:00:14	check_reload_status	430	updating dyndns 1_WAN_PPPOE
Aug 12 14:00:14	php-fpm	88053	/rc.newwanip: Default gateway setting Interface 1_WAN_PPPOE Gateway as default.
Aug 12 14:00:14	rc.gateway_alarm	42980	>>> Gateway alarm: 1_WAN_PPPOE (Addr:172.16.12.102 Alarm:1 RTT:0ms RTTsd:0ms Loss:100%)
Aug 12 14:00:14	php-fpm	88053	/rc.newwanip: Gateway, none 'available' for inet, use the first one configured. '1_WAN_PPPOE'
Aug 12 14:00:09	ppp	19091	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 12 14:00:08	php-fpm	88053	/rc.newwanip: rc.newwanip: on (IP address: 86.168.50.162) (interface: 1_WAN[wan]) (real interface: pppoe0).
Aug 12 14:00:08	php-fpm	88053	/rc.newwanip: rc.newwanip: Info: starting on pppoe0.
Aug 12 14:00:07	ppp	19091	[wan] IFACE: Add description "1_WAN"
Aug 12 14:00:07	ppp	19091	[wan] IFACE: Rename interface ng0 to pppoe0
Aug 12 14:00:07	ppp	19091	[wan] IFACE: Up event
Aug 12 14:00:07	check_reload_status	430	rc.newwanip starting pppoe0
Aug 12 14:00:06	check_reload_status	430	Rewriting resolv.conf
Aug 12 14:00:06	ppp	19091	[wan] 86.168.50.162 -> 172.16.12.102
Aug 12 14:00:06	ppp	19091	[wan] IPCP: LayerUp
Aug 12 14:00:06	ppp	19091	[wan] IPCP: state change Ack-Sent --> Opened
Aug 12 14:00:06	ppp	19091	[wan] SECDNS 81.139.57.100
Aug 12 14:00:06	ppp	19091	[wan] PRIDNS 81.139.56.100
Aug 12 14:00:06	ppp	19091	[wan] IPADDR 86.168.50.162
Aug 12 14:00:06	ppp	19091	[wan] IPCP: rec'd Configure Ack #7 (Ack-Sent)
Aug 12 14:00:06	ppp	19091	[wan] SECDNS 81.139.57.100
Aug 12 14:00:06	ppp	19091	[wan] PRIDNS 81.139.56.100
Aug 12 14:00:06	ppp	19091	[wan] IPADDR 86.168.50.162
Aug 12 14:00:06	ppp	19091	[wan] IPCP: SendConfigReq #7
Aug 12 14:00:06	ppp	19091	[wan] SECDNS 81.139.57.100
Aug 12 14:00:06	ppp	19091	[wan] PRIDNS 81.139.56.100
Aug 12 14:00:06	ppp	19091	[wan] 86.168.50.162 is OK
Aug 12 14:00:06	ppp	19091	[wan] IPADDR 86.168.50.162
Aug 12 14:00:06	ppp	19091	[wan] IPCP: rec'd Configure Nak #6 (Ack-Sent)
Aug 12 14:00:06	ppp	19091	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 12 14:00:06	ppp	19091	[wan] SECDNS 0.0.0.0
Aug 12 14:00:06	ppp	19091	[wan] PRIDNS 0.0.0.0
Aug 12 14:00:06	ppp	19091	[wan] IPADDR 0.0.0.0
Aug 12 14:00:06	ppp	19091	[wan] IPCP: SendConfigReq #6
Aug 12 14:00:06	ppp	19091	[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Aug 12 14:00:06	ppp	19091	[wan] IPCP: rec'd Configure Reject #5 (Ack-Sent)
Aug 12 14:00:06	ppp	19091	[wan] IPCP: state change Req-Sent --> Ack-Sent
Aug 12 14:00:06	ppp	19091	[wan] IPADDR 172.16.12.102
Aug 12 14:00:06	ppp	19091	[wan] IPCP: SendConfigAck #187
Aug 12 14:00:06	ppp	19091	[wan] 172.16.12.102 is OK
Aug 12 14:00:06	ppp	19091	[wan] IPADDR 172.16.12.102
Aug 12 14:00:06	ppp	19091	[wan] IPCP: rec'd Configure Request #187 (Req-Sent)
Aug 12 14:00:06	ppp	19091	[wan_link0] rec'd unexpected protocol IPV6CP, rejecting
Aug 12 14:00:06	ppp	19091	[wan] SECDNS 0.0.0.0
Aug 12 14:00:06	ppp	19091	[wan] PRIDNS 0.0.0.0
Aug 12 14:00:06	ppp	19091	[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Aug 12 14:00:06	ppp	19091	[wan] IPADDR 0.0.0.0
Aug 12 14:00:06	ppp	19091	[wan] IPCP: SendConfigReq #5
Aug 12 14:00:06	ppp	19091	[wan] IPCP: state change Starting --> Req-Sent
Aug 12 14:00:06	ppp	19091	[wan] IPCP: Up event
Aug 12 14:00:06	ppp	19091	[wan] IPCP: LayerStart
Aug 12 14:00:06	ppp	19091	[wan] IPCP: state change Initial --> Starting
Aug 12 14:00:06	ppp	19091	[wan] IPCP: Open event
Aug 12 14:00:06	ppp	19091	[wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Aug 12 14:00:06	ppp	19091	[wan_link0] Link: Join bundle "wan"
Aug 12 14:00:06	ppp	19091	[wan_link0] Link: Matched action 'bundle "wan" ""'
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: authorization successful
Aug 12 14:00:06	ppp	19091	[wan_link0] MESG: CHAP authentication success
Aug 12 14:00:06	ppp	19091	[wan_link0] CHAP: rec'd SUCCESS #1 len: 31
Aug 12 14:00:06	ppp	19091	[wan_link0] CHAP: sending RESPONSE #1 len: 52
Aug 12 14:00:06	ppp	19091	[wan_link0] CHAP: Using authname "green-light@service.btclick.com"
Aug 12 14:00:06	ppp	19091	[wan_link0] Name: "acc-aln2.tbs"
Aug 12 14:00:06	ppp	19091	[wan_link0] CHAP: rec'd CHALLENGE #1 len: 59
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: LayerUp
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: auth: peer wants CHAP, I want nothing
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: state change Ack-Sent --> Opened
Aug 12 14:00:06	ppp	19091	[wan_link0] MAGICNUM 0x53da0584
Aug 12 14:00:06	ppp	19091	[wan_link0] MRU 1492
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: rec'd Configure Ack #4 (Ack-Sent)
Aug 12 14:00:06	ppp	19091	[wan_link0] MAGICNUM 0x53da0584
Aug 12 14:00:06	ppp	19091	[wan_link0] MRU 1492
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: SendConfigReq #4
Aug 12 14:00:06	ppp	19091	[wan_link0] PROTOCOMP
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: rec'd Configure Reject #3 (Ack-Sent)
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: state change Req-Sent --> Ack-Sent
Aug 12 14:00:06	ppp	19091	[wan_link0] MAGICNUM 0x4fd3fb4b
Aug 12 14:00:06	ppp	19091	[wan_link0] AUTHPROTO CHAP MD5
Aug 12 14:00:06	ppp	19091	[wan_link0] MRU 1492
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: SendConfigAck #58
Aug 12 14:00:06	ppp	19091	[wan_link0] MAGICNUM 0x4fd3fb4b
Aug 12 14:00:06	ppp	19091	[wan_link0] AUTHPROTO CHAP MD5
Aug 12 14:00:06	ppp	19091	[wan_link0] MRU 1492
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: rec'd Configure Request #58 (Req-Sent)
Aug 12 14:00:06	ppp	19091	[wan_link0] MAGICNUM 0x53da0584
Aug 12 14:00:06	ppp	19091	[wan_link0] MRU 1492
Aug 12 14:00:06	ppp	19091	[wan_link0] PROTOCOMP
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: SendConfigReq #3
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: state change Starting --> Req-Sent
Aug 12 14:00:06	ppp	19091	[wan_link0] LCP: Up event
Aug 12 14:00:06	ppp	19091	[wan_link0] Link: UP event
Aug 12 14:00:06	ppp	19091	[wan_link0] PPPoE: connection successful
Aug 12 14:00:06	ppp	19091	PPPoE: rec'd ACNAME "acc-aln2.tbs"
Aug 12 14:00:06	ppp	19091	[wan_link0] PPPoE: Connecting to ''
Aug 12 14:00:06	ppp	19091	[wan_link0] Link: reconnection attempt 2
Aug 12 14:00:05	ppp	19091	[wan_link0] Link: reconnection attempt 2 in 1 seconds
Aug 12 14:00:05	ppp	19091	[wan_link0] LCP: Down event
Aug 12 14:00:05	ppp	19091	[wan_link0] Link: DOWN event
Aug 12 14:00:05	ppp	19091	[wan_link0] PPPoE connection timeout after 9 seconds
Aug 12 13:59:56	ppp	19091	[wan_link0] PPPoE: Connecting to ''
Aug 12 13:59:56	ppp	19091	[wan_link0] Link: reconnection attempt 1
Aug 12 13:59:52	ppp	19091	[wan_link0] Link: reconnection attempt 1 in 4 seconds
Aug 12 13:59:52	ppp	19091	[wan_link0] LCP: LayerDown
Aug 12 13:59:52	ppp	19091	[wan] Bundle: Last link has gone, no links for bw-manage defined
Aug 12 13:59:52	ppp	19091	[wan] IPCP: state change Closing --> Initial
Aug 12 13:59:52	ppp	19091	[wan] Bundle: No NCPs left. Closing links...
Aug 12 13:59:52	ppp	19091	[wan] IPCP: LayerFinish
Aug 12 13:59:52	ppp	19091	[wan] IPCP: Down event
Aug 12 13:59:52	ppp	19091	[wan] IFACE: Set description "1_WAN"
Aug 12 13:59:52	ppp	19091	[wan] IFACE: Rename interface pppoe0 to pppoe0
Aug 12 13:59:52	ppp	19091	[wan] IFACE: Down event
Aug 12 13:59:52	ppp	19091	[wan] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
Aug 12 13:59:52	check_reload_status	430	Rewriting resolv.conf
Aug 12 13:59:51	ppp	19091	[wan] IPCP: LayerDown
Aug 12 13:59:51	ppp	19091	[wan] IPCP: SendTerminateReq #4
Aug 12 13:59:51	ppp	19091	[wan] IPCP: state change Opened --> Closing
Aug 12 13:59:51	ppp	19091	[wan] IPCP: Close event
Aug 12 13:59:51	ppp	19091	[wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Aug 12 13:59:51	ppp	19091	[wan_link0] Link: Leave bundle "wan"
Aug 12 13:59:51	ppp	19091	[wan_link0] LCP: state change Opened --> Starting
Aug 12 13:59:51	ppp	19091	[wan_link0] LCP: Down event
Aug 12 13:59:51	ppp	19091	[wan_link0] Link: DOWN event
Aug 12 13:59:51	ppp	19091	[wan_link0] PPPoE: connection closed
Aug 12 13:59:33	ppp	19091	[wan_link0] LCP: no reply to 1 echo request(s)
Aug 12 13:53:00	sshguard	18557	Now monitoring attacks.
                                            D 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post