Bug 74918
| Summary: | Adding second NIC to same network segment disables first NIC | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Tom Wood <woodt> | ||||
| Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | Ben Levenson <benl> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.0 | CC: | ahabig, kheal, rvokal | ||||
| 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: | 2005-09-29 20:19:27 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: | |||||||
| Attachments: |
|
||||||
|
Description
Tom Wood
2002-10-02 19:47:58 UTC
Created attachment 78224 [details]
diagnostic commands run to illustrate the problem (with inline commentary)
The same situation exists with stock 2.4.19 and 2.4.20-pre8 kernels. ifup and ifdown are part of the initscripts, so i reassign it to the proper component. But agreed, this is not the 'desired' behaviour. :-) You should be able to get the 'correct' behaviour for your test setup with 2 nics in the same system on the same subnet using the ip and route commands manually. Read ya, Phil Phil, I've tried exactly what you suggest with manually setting routes. That doesn't help. The first NIC gets creamed by the second's presence. Nothing I can think of will restore the routing, even though netstat -r looks fine. That's why I thought this was kernel related. I bumped into this too, but the problem doesn't depend on being on the same network segment. My configuration is a standard ip-masq'ing one: eth0 - DHCP assigned parameters, talks to world eth1 - static interface to private 192.168.1. net Even with explicitly stating DEFROUTE=no in the ifcfg-eth1, bringing up the eth1 interface clobbers the eth0 routing to the world. Worked fine in 7.3 and previous releases. My problem isn't limited to being on the same network either. It's just that my initial configuration had both NICs on the same segment. Whatever interface comes up last wins the battle and kills its opponents. I found a work-around for my problem. Somehow, a GATEWAY definition had found its way into my ifcfg-eth1 file. Removing this seems to have removed the ifup script's desire to add a new default route. This doesn't solve the bug though, the scripts should not ignore DEFROUTE=no and should not clobber existing routes. Not sure how the GATEWAY line got in there - it was bogus (the little local subnet has none) and isn't in my other 7.3 machines. I don't know if it was in this machine's file before the upgrade to 8.0 or if the upgrade was trying to be helpful. I have not run any net configuration scripts, I just edit the files myself. Closing bugs on older, no longer supported, releases. Apologies for any lack of response. If this persists on a current release, such as Fedora Core 4, please open a new bug. |