| Summary: | Stabilize net-analyzer/sflowtool | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Benjamin Smee (strerror) (RETIRED) <strerror> |
| Component: | New packages | Assignee: | Benjamin Smee (strerror) (RETIRED) <strerror> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ppc |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Benjamin Smee (strerror) (RETIRED)
2005-11-26 04:35:01 UTC
Only problem here seems to be that sFlow packets are high speed switched networks. I'm unfortunately not privleged enough to have one of those. Is there some kind of a test case for this? Also s/sflowtools/sflowtool/. Thats not quite true. Sflow is just a standard (like netflow) for sending / storing information about traffic flows around a network. Unfortunately most of the devices that support it are large commercial high end routers, which understandably makes it hard to test. That said I believe that ntop can export sflows, so you could configure ntop to send some sflows, and then use the sflowtools package to capture / analyse them as a test. Failing that you can just accept mine and our users assurances that it is working in production environments "as is". x86 has indicated that they are happy if I mark this stable myself. I will do that shortly for x86 which just leaves ppc. PPC herd please let me know one way or the other about this soon so I can close this bug :) Stable on x86, thanks strerror Marked ppc stable, sorry for the wait. It seems to work okay, but as I also don't have the hardware in question. Since we're the last arch, I'll close the bug. |