I'm experiencing this as well. Setting the link speed didn't do it for me.
My first attempt was to pass 192.168.100.1 (my modem) to 192.168.100.20 67/68 UDP. Noticed in the logs, but doesn't make sense as there are no other devices. Set top box perhaps?
Now I am getting Rule (12000) blocking source 10.240.160.225:67 destination: my public ip:68 So, I deselected Block private networks on WAN and rebooted.
Looks like the dhcp requests are not being blocked now, but I am still getting latency alerts.
recently upgraded to 2.3.4-release-p1
Overnight, another latency error and dpinger sendto error 65.
Noticed this in firewall log.
Oct 12 07:10:02 WAN block bogon IPv6 networks from WAN (11000) 0.0.0.0:68 255.255.255.255:67 UDP
Has my ISP changed the way they are doling out addresses?
Update: Had cable dude come out and string a new line to the pole and have had no drops for 24 hours.
Update 2: It's back. Not as bad but this is definitely getting annoying. Time to dump Optimum Cable for FIOS perhaps.
Oct 16 15:24:28 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 68.196.96.1 bind_addr 68.196.101.146 identifier "WAN_DHCP " Oct 16 15:24:23 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 68.196.96.1 bind_addr 68.196.101.146 identifier "WAN_DHCP " Oct 16 15:24:18 dpinger WAN_DHCP 68.196.96.1: sendto error: 65 Oct 16 15:24:17 dpinger WAN_DHCP 68.196.96.1: sendto error: 65