From the module load order, I infer that the tulip card (the LinkSys) is intended to be eth0, and the 3Com eth1. You might want to verify that this is what happens, though, since if *either* module fails to find a suitable NIC, the remaining NIC will be associated with eth0 and there will be no eth1.

Subject to that uncertainty, I'm guessing that the 3c59x module is not finding the 3C595 NIC. This is not a model I am familiar with, so the fist thing you should do is verify that 3c59x.o actually supports it. Assuming it does, try running from the command line "insmod 3c59x" and see what error (if any) insmod returns. If you get no error, then use "ip -v link" to see if eth1 has been created.

Until you get the eth1 interface created, then configured, there is no point mucking around with dhcpd settings.

PS -- when posting error messages, please report them a bit more cleanly -- use quotes when you are quoting or, better, put them on their own lines, instead of running them into your commentary. Also, it helps if you quote a bit more verbosely ... give us some context for the lines you think are important by including what comes right before and right after them (they often contain information that you do not realize is also important for troubleshooting).

At 09:23 AM 10/25/02 -0700, Craig wrote:
Hi folks,
I trying to set up a new box using the new Bering 1.04, and I'm using a
Linksys LNE100TX and a 3Com 3C595-TX. My IP address is assigned
dynamically to me by my ISP (I have AT&T Broadband), and I'm trying to
use DHCP for my LAN. Here's what I have done:

1.) Uncommented the appropriate drivers. When Bering boots - I see:

Loading modules:
tulip - 3c59x - Using /lib/modules/3c59x.o

2.) Edited the syslinux.cfg file, and added the dhcpd entry.
3.) Edited the /etc/shorewall/interfaces file and added the "dhcp" entry
(without the quotes, of course) on the eth1 line under the OPTIONS
category.

As Bering boots, when it get to the point where it says "Configuring
network interfaces" I see the error message...Operation not supported by
device, and then as Bering finishes booting, I see a Device "eth1" does
not exist error message. When Bering finally boots, I typed ps ax and I
see: pump -i eth0, but I don't see any reference to dhcpd or eth1.
Suggestions???



--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------



-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
------------------------------------------------------------------------
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

Reply via email to