Bug 21818

Summary: ipfw queuing: == not eligible messages on kernel log
Product: Base System Reporter: Pekka Savola <pekkas>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-STABLE   
Hardware: Any   
OS: Any   

Description Pekka Savola 2000-10-07 15:50:00 UTC 
After installing ipfw queueing rules, I get the following kind of messages constantly to my kernel log:

---
Oct  7 07:30:07 den last message repeated 2 times
Oct  7 07:30:09 den /kernel: == not eligible, size 1408
Oct  7 07:30:09 den /kernel: == not eligible, size 1408
Oct  7 07:30:11 den /kernel: == not eligible, size 1500
Oct  7 07:30:20 den last message repeated 4 times
Oct  7 07:30:21 den /kernel: == not eligible, size 576
Oct  7 07:30:21 den /kernel: == not eligible, size 1500
Oct  7 07:30:22 den /kernel: == not eligible, size 1500
Oct  7 07:30:22 den /kernel: == not eligible, size 628
Oct  7 07:30:33 den /kernel: == not eligible, size 1500
---

Relevant kernel options: IPFIREWALL, DUMMYNET.


Someone else has seen this too; no replies:

http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1460716+0+archive/2000/freebsd-questions/20000813.freebsd-questions

How-To-Repeat: ipfw add queue 1 ip from my.host to any out
ipfw queue 1 config weight 5 pipe 2 mask dst-ip 0xffffffff 
ipfw pipe 2 config bw 7000Kbit/s plr 0 buckets 512

[this didn't happen with mask 'all', I think]

The idea here is to spread 7Mb/s link across to every user transferring _from_ the server (_to_ traffic is pretty light).
Comment 1 Luigi Rizzo freebsd_committer freebsd_triage 2001-02-11 23:23:46 UTC 
State Changed
From-To: open->closed

the msg was a diagnostic one, and the code has been significantly 
changed since the report. PR not relevant anymore.