metronet fiber, internet goes down roughly every 24 hours
-
thank you
i am about to boot up the minnowboard. do you have any idea what i can be looking for in the logs for a failing wan port?
example:
the first line is when the internet went down. 100.92.192.1 is the gateway address of the modem itself
Feb 16 05:55:27 dpinger WAN_DHCP 100.92.192.1: Alarm latency 2326us stddev 2231us loss 21% Feb 16 06:03:57 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " Feb 16 06:03:57 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " Feb 16 06:04:05 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " Feb 16 06:04:05 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " Feb 16 06:07:25 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " Feb 16 06:07:25 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " Feb 16 06:07:33 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " Feb 16 06:07:36 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 100.92.192.1 bind_addr 100.92.205.91 identifier "WAN_DHCP " -
All of those are dpinger starting apart from the first line which is an alarm when it hit >20% packet loss.
There's nothing in the system to show why it kept restarting? Flapping link would be my first guess.
Steve
-
Understood.
Would you agree that the device Hooked up to the pfsense router is what is going offline though
Which tab are you suggesting I review logs from
-
The main system log would show the link going up and down if it is in fact doing that.
If not it should show what it triggering dpinger to restart continually.Steve
-
The device was powered off so it does not show any logs under system - general before 11am the last time I got the previous log I posted
Checking car/ log -
Order 101916 has been placed
I am not going to use the minnowboard as my primary device anymore
Thank you for great support and products
-
Well I can't object.
But it would be good to know why that was happening. You might try swapping the LAN and WAN assignment and see if the error follows the interface or stays on the port.Steve
-
i tried loading ubuntu LTS. 2 version in fact, to test the nics. i don't have a hub to get both a keyboard and mouse working, only one would work at a time. a keyboard with a hub built in... still both would not work. could not find any good documentation
then i find the minnowboard project has been abandoned pretty much, so i'll scratch that 300 dollar purchase off as a lesson (nothing against Netgate i know it wasn't an official product)
time to move on to bigger and better you know
-
That 4220 might still be covered under warranty. I’m pretty sure it was released after the SG-2220.
Jeff
-
I bought it in august of 2018
The whole minnowboard project has been abandoned it appears
-
@bcruze I would still contact them, it's probably under warranty.
https://go.netgate.com/support/login
Jeff
-
@akuma1x said in is the Netgate sg-2220 capable of release 2.4.5:
@bcruze I would still contact them, it's probably under warranty.
https://go.netgate.com/support/login
Jeff
looks like i have my answer in this thread. it is a Pfsense software issue : https://forum.netgate.com/topic/150568/problems-reestablishing-the-connection/2
-
since my wan continues to drop(supposedly Metronet says its not). and Pfsense will not reconnect:
under interfaces > wan > dhcp configuration > presets.
correct me if i am wrong. but will that not force the device to reconnect per the presets and fix this issue?
-
If you are actually hitting https://redmine.pfsense.org/issues/9267 then the problem is that if dhclient hits it's timeout values it mishandles the error, crashes out and never retries. Others have worked around that by setting the timeout to something much higher like 900s. https://forum.netgate.com/post/854007
That works well for the situation where the modem reboots but takes longer than the timeout to do so.
Steve
-
its enabled now. it was not before. 24 hours will tell, thanks for the replies Stephen
more logs, that show the gateway goes down for whatever reason.
Feb 19 18:13:27 rc.gateway_alarm 2403 >>> Gateway alarm: WAN_DHCP (Addr:100.92.192.1 Alarm:1 RTT:1.135ms RTTsd:1.512ms Loss:21%) Feb 19 18:13:27 check_reload_status updating dyndns WAN_DHCP Feb 19 18:13:27 check_reload_status Restarting ipsec tunnels Feb 19 18:13:27 check_reload_status Restarting OpenVPN tunnels/interfaces Feb 19 18:13:27 check_reload_status Reloading filter Feb 19 18:13:28 php-fpm 66863 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP. Feb 19 18:16:59 php-fpm 53040 /index.php: Successful login for user 'admin' from: 192.168.1.205 (Local Database) Feb 19 18:21:59 php-fpm 53040 /status_interfaces.php: The command '/usr/local/sbin/dhclient {$ipv} -d -r -lf '/var/db/dhclient.leases.igb0' -cf '/var/etc/dhclient_wan.conf' -sf '/usr/local/sbin/pfSense-dhclient-script'' returned exit code '1', the output was 'Internet Systems Consortium DHCP Client 4.3.6-P1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on BPF/igb0/00:08:a2:09:e9:be Sending on BPF/igb0/00:08:a2:09:e9:be Can't attach interface {} to bpf device /dev/bpf0: Device not configured If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting.' Feb 19 18:22:07 check_reload_status rc.newwanip starting igb0 Feb 19 18:22:08 php-fpm 66863 /rc.newwanip: rc.newwanip: Info: starting on igb0. Feb 19 18:22:08 php-fpm 66863 /rc.newwanip: rc.newwanip: on (IP address: 100.92.220.245) (interface: WAN[wan]) (real interface: igb0). Feb 19 18:22:08 php-fpm 66863 /rc.newwanip: The command '/sbin/route delete -host ' returned exit code '64', the output was 'route: destination parameter required route: usage: route [-46dnqtv] command [[modifiers] args]' Feb 19 18:22:08 php-fpm 66863 /rc.newwanip: The command '/sbin/route delete -host ' returned exit code '64', the output was 'route: destination parameter required route: usage: route [-46dnqtv] command [[modifiers] args]' Feb 19 18:22:13 php-fpm 66863 /rc.newwanip: Resyncing OpenVPN instances for interface WAN. Feb 19 18:22:13 php-fpm 66863 OpenVPN terminate old pid: 98658 Feb 19 18:22:14 kernel sonewconn: pcb 0xfffff8000a55db40: Listen queue overflow: 2 already in queue awaiting acceptance (1 occurrences) Feb 19 18:22:16 php-fpm 66863 /rc.newwanip: OpenVPN ID client3 PID 98658 still running, killing. Feb 19 18:22:17 kernel ovpnc3: link state changed to DOWN Feb 19 18:22:17 php-fpm 66863 OpenVPN PID written: 84973 Feb 19 18:22:17 check_reload_status Reloading filter Feb 19 18:22:17 php-fpm 66863 /rc.newwanip: Creating rrd update script Feb 19 18:22:19 kernel ovpnc3: link state changed to UP Feb 19 18:22:19 check_reload_status rc.newwanip starting ovpnc3 Feb 19 18:22:19 php-fpm 66863 /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 100.92.220.245 -> 100.92.220.245 - Restarting packages. Feb 19 18:22:19 check_reload_status Starting packages Feb 19 18:22:20 php-fpm 339 /rc.newwanip: rc.newwanip: Info: starting on ovpnc3. -
Still went down, I called they reset the ont and it came back instantly
I’ll have a static ip Monday
And a new modem Monday...
I setup the new 3100 today and it runs great!
Anything specific to setup a static address on pfsense?
-
Not really, if it's actually a static IP set the WAN to static and configure the IP, subnet and gateway.
If it's supplied to you a static dhcp lease then you don't have to do anything.
Steve
-
Every 24 hours this is beyond frustrating
3 pfsense routers all the same issue now
So according to the redmine fix isn’t released until version 2.5?
-
It's not at all clear that's what you're hitting. When it goes down what do you do to re-stablish it?
If that's your only WAN connection you can just disable the 'gateway monitoring action' on the gateway. That will keep the monitoring stats to prevent it reloading everything whenever the gateway stops responding.
You should probably also set the monitoring IP to something other than the gateway. The gateway may well drops pings under load.Steve
-
i turned off gateway monitoring entirely yesterday and it still went down early this morning
i go to interface tab. release, renew and the connection instantly comes back online
here are my findings the Nokia ONT is changing the local address of the device every 24 hours. when it changes Pfsense says the wan goes down, and everything stops working. i have no way to communicate to the ONT by webqui or ftp etc. since they willl not release that to me.
the last setting i just changed under wan is : Block private networks and loopback addresses UNCHECKED
