Bug 13518 – warning: setsockopt(PACKET_RX_RING): Protocol not available

Bug 13518 - warning: setsockopt(PACKET_RX_RING): Protocol not available

Summary:	warning: setsockopt(PACKET_RX_RING): Protocol not available

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	tcpdump (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Harald Hoyer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-07-06 07:07 EDT by Pekka Savola
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-08-11 11:02:22 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Pekka Savola 2000-07-06 07:07:42 EDT

Tcpdump gives a warning when running it:

setsockopt(PACKET_RX_RING): Protocol not available

This isn't aesthetically pleasing ;)

Comment 1 Pekka Savola 2000-07-10 15:30:28 EDT

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.

Comment 2 Jeff Johnson 2000-07-12 00:08:01 EDT

This should be fixed by tcpdump-3.4-22 rebuild.

Comment 3 Pekka Savola 2000-07-27 08:08:54 EDT

This bug resurfaced in beta5 / wasn't fixed. :-(

Comment 4 Tim Waugh 2000-07-27 09:47:19 EDT

tcpdump-3.4-26 works fine here: can you check that's what you have?

Comment 5 Tim Waugh 2000-07-27 09:49:00 EDT

Sorry, my mistake; a rebuilt 3.4-26 works, but the binary package was still
faulty.

Comment 6 Pekka Savola 2000-07-31 16:44:32 EDT

Upped the priority and severity.

IMO this isn't something we want to see in Winston final.

Comment 7 Jeff Johnson 2000-08-04 16:47:40 EDT

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.

Comment 8 Pekka Savola 2000-08-10 11:09:47 EDT

This happens in RC1 too :-(

Comment 9 Jeff Johnson 2000-08-11 11:02:19 EDT

Ahh, the problem is compiling *with* 2.4 headers. Error message removed in
tcpdump-2.4-28.

Note You need to log in before you can comment on or make changes to this bug.