(1) To confirm the MAC addresses of eth0 and eth1.
Good manufacturers such as 3COM, Intel,
SMC, Sohoware, D-Link, Netgear,
US Robotics
and others
have the MAC addresses clearly labeled on the cards.
Boot up LRP firewall, login as root,
q to drop to the
# prompt,
type
ip address, the funny looking number after
link/ether is the MAC address
 |
MAC address | ip address shows | conclusion |
| card A: assumed to be eth0 | |||
| card B: assumed to be eth1 |
If you cannot see eth0 or eth1 with
ip address,
type lsmod
, the bottom few lines tell you the name of the network
driver loaded.
Click here to return to main page
---------- below are special cases ------------
If card A and card B are of different make/type, then the order of
eth0 and eth1 is determined completely by
the order in which the modules are loaded.
Power up firewall, login as root,
3-packages, 2-modules,
1-modules, in the Ethernet cards section,
the order which the driver is listed is important, the first valid driver loaded
is eth0.
If you use ISA card and IO addresses other than 300 and 320, then you need
to modify the
"io=0x300,0x320" parameter accordingly.
Dependency:
If you use ne, wd, or smc-ultra driver, make sure
8390 is loaded first.
If you
use 3c59x, eepro100, epic100, rtl8139, sundance, tulip, via-rhine or winbond-840
driver, make sure pci-scan is loaded first.
If you use ne2k-pci driver, make sure 8390 and
pci-scan are loaded first.
After you made changes, Ctrl-S and Enter to save, Ctrl-C, q twice, B-for backup, 5-modules.
If you want to know which drivers are loaded, at the
# prompt
type lsmod
, the bottom few lines will tell you what modules are loaded. This is helpful
in
troubleshooting in cases where you suspect the network drivers are not loaded.