Bug 111895
Summary: | r-c-network does not seem to respect static routing on virtual interfaces | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Sven Winnecke <sven.winnecke> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED DEFERRED | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | pcfe, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-20 20:26:53 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
Sven Winnecke
2003-12-11 13:31:34 UTC
and the route-eth0:1 properly used by network restart? sorry... and the route-eth0:1 is not properly used by network restart? Exactly. All interfaces come up properly and the routes are set correctly for the physical interface (eth0) but not for the virtual interface (eth0:1). Setting the route manually "route add ..." works fine however, so I assume it is not a general networking problem. While playing with it I took the virtual interface down and back up (ifdown eth0:1, then ifup eth0:1), and ifup brings these messages: bash# ifup eth0:1 Cannot find device "eth0:1" Cannot find device "eth0:1" bash# That's one line for each interface-dependant route (I tried to set only one route and got only one of those messages). Maybe the real problem is the "ip" tool that is called from within the network scripts, at least the mentioned message text is to be found in the /sbin/ip binary. As long as the problem persists I will just use a little init script with the necessary "route" commands. A fix would still be nice though. ok, I'll reassign to the initscripts component... This problem will be resolved in a future release of Red Hat Enterprise Linux; tentatively, RHEL 5. Red Hat does not currently plan to provide a resolution for this in a Red Hat Enterprise Linux update for currently deployed systems. With the goal of minimizing risk of change for deployed systems, and in response to customer and partner requirements, Red Hat takes a conservative approach when evaluating changes for inclusion in maintenance updates for currently deployed products. The primary objectives of update releases are to enable new hardware platform support and to resolve critical defects. |