Project

General

Profile

Actions
Copy link

Bug #2792

closed

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

Added by Jim Pingle almost 12 years ago. Updated over 11 years ago.

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

100%

Estimated time:
Plus Target Version:
Release Notes:
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.

Actions
Copy link
 #1

Updated by Jim Pingle almost 12 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.

Actions
Copy link
 #2

Updated by Ermal Luçi almost 12 years ago

  • Status changed from New to Feedback

A patch has been committed which should improve the situation

Actions
Copy link
 #3

Updated by Ermal Luçi over 11 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.

Actions
Copy link

Also available in: Atom PDF