Project

General

Profile

Bug #2792

pfSctl / check_reload_status can ignore linkup/linkdown events if they fire too fast.

Added by Jim Pingle over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Ermal Luçi
Category:
Interfaces
Target version:
Start date:
02/04/2013
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.0.x
Affected Architecture:

Description

If an ethernet interface's link goes down and up too rapidly, the 'up' event sent by pfSctl ("linkup start") can be ignored by the rate limiting code that prevents multiple events from being triggered too rapidly.

As such, if someone using DHCP has their link cycle rapidly, then dhclient will be stopped but will never restart.

History

#1 Updated by Jim Pingle over 7 years ago

This happens on RELENG_2_0 as well so we'll need to pull back the fix there as well if any pfSense code changes are required.

#2 Updated by Ermal Luçi over 7 years ago

  • Status changed from New to Feedback

A patch has been committed which should improve the situation

#3 Updated by Ermal Luçi about 7 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100

linkup events will never be aggregated by check_reload_status hence no missing.

Also available in: Atom PDF