RE: [leaf-user] Errors--Route through eth0?
Richard: I'll be glad to share what I learn as I go, and I planned on sending lessons-learned back to the list / primary producers of LEAF. You pointed me in the right track, but it turned out the 3c589_cs CANNOT be called from within the /etc/modules. Instead, the 3c589 driver needs moved to the /lib/modules/pcmcia, then the pcmcia package backed up. Upon load, the OS automatically loads these modules, in module-dependent order. That got eth0 working, at least from the firewall's view. I'm still checking the eth0 service to make sure I understand what's available / works there. Best wishes, -Original Message- From: Richard Doyle [SMTP:[EMAIL PROTECTED] Sent: Monday, 09 June, 2003 21:03 To: '[EMAIL PROTECTED]' Subject:Re: [leaf-user] Errors--Route through eth0? On Mon, 2003-06-09 at 19:19, Greg Playle wrote: 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 snip # /etc/modules: kernel modules to load at boot time. # ISA ethernet cards # PCI ethernet cards # should the 3c589_cs.o be declared here? - Yes. You can insert the module on a running system with insmod 3c589_cs I'm very interested in your progress on this project, as I'm about to try something rather similar in the next few weeks. Good luck! --- 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 --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 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
Re: [leaf-user] Errors--Route through eth0?
On Mon, 2003-06-09 at 19:19, Greg Playle wrote: 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 snip # /etc/modules: kernel modules to load at boot time. # ISA ethernet cards # PCI ethernet cards # should the 3c589_cs.o be declared here? - Yes. You can insert the module on a running system with insmod 3c589_cs I'm very interested in your progress on this project, as I'm about to try something rather similar in the next few weeks. Good luck! --- 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
RE: [leaf-user] Errors--Route through eth0?
Please reply to the list. On Mon, 2003-06-09 at 20:49, Greg Playle wrote: I guess I'm a bit puzzled at this. The messages at boot appear to indicate that insmod is throwing unresolved symbol errors when it tries to load 3c589_cs. The things it's trying to refer to appear to be the modules loaded by the pcmcia modules. Later, the load messages show the pcmcia modules loading, but of course, 3c589 isn't working. Should the pcmcia call in syslinux.cfg precede the call to modules.lrp? Well, I haven't used pcmcia with LEAF yet, but yes, the pcmcia drivers (ds and pcmcia_core) must be loaded before the 3c589 driver, as shown by modules.dep: /lib/modules/2.4.20/pcmcia/3c589_cs.o: /lib/modules/2.4.20/pcmcia/ds.o \ /lib/modules/2.4.20/pcmcia/pcmcia_core.o /lib/modules/2.4.20/pcmcia/ds.o:/lib/modules/2.4.20/pcmcia/pcmcia_core.o /lib/modules/2.4.20/pcmcia/pcmcia_core.o: -Richard --- 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
Re: [leaf-user] Errors--Route through eth0?
This is all a bit muddled in my mind, Greg, and the message from Richard Doyle -- which appears to be in reply to something you wrote that I have not seen yet -- confuses me a bit more. 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: 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. [details deleted] --- 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
Re: [leaf-user] Errors--Route through eth0?
On Sun, 08 Jun 2003 15:51:36 -0700, Ray Olszewski [EMAIL PROTECTED] wrote: At 04:12 PM 6/8/2003 -0600, Greg Playle wrote: I'm working a simple, serial-modem / single network (ppp0 eth0) setup. Which LEAF variant? It's impossible even to begin giving any sort of detailed advice without knowing if it's Dachstein, Bering, or what. At boot, one of the last messages before login is: Masquerade: Error: Unable to determine the routes through eth0 Since you have a ppp setup, eth0 is presumably your LAN interface. Without context, this message is hard to interpret, but it make me suspect that you missed some setting and the system thinks that eth0 is the external interface. This is only a guess, though. This message usually means that the internal interface isn't up when Shorewall starts. Shorewall examines the routing table to understand what addresses need to be masqueraded. -Tom -- Tom Eastep\ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ [EMAIL PROTECTED] --- 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
