pfSense 2.6 CE randomly drops internet/gateway connectivity

Networking & Firewalls
1

Hello,

Hoping someone can help me out. I have been using pfsense CE for a couple of years now, with little changes to the default settings.

I am running on a physical box (not virtualized) and recently i have started to see that randomly the gateway connectivity will drop. I have checked the internet connection from my modem during this time by plugging my laptop into it directly and the connection works.

The drop lasts for about 1 to 5 minutes, and then the connection resumes (no reboot required).
At first I thought that maybe the Monitor IP that I was using was the cause of the issue but changing this to 8.8.8.8 and 1.1.1.1 the issue still occurrs. Searching on the net I found a post where someone else had a similar issue and found that by turning off Gateway Monitoring it resolved the issue for them, I have also tried this and found the issue to still occur.

I have thought about trying the following to see if it resolves my issue:

1 - Perform a fresh installation of pfSense and restore my settings
2 - Perform a fresh installation of pfSense and reconfigure my settings manually

But wanted to check to see if anyone had any thoughts before I go down this avenue.

A friend has suggested that maybe my NICs could be on thier way out, but I don’t really see any evidence to support this.

2

What network card.

If realtek, replace it with a intel card ,as PFSense has issues with realtek cards

2 Likes
3

Hi Paul,

I am using a 4 port Intel I350 NIC card, configured as below

igb2@pci0:1:0:2: class=0x020000 card=0x7b18108e chip=0x15218086 rev=0x01 hdr=0x00
vendor = ‘Intel Corporation’
device = ‘I350 Gigabit Network Connection’
class = network
subclass = ethernet
bar [10] = type Memory, range 32, base 0xff500000, size 1048576, enabled
bar [1c] = type Memory, range 32, base 0xffa04000, size 16384, enabled
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message, 64 bit, vector masks
cap 11[70] = MSI-X supports 10 messages, enabled
Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
cap 10[a0] = PCI-Express 2 endpoint max data 512(512) FLR NS
max read 512
link x4(x4) speed 5.0(5.0) ASPM disabled(L0s/L1)
cap 03[e0] = VPD
ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
ecap 0003[140] = Serial 1 a0369fffffed0bcc
ecap 000e[150] = ARI 1
ecap 0010[160] = SR-IOV 1 IOV disabled, Memory Space disabled, ARI disabled
0 VFs configured out of 8 supported
First VF RID Offset 0x0180, VF RID Stride 0x0004
VF Device ID 0x1520
Page Sizes: 4096 (enabled), 8192, 65536, 262144, 1048576, 4194304
ecap 0017[1a0] = TPH Requester 1
ecap 000d[1d0] = ACS 1

4

Not sure if this helps but I had constant issues with 2.6 and the gateways (ISP and VPN) not staying up. The same build on 2.5.2 was rock solid.

If you have the ISO perhaps roll back to 2.5.2 to see if you have the same problem.

If you don’t try out pfSense Plus.

I upgraded to 23.05 and the gateways have been rock solid.

I never got to the root cause why 2.6 won’t work for my build but I can say it has worked for the last week on 23.05 with no issues.

5

I have to ask, even though the control panel says it isn’t connected, do you still have internet through pfsense? At home I have issues with the pings getting lost from the dpinger service, but still have connection working. Had this on 2.4.5 and 2.6.x with an older Intel card. I may upgrade to an i350 soon and do more testing, but a lot of my problem is that I switched to T Mobile and CGNAT is an issue.

I’m also not running my site to site VPN right now, so really no reason to be running pfsense at home. Hasn’t been a big priority for me to make everything work again.

6

no all devices loose connection to the internet

7

Hi Neo,

I don’t have access to 2.5.2 but have just registered for Pfsense+ so will try upgrading to 23.05 in the morning and see if that makes a difference…

8

I’d recommend keeping pfSense ISO’s locally, once they upgrade, Netgate pulls the previous version. In the Plus+ version you can keep a snapshot of the build (not just config) if you are using ZFS file format for pfSense.

9

thanks for the info, I ended up doing the upgrade last night once I recieved the key, will see how it goes today, also enaled the gatway monitoring incase I start to see signs of the internet failing.

Also looks like you can get the ISO’s from here https://repo.ialab.dsu.edu/pfsense/

10

So the issue, occurred again today:

image

11

Are you sure this is a pfsense issue and not a modem or ISP issue?

1 Like
12

ISP has monitored the connection while this has been occurring and see no drop in connection from the modem, I also from the lights and connected laptop don’t see a connection issue when this occurs

13

Have you tired to replace the cable that goes from your modem to your firewall? I ask because I had a bad cable and it caused this exact issue.

Also have you looked at the logs on pfsense to see if anything stand out?

14

Hi,

This is what I have done so far to try and resolve the issue:

  • replaced ethernet cable between pfSense and modem with a new one
  • replaced ethernet cable between pfSense and network switch with a new one
  • had ISP replace the modem
  • had ISP monitor modem connectivity for 24 hrs to see if signal dropped
  • reinstalled pfSense and restored configuration from backup
  • Connected spare laptop directly to the modem to monitor connectivity during pfSense reporting connectity issue

under status/System Logs/System/Gateway the following is reported:

Jun 14 07:58:07 dpinger 85346 WAN_DHCP 1.1.1.1: Alarm latency 30185us stddev 45099us loss 11%
Jun 14 07:58:07 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Alarm latency 30068us stddev 36149us loss 11%
Jun 14 08:13:01 dpinger 85346 WAN_DHCP 1.1.1.1: Clear latency 22539us stddev 21771us loss 3%
Jun 14 08:13:01 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Clear latency 29975us stddev 36159us loss 2%
Jun 14 17:51:38 dpinger 85346 WAN_DHCP 1.1.1.1: Alarm latency 23192us stddev 20861us loss 11%
Jun 14 17:52:29 dpinger 85346 WAN_DHCP 1.1.1.1: Clear latency 20923us stddev 20570us loss 7%
Jun 14 18:17:38 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Alarm latency 64526us stddev 99461us loss 11%
Jun 14 18:17:39 dpinger 85346 WAN_DHCP 1.1.1.1: Alarm latency 56144us stddev 95155us loss 11%
Jun 14 18:17:49 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Clear latency 59741us stddev 88561us loss 10%
Jun 14 18:17:50 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Alarm latency 59267us stddev 88638us loss 11%
Jun 14 18:22:59 dpinger 85346 WAN_DHCP 1.1.1.1: Clear latency 48994us stddev 92146us loss 5%
Jun 14 18:23:02 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Clear latency 50072us stddev 75239us loss 10%
Jun 14 18:23:03 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Alarm latency 50183us stddev 75573us loss 11%
Jun 14 18:23:18 dpinger 85346 WAN_DHCP 1.1.1.1: Alarm latency 69262us stddev 106151us loss 11%
Jun 14 18:26:15 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Clear latency 37689us stddev 46263us loss 5%
Jun 14 18:26:16 dpinger 85346 WAN_DHCP 1.1.1.1: Clear latency 28150us stddev 47459us loss 10%
Jun 14 18:26:20 dpinger 85346 WAN_DHCP 1.1.1.1: Alarm latency 28273us stddev 47646us loss 11%
Jun 14 18:26:31 dpinger 85712 WAN_DHCP6 2606:4700:4700::1111: Alarm latency 41238us stddev 46147us loss 11%
Jun 14 18:27:25 dpinger 85712 exiting on signal 15
Jun 14 18:27:25 dpinger 85346 exiting on signal 15
Jun 14 18:27:25 dpinger 16193 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 1.1.1.1 bind_addr 174.119.182.87 identifier WAN_DHCP
Jun 14 18:27:25 dpinger 17385 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 2606:4700:4700::1111 bind_addr 2607:f798:804:2a6:287c:f5df:161:f47 identifier WAN_DHCP6
Jun 14 18:27:27 dpinger 17385 WAN_DHCP6 2606:4700:4700::1111: Alarm latency 14149us stddev 1217us loss 25%
Jun 14 18:27:30 dpinger 16193 WAN_DHCP 1.1.1.1: Alarm latency 48265us stddev 65606us loss 11%
Jun 14 18:27:54 dpinger 17385 WAN_DHCP6 2606:4700:4700::1111: Clear latency 30108us stddev 42912us loss 7%
Jun 14 18:28:03 dpinger 16193 WAN_DHCP 1.1.1.1: Clear latency 25738us stddev 36402us loss 8%
Jun 14 18:33:22 dpinger 16193 WAN_DHCP 1.1.1.1: sendto error: 65
Jun 14 18:33:23 dpinger 16193 WAN_DHCP 1.1.1.1: sendto error: 65
Jun 14 18:33:23 dpinger 16193 WAN_DHCP 1.1.1.1: sendto error: 65
Jun 14 18:33:24 dpinger 16193 WAN_DHCP 1.1.1.1: sendto error: 65
Jun 14 18:33:24 dpinger 17385 exiting on signal 15
Jun 14 18:33:24 dpinger 16193 exiting on signal 15
Jun 14 18:37:20 dpinger 92047 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 1.1.1.1 bind_addr 174.119.182.87 identifier WAN_DHCP
Jun 14 18:37:20 dpinger 92590 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 2606:4700:4700::1111 bind_addr 2607:f798:804:2a6:287c:f5df:161:f47 identifier WAN_DHCP6
Jun 14 18:37:22 dpinger 92590 exiting on signal 15
Jun 14 18:37:22 dpinger 92047 exiting on signal 15
Jun 14 18:37:22 dpinger 28834 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 1.1.1.1 bind_addr 174.119.182.87 identifier WAN_DHCP
Jun 14 18:37:22 dpinger 29717 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 2606:4700:4700::1111 bind_addr 2607:f798:804:2a6:287c:f5df:161:f47 identifier WAN_DHCP6
Jun 14 18:37:22 dpinger 29717 exiting on signal 15
Jun 14 18:37:22 dpinger 28834 exiting on signal 15
Jun 14 18:37:22 dpinger 48775 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 1.1.1.1 bind_addr 174.119.182.87 identifier WAN_DHCP
Jun 14 18:37:22 dpinger 49031 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 2606:4700:4700::1111 bind_addr 2607:f798:804:2a6:287c:f5df:161:f47 identifier WAN_DHCP6
Jun 14 18:37:26 dpinger 49031 WAN_DHCP6 2606:4700:4700::1111: Alarm latency 18471us stddev 2683us loss 50%
Jun 14 18:37:47 dpinger 49031 exiting on signal 15
Jun 14 18:37:47 dpinger 48775 exiting on signal 15
Jun 14 18:37:47 dpinger 40473 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 1.1.1.1 bind_addr 174.119.182.87 identifier WAN_DHCP
Jun 14 18:37:47 dpinger 40706 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 2606:4700:4700::1111 bind_addr 2607:f798:804:2a6:5c9c:96c:71cc:96f3 identifier WAN_DHCP6
Jun 14 20:12:14 dpinger 40473 WAN_DHCP 1.1.1.1: Alarm latency 22968us stddev 18220us loss 11%
Jun 14 20:12:26 dpinger 40473 WAN_DHCP 1.1.1.1: Clear latency 21496us stddev 17134us loss 9%

under status/System Logs/System/Routing the following is reported:

Jun 14 11:45:22 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:22 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:22 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:22 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:24 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:24 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:25 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:25 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:26 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:26 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:27 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 11:45:38 miniupnpd 63328 upnp_event_process_notify: connect(10.100.1.104:2869): Operation timed out
Jun 14 18:27:08 radvd 27023 attempting to reread config file
Jun 14 18:27:08 radvd 27023 warning: AdvDNSSLLifetime <= 2*MaxRtrAdvInterval would allow stale DNS suffixes to be deleted faster
Jun 14 18:27:08 radvd 27023 resuming normal operation
Jun 14 18:27:24 radvd 27023 attempting to reread config file
Jun 14 18:27:24 radvd 27023 warning: AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
Jun 14 18:27:24 radvd 27023 warning: (/var/etc/radvd.conf:29) AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
Jun 14 18:27:24 radvd 27023 warning: AdvDNSSLLifetime <= 2*MaxRtrAdvInterval would allow stale DNS suffixes to be deleted faster
Jun 14 18:27:24 radvd 27023 resuming normal operation
Jun 14 18:27:25 radvd 27023 attempting to reread config file
Jun 14 18:27:25 radvd 27023 warning: AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
Jun 14 18:27:25 radvd 27023 warning: (/var/etc/radvd.conf:29) AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
Jun 14 18:27:25 radvd 27023 warning: AdvDNSSLLifetime <= 2*MaxRtrAdvInterval would allow stale DNS suffixes to be deleted faster
Jun 14 18:27:25 radvd 27023 resuming normal operation
Jun 14 18:27:34 radvd 27023 attempting to reread config file
Jun 14 18:27:34 radvd 27023 warning: AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
Jun 14 18:27:34 radvd 27023 warning: (/var/etc/radvd.conf:29) AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
Jun 14 18:27:34 radvd 27023 warning: AdvDNSSLLifetime <= 2*MaxRtrAdvInterval would allow stale DNS suffixes to be deleted faster
Jun 14 18:27:34 radvd 27023 resuming normal operation
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:22 miniupnpd 63328 Failed to get IP for interface igb0
Jun 14 18:33:22 miniupnpd 63328 SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jun 14 18:33:22 miniupnpd 63328 PCPSendUnsolicitedAnnounce(sockets[0]) sendto(): No route to host
Jun 14 18:33:22 miniupnpd 63328 PCPSendUnsolicitedAnnounce() IPv6 sendto(): Network is down
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:22 miniupnpd 63328 Failed to get IP for interface igb0
Jun 14 18:33:22 miniupnpd 63328 SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jun 14 18:33:22 miniupnpd 63328 PCPSendUnsolicitedAnnounce(sockets[0]) sendto(): No route to host
Jun 14 18:33:22 miniupnpd 63328 PCPSendUnsolicitedAnnounce() IPv6 sendto(): Network is down
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:22 miniupnpd 63328 ioctl(s, SIOCGIFADDR, …): Can’t assign requested address
Jun 14 18:33:24 radvd 27023 exiting, 1 sigterm(s) received
Jun 14 18:33:24 radvd 27023 sending stop adverts
Jun 14 18:33:24 radvd 27023 removing /var/run/radvd.pid
Jun 14 18:33:24 radvd 27023 returning from radvd main
Jun 14 18:33:30 radvd 77131 version 2.19 started
Jun 14 18:33:30 radvd 77131 warning: AdvDNSSLLifetime <= 2*MaxRtrAdvInterval would allow stale DNS suffixes to be deleted faster
Jun 14 18:35:37 radvd 77363 attempting to reread config file
Jun 14 18:35:37 radvd 77363 warning: AdvDNSSLLifetime <= 2*MaxRtrAdvInterval would allow stale DNS suffixes to be deleted faster
Jun 14 18:35:37 radvd 77363 resuming normal operation
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=10, 10.100.1.245): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 sendto(udp_notify=11, [2607:fea8:45d9:1100:a236:9fff:feed:bcd]): Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=491, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=491, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=507, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=489, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=475, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=495, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=499, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=427, dest=[ff0e::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=491, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=491, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=507, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=489, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=475, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=495, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=499, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=427, dest=[ff05::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=491, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=491, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=507, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=489, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=475, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=495, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=435, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=499, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=11, len=427, dest=[ff02::c]:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=469, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=469, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=485, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=467, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=413, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=453, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=413, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=473, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=413, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=477, dest=239.255.255.250:1900): sendto: Network is down
Jun 14 18:35:52 miniupnpd 63328 try_sendto(sock=10, len=405, dest=239.255.255.250:1900): sendto: Network is down

igb0 is the network interface that connects to the modem

15

There are advanced settings for the WAN connection, perhaps the defaults are not working for you, I only just changed over to fiber and noticed this section, mine are on defaults but perhaps test the other presets.

Screenshot from 2023-06-15 08-25-27
Screenshot from 2023-06-15 08-25-271153×538 68.6 KB

16

Do you need IPv6 on the wan connection, if not I would disable IPv6

What IP address are you monitoring on the isp gateway - System - Rounting - Gatewys

17

Hi Neo and Paul.

@neogrid - I have look at those settings and gone over them with my ISP, who have said that the information is not needed.

@Paul - I am using IP’s 1.1.1.1 for IPv4 and 2606:4700:4700::1111 for IPv6, the IPv6 enablement was through my ISP’s suggestion and using the settings that they provided.

18

When I was investigating my issue I did read in some odd situations setting a non-local gateway works.

Screenshot 2023-06-15 at 13-36-28 System Routing Gateways Edit - pfSensePem.pembroke.lan
Screenshot 2023-06-15 at 13-36-28 System Routing Gateways Edit - pfSensePem.pembroke.lan1223×1292 115 KB

19

i have not tried that setting yet, i have made a couple of tweeks to the gateway monitor, I will see if that helps, if not then I will revert the settings and enable this and see how that goes

20

restart dpinger service (Gateway Monitoring Daemon).