Bug 13518
| Summary: | warning: setsockopt(PACKET_RX_RING): Protocol not available | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Pekka Savola <pekkas> |
| Component: | tcpdump | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-08-11 15:02:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pekka Savola
2000-07-06 11:07:42 UTC
I tracked this to libpcap's pcap_open_live before figuring out this was just another compile issue. 'rpm --rebuild tcpdump*.src.rpm' fixes the problem. This should be fixed by tcpdump-3.4-22 rebuild. This bug resurfaced in beta5 / wasn't fixed. :-( tcpdump-3.4-26 works fine here: can you check that's what you have? Sorry, my mistake; a rebuilt 3.4-26 works, but the binary package was still faulty. Upped the priority and severity. IMO this isn't something we want to see in Winston final. This smells like Yet Another Trip through the build system with final kernel headers should fix. Please reopen if tcpdump-3.4-27 still has a problem. This happens in RC1 too :-( Ahh, the problem is compiling *with* 2.4 headers. Error message removed in tcpdump-2.4-28. |