dpinger and WAN access problems since 2.5.0

charvey

I upgraded to 2.5.0 after over 300 days of flawless uptime in 2.4.5. Now, about once a day I am seeing the following symptoms:

No WAN access from all clients
[2.5.0-RELEASE][admin@pfSense.local]/root: ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
ping: sendto: Permission denied
ping: sendto: Permission denied
Mar 17 13:35:04 dpinger 90705 WAN_DHCP xxx.xxx.xxx.xxx: sendto error: 13

During these outages I also have:

igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: WAN
	options=e120bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6>
	ether 0c:c4:7a:ac:82:f2
	inet6 fe80::ec4:7aff:feac:82f2%igb0 prefixlen 64 scopeid 0x1
	inet xxx.xxx.xxx.xxx netmask 0xffffffe0 broadcast 255.255.255.255
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Status->Gateways->Reload Service fixes WAN access every time. but dpinger will not always work after gateway service reload. So I'll see the WAN gateway marked as down on the dashboard, but everything else is fine.

The default gateway is set in System->Routing. There is only one gateway.

charvey

Solved this -- kinda. I disabled CoDeL and everything went back to normal. Maybe I'll try setting it up again once 2.5.1 comes out.