Bug 2335

Summary: Adding default route fails if not on same network as IF
Product: [Retired] Red Hat Linux Reporter: tm
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-09-20 20:33:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description tm 1999-04-23 04:50:40 UTC
Have a computer which eth0 address is on a different
subnet than the router providing the default gw.

I know that I could use ipalias to get it on this
network as well, but of various reasons I don't want

Lets say:
Physical network:
Default gw:
Address of RH 5.2 computer:

To rech the default gw I first have to add a route
to on eth0.

Then I can set the default route to
No problem.

The problem is that /etc/sysconfig/network-scripts/ifup
adds the default route before it adds other static
routes (calling ifup-post at the very end of the script).

Therefore, the default route cannot be added as it
don't know here the network is.

The only reason for adding default route before other
static routes that I may think of is to be able to
reach a name server that is used to resolve gateway

I would say that doing that is a bad habit and that
it is a bug to add the default route before local
static routes are added.

Terje Marthinussen

Comment 1 Bill Nottingham 1999-09-20 20:33:59 UTC
Fixing this would break static routes on the other side
of the gateway, though. We probably won't fix this.