Bug 10587

Summary: linuxconf won't create route to host on specific interface
Product: [Retired] Red Hat Linux Reporter: advax
Component: linuxconfAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: monica
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:47:39 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 advax 2000-04-05 00:15:38 UTC
Want to create a route on a specific interface for use with proxy arp

e.g.
/etc/sysconfig/static_routes needs an entry like:
eth1 host 142.90.n.n
which is handled by /etc/sysconfig/network-scripts/ifup-routes

Linuxconf cannot make this, and does not parse an existing entry
under "routing and gateways".

Andrew

Comment 1 monica 2000-06-04 05:29:20 UTC
Every time I use Linuxconf to edit any parameter, my routing table is EMPTIED, 
with the exception of the localhost.  I then lose all network and internet 
connectivity, and it is impossible to add a route via the route daemon.  The 
only solution I have found is to use netconfig.  HOWEVER, watch out because the 
default gateway and nameserver are auto-filled incorrectly!

Comment 2 Brent Fox 2002-06-05 16:17:52 UTC
Closing because we don't ship linuxconf anymore

Comment 3 Red Hat Bugzilla 2006-02-21 18:47:39 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.