What I *think* is going on is simply that the eth0 interface is not being created because you are not loading the module(s) needed to detect and initialize the NIC. At the least, this is the 3c589_cs.o; it includes anything that module depends on. It has (they have) to be in /etc/modules, and if there is more than one, they have to be in the right order.
Based on the details in this message of yours and the one Richard posted, I **think** you need to edit /etc/modules to read something like this (my edits are not indented):
# /etc/modules: kernel modules to load at boot time. # ISA ethernet cards
# PCI ethernet cards # should the 3c589_cs.o be declared here? <-------------
pcmcia_core ds. 3c589_cs
# Modules needed for PPP connection slhc ppp_generic ppp_async # The three following modules are not always needed #zlib_inflate #zlib_deflate #ppp_deflate
# Masquerading 'helper' modules # Other modules available in bering/modules/net/ipv4/netfilter ip_conntrack_ftp ip_conntrack_irc ip_nat_ftp ip_nat_irc
insmod'ing the modules in this order should cause the card to be detected and the eth0 interface created ... although in saying this I rely on your identifying this module as the right one for the card and on the depmod info in Richard's message being correct. All your other symptoms are secondary, caused by the eth0 interface not existing. Once it exists, other problems may turn up with your setup ... but until the interface exists, neither we nor you can even begin to evaluate that part of your configuration.
BTW, the order of packages in syslinux.cfg has nothing to do with this problem. The order of modules ... and the completeness of the list ... in /etc/modules has everything to do with it.
Digression into background: full-strength Linux systems almost universally use modprobe to install modules. modprobe takes care of module dependencies for you, loading what is needed for the named modules. Small distros like LEAF typically use the smaller program insmod, which does not do dependency checking for you. So someone coming to LEAF from Red Hat or Debian needs to adjust his or her thinking a bit to get this stuff rght.
Hope this helps. Good luck.
At 08:19 PM 6/9/2003 -0600, Greg Playle wrote:
[details deleted]My thanks to Tom Eastep and Ray Olszewski, who pointed out some information that would help.
I'm working on LEAF Bering 1.2, using a PPP serial modem (as ppp0) and a PCMCIA NIC as eth0 for the internal network. The host is a Toshiba Satellite Pro 460CDX laptop (recycled). The NIC is an older 3Com EtherLink III 3C589D based card (recycled).
At boot, the firewall gives an error message of: Masquerade: Error: Unable to determine the routes through eth0
Tom suggested the interface isn't up before Shorewall starts, and that seems reasonable. Ray suggested there was a configuration error, and that seems highly likely, as I'm still learning.
Pinging the firewall from the internal network, to the default IP of 192.168.1.254 "Destination Host Unreachable".
I think I've failed to declare something associated with the PCMCIA cards--I'm not sure where the declaration of the 3c589 driver goes--the documentation isn't clear.
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
