Project

General

Profile

Actions

Bug #4276

closed

Layer 7 not working / ipfw-classifyd high load

Added by Bartłomiej Bujak about 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Layer 7
Target version:
-
Start date:
01/24/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.x
Affected Architecture:
All

Description

After upgrade pfsense 2.1.5 to 2.2 i have problem with ipfw-classifyd

  PID USERNAME  THR PRI NICE   SIZE    RES STATE    TIME    WCPU COMMAND
76425 root        5  20    0 23584K  7760K nanslp   1:45  63.87% ipfw-classifyd

I remove Traffic Shaper Layer7 rule and now all it's ok . I had only 1 rule.

76425 root        5  20    0 23584K  7788K nanslp   3:21   0.00% ipfw-classifyd

Actions #1

Updated by Bartłomiej Bujak about 9 years ago

In logs:

dnsmasq[89256]: failed to send packet: No buffer space available

After remove layer7 rule, DNS ( on client) start work correctly

Actions #2

Updated by Chris Buechler about 9 years ago

  • Project changed from pfSense Packages to pfSense
  • Category set to Layer 7
Actions #3

Updated by winmasta winmasta about 9 years ago

in logs:

ipfw-classifyd: packet dropped: output queue full
Actions #4

Updated by Jim Pingle about 9 years ago

  • Status changed from New to Confirmed
  • Target version set to 2.2.2

Pretty simple to reproduce

  • Add a layer 7 container, for example, to block bittorrent
  • Apply the layer 7 container on a pass rule on LAN to pass all traffic
  • Observe that no traffic passes and ipfw-classifyd is consuming 100% CPU
Actions #5

Updated by Jim Pingle about 9 years ago

  • Subject changed from ipfw-classifyd high load after upgrade do 2.2 to Layer 7 not working / ipfw-classifyd high load
  • Affected Architecture All added
  • Affected Architecture deleted ()
Actions #6

Updated by Florent THOMAS about 9 years ago

Hy, Also concerned

Actions #7

Updated by winmasta winmasta about 9 years ago

version 2.2.1 still have this bug

Actions #8

Updated by Chris Buechler about 9 years ago

  • Target version changed from 2.2.2 to 2.2.3
Actions #9

Updated by Ermal Luçi about 9 years ago

This is missed patch from 8.3 diverttag.diff

Actions #10

Updated by Florent THOMAS almost 9 years ago

Hy folks, any chance to hav a patch for the 2.2.2?

regards

Actions #11

Updated by Chris Buechler almost 9 years ago

  • Target version changed from 2.2.3 to 2.3
Actions #12

Updated by Chris Buechler over 8 years ago

  • Assignee set to Chris Buechler
Actions #13

Updated by Chris Buechler over 8 years ago

  • Status changed from Confirmed to Closed
  • Target version deleted (2.3)
  • Affected Version changed from 2.2 to 2.2.x

closing in favor of #5508

Actions #14

Updated by winmasta winmasta over 8 years ago

version 2.2.5 still have this bug

Actions #15

Updated by Chris Buechler over 8 years ago

winmasta winmasta wrote:

version 2.2.5 still have this bug

Yes. It's not being fixed. See #5508.

Actions #16

Updated by winmasta winmasta over 8 years ago

Too bad, i used it without any problems. Is it going to make a similar module ?

Actions #17

Updated by Michael F over 8 years ago

Version 2.2.5 still affected

Actions

Also available in: Atom PDF