Bug 346421 – kernel increasing the snmp counter error.

Bug 346421 - kernel increasing the snmp counter error.

Summary:	kernel increasing the snmp counter error.

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Enterprise Linux 3
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	3.9
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Kernel Manager
QA Contact:	Martin Jenner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-23 04:09 EDT by Gui Jianfeng
Modified:	2008-05-01 18:39 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-05-01 18:39:34 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
A patch to fix this problem (1.51 KB, patch) 2007-10-23 04:09 EDT, Gui Jianfeng	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Gui Jianfeng 2007-10-23 04:09:14 EDT

Description of problem:
When kernel receives a package with wrong destination ipv4 address,
the "InAddrErrors" counter located in /proc/net/snmp doesn't increase correctly.

Version-Release number of selected component (if applicable):
2.4.21-50.EL

How reproducible:
send ipv4 packages with wrong destination address(for instance 0.0.0.0)
check the "InAddrErrors" increasing correctly

Steps to Reproduce:
1.
2.
3.
  
Actual results:
InAddrErrors is always 0

Expected results:
InAddrErrors increase correctly

Additional info:

Comment 1 Gui Jianfeng 2007-10-23 04:09:14 EDT

Created attachment 234851 [details]
A patch to fix this problem

Comment 2 Don Howard 2008-05-01 18:39:34 EDT

Thank you for the patch proposal.

RHEL3 is no longer in active developement.  Only critical security and bug fixes
will be considered for inclusion.

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