Bug 63932 - firewall NIC selection eth0
firewall NIC selection eth0
Status: CLOSED NOTABUG
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
skipjack-beta1
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-04-22 03:14 EDT by John Sheahan
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-04-22 03:14:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Sheahan 2002-04-22 03:14:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020311

Description of problem:
Installed skipjack - 1 on a 2 NIC box.
Nic's are different types, specifically one uses
tulip.o and other 8139too.o modules.
When configuring these interfaces at boot,  I want to select which one is eth0.
skipjack got them the wrong way around in modules.conf

Version-Release number of selected component (if applicable):


How reproducible:
Didn't try

Steps to Reproduce:
1. install on 2 nic box, where nic's use different modules 
2. note modules.conf will contain 2 alias lines 
3. even chance they are wrong way around.
	

Expected Results:  Like to select which module corresponds to eth0 on the tabbed
install form.

Additional info:
Comment 1 Jeremy Katz 2002-04-22 10:10:56 EDT
Boot with 'linux noprobe' if you want to manually load modules to specify the
order.  Defaults are based on PCI bus ordering which is as correct of a way as
you can get.

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