PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000861 | PacketFence | public | 2009-11-27 17:26 | 2011-01-26 15:43 | |
| Reporter | obilodeau | ||||
| Assigned To | obilodeau | ||||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0000861: pfmon runs out of memory when using a very large trapping.range or registration.range | ||||
| Description | pfmon has a very inefficient way of caching network ranges for its various operations. This is mostly useful for arp mode, other modes almost never query the cache. Check lib/pf/util.pm's pfmon_preload(). When you have a large network (say a 10.0.0.0/8) pfmon will crash with an Out of Memory! error during its preload stage. Optimizing the code doesn't seem a good solution. Big networks won't work in arp isolation and in vlan isolation we run a cleanup loop which rarely accesses the cache so it'll fall back on the less efficient isinrange() but thats ok. So my fix proposal is to disable the caching in vlan isolation mode. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2009-11-27 17:26 | obilodeau | New Issue | |||
| 2009-11-27 17:26 | obilodeau | Status | new => assigned | ||
| 2009-11-27 17:26 | obilodeau | Assigned To | => obilodeau | ||
| 2009-11-27 18:36 | obilodeau | Note Added: 0001413 | |||
| 2009-11-27 18:36 | obilodeau | Status | assigned => resolved | ||
| 2009-11-27 18:36 | obilodeau | Resolution | open => fixed | ||
| 2011-01-26 15:43 | obilodeau | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||