Australian NBN connection stops after random time
-
@bleve Yep, so what's your System->Routing setting for the Monitoring IP on your WAN set to?
-
WAN_DHCP WAN 167.179.136.1 167.179.136.1 Interface WAN_DHCP Gateway
That's the next hop, confirmed by traceroute :
[2.6.0-RELEASE][carl@barry.aboc.net.au]/home/carl: traceroute www.sun.com
traceroute: Warning: www.sun.com has multiple addresses; using 23.214.90.91
traceroute to e120265.dscx.akamaiedge.net (23.214.90.91), 64 hops max, 40 byte packets
1 loop1671791360.bng.mel.aussiebb.net (167.179.136.1) 2.708 ms 3.123 ms 1.961 ms
2 10.241.4.108 (10.241.4.108) 1.813 ms 1.851 ms 2.029 ms.
.
. -
@bleve So that's your upstream IP and that's the default action. But if you change it to a public IP that always replies (Google DNS, CloudFlare, any other like that which replies to a ping) you will likely stay online.
This is from an email I sent to a TAC Professional customer earlier this evening regarding a request for a configuration review on this very issue:
I recommend changing your Gateway Monitoring IP from {blank} to something that will respond to a ping always on the internet, typically a DNS server will fit this need. By not specifying this your upstream device is used and ISPs often treat a once-a-second ping as an attempted Denial-of-Service (DoS) attack and will block that ping from happening. It then results in the gateway being marked down, even though the ISP is still routing all the traffic and then you are down for 5-15 minutes depending on the ISP policies. I recommend setting this to either Google's or CloudFlare's DNS server IP.
-
@rcoleman-netgate So you're suggesting that my ISP is blocking the monitor, and then the DHCP fails? What about just getting rid of the monitor entirely? I see that's an option. Silly or not?
-
@bleve I would keep dpinger working and just set the IP to something not in the ISP purview. Easier than trying to guess if the internet is down because you don't have a monitor at all anymore.
-
@rcoleman-netgate Thank you, I've set it to the poor much-hammered-on 8.8.8.8, will wait & see.
Thank you for your help!
Any idea for how I can get the temp sensor to behave? I don't believe it's 27.9 degrees all the time!
Carl
-
@bleve said in Australian NBN connection stops after random time:
I don't believe it's 27.9 degrees all the time!
That sounds kinda low, honestly. Could be reading the wrong detail. I can't comment on the third party hardware -- that's outside of the scope of my work.
-
@rcoleman-netgate It's 100% wrong!
Under all this, is a FreeBSD 12.3 box, is it safe to install mbmon and see if it'll work? -
@bleve We don't recommend side-loading software but if you want to there's nothing to stop you from it.
-
@rcoleman-netgate I'll skip it, if it's not recommended.
Thank you again for your time. -
I'm guessing but it looks like you're with Aussie Broadband - based on that gateway IP address.
What sort of NBN connection do you have? Just wondering what your "NBN modem/router" is.
I'm with Aussie on HFC. I haven't had gateway monitoring on for more than three years. You could just try turning it off and see what happens. ABB-allocated IP addresses are very "sticky".
-
@biggsy said in Australian NBN connection stops after random time:
I'm guessing but it looks like you're with Aussie Broadband - based on that gateway IP address.
Yes, FTTP, with a static IP and a /24 behind it. The IP address won't change. Does it still want some sort of monitoring? Yes. A ping every second? Probably more than it needs!
-
@bleve so I've turned the ping interval down to 1 ping every 5000ms instead of 500ms. That should reduce the unnecessary pings too.
-
So you've got your pfSense box plugged directly into the NBN NTD?
If you don't have any luck with the 5000ms pings, I seriously suggest that you try disabling monitoring. The reason I turned mine off was simply because of false alarms. Never worked out what triggered them but they were false.
-
@biggsy said in Australian NBN connection stops after random time:
So you've got your pfSense box plugged directly into the NBN NTD?
Yes
I'm not sure how else you'd do it? Or why you'd do it any other way?If you don't have any luck with the 5000ms pings, I seriously suggest that you try disabling monitoring. The reason I turned mine off was simply because of false alarms. Never worked out what triggered them but they were false.
I'm certainly considering it! Thank you
-
@bleve said :
I'm not sure how else you'd do it? Or why you'd do it any other way?
Only checking that you didn't have something else between the NTD and pfSense because you said something about the "NBN router/modem". All good.
-
@bleve said in Australian NBN connection stops after random time:
Any idea for how I can get the temp sensor to behave? I don't believe it's 27.9 degrees all the time!
Assuming it's an Intel CPU go to Sys > Adv > Misc and set the thermal sensors to Intel Core.
That will give you the on-die CPU sensors data. You can add the thermal sensors widget to the dashboard to view them. And they will be logged in the Status > Monitoring graphs.
Yes that 27.9°C value is almost certainly bogus. Likely an invalid ACPI sensor location the BIOS is passing.Since it's only the WAN that stops it's probably not an over temperature issue but 'almost too hot to touch' is worrrying.
Steve
-
@stephenw10 thank you, that worked a treat!
-
@bleve said in Australian NBN connection stops after random time:
@stephenw10 thank you, that worked a treat!
I popped a USB powered case fan on top of this little box, and the newly reported 52 degrees is now 35 (Celcius). Win!
Thank you again for your advice and assistance.
-
Followup on this, since we made the change to the service check, there's been zero outages, it's been 100% solid.
Also, the little USB fan I popped on top of the box, has kept the temp nice and low (mid 30's C).
Thank you all again for your help.