Bug 75354 - sysctl variable problem when setting parameters on vlan interfaces
Summary: sysctl variable problem when setting parameters on vlan interfaces
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: procps
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-07 16:11 UTC by Tarhon-Onu Victor
Modified: 2007-04-18 16:47 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-03-29 12:42:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Tarhon-Onu Victor 2002-10-07 16:11:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Description of problem:
Sysctl is unable to set up parameters for vlan interfaces. The problem consists
in the separators which are '.' and/or '/'. If in a variable in sysctl.conf are
both present (net.ipv4/ip_forward) sysctl will not warn us. So we will unable to
set (say) rp_filter on eth1.307 vlan interface.
The problem is present to all previous versions of procps, and it can be fixed
quicly if only one of the delimiters is accepted for the same variable.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.create a vlan interface
2.figure out how to write a variable in /etc/sysctl.conf in roder to set
parameters on eth1.307.
3.let me know if you succeed (maybe it's possible, but I found no possibility).
	

Additional info:

Comment 1 Alexander Larsson 2002-10-08 14:28:38 UTC
yeah. That doesn't seem possible.
Unfortunately it also seems hard to fix and stay backwards compat.
Adding a switch is possible, but something else needs to be done for
/etc/sysctl.conf.


Comment 2 Alexander Larsson 2004-02-05 10:44:23 UTC
Mass reassign to new owner

Comment 3 Daniel Walsh 2004-03-29 12:42:26 UTC
Fixed in procps 3.2.0


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