Project

General

Profile

Actions
Copy link

Bug #4276

closed
BB CB

Layer 7 not working / ipfw-classifyd high load

Bug #4276: Layer 7 not working / ipfw-classifyd high load

Added by Bartłomiej Bujak over 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Chris Buechler
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

BB Updated by Bartłomiej Bujak over 11 years ago Actions
Copy link
 #1

In logs:

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

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

CB Updated by Chris Buechler over 11 years ago Actions
Copy link
 #2

  • Project changed from pfSense Packages to pfSense
  • Category set to Layer 7

WW Updated by winmasta winmasta over 11 years ago Actions
Copy link
 #3

in logs:

ipfw-classifyd: packet dropped: output queue full

JP Updated by Jim Pingle over 11 years ago Actions
Copy link
 #4

  • 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

JP Updated by Jim Pingle over 11 years ago Actions
Copy link
 #5

  • 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 ()

FT Updated by Florent THOMAS over 11 years ago Actions
Copy link
 #6

Hy, Also concerned

WW Updated by winmasta winmasta over 11 years ago Actions
Copy link
 #7

version 2.2.1 still have this bug

CB Updated by Chris Buechler over 11 years ago Actions
Copy link
 #8

  • Target version changed from 2.2.2 to 2.2.3

EL Updated by Ermal Luçi over 11 years ago Actions
Copy link
 #9

This is missed patch from 8.3 diverttag.diff

FT Updated by Florent THOMAS over 11 years ago Actions
Copy link
 #10

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

regards

CB Updated by Chris Buechler over 11 years ago Actions
Copy link
 #11

  • Target version changed from 2.2.3 to 2.3

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #12

  • Assignee set to Chris Buechler

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #13

  • 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

WW Updated by winmasta winmasta almost 11 years ago Actions
Copy link
 #14

version 2.2.5 still have this bug

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #15

winmasta winmasta wrote:

version 2.2.5 still have this bug

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

WW Updated by winmasta winmasta almost 11 years ago Actions
Copy link
 #16

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

MF Updated by Michael F almost 11 years ago Actions
Copy link
 #17

Version 2.2.5 still affected

Actions
Copy link

Also available in: Atom