Bug 594499 - Anaconda bad handling of second ethernet adapter
Summary: Anaconda bad handling of second ethernet adapter
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-20 20:43 UTC by Raman Gupta
Modified: 2010-05-25 19:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-25 19:50:57 UTC
Type: ---

Attachments (Terms of Use)

Description Raman Gupta 2010-05-20 20:43:02 UTC
Description of problem:

I have two ethernet adapters, eth0 and eth1. The first is the built-in
motherboard adapter which I don't use (nothing is plugged in) and the second is
an Intel gigabit add-on controller card.

I have nothing plugged into eth0. My network is plugged into eth1.

During the anaconda fresh net install (not an upgrade), it was able to download
the stage2 image but once it got to the point of connecting to a yum repository
it failed -- the network connection was unavailable.

I was able to continue by switching to another virtual console and manually

ip route flush all
ip route add dev eth1
ip route add default via

At this point the network routed via the correct adapter, all was well, and I
was able to continue the anaconda install.

Comment 1 Chris Lumens 2010-05-25 04:15:55 UTC
Please attach /tmp/anaconda.log and /tmp/syslog from the point when you hit this problem to this bug report.

Comment 2 Raman Gupta 2010-05-25 19:33:32 UTC
Unfortunately, they have been removed by tmpwatch.

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