Olaf Hering wrote:
On Mon, Jun 04, hysterion wrote:
Hub ---------------- 7300 --- Modem --- WEB.
You dont need two ethernet cards, you need two interfaces.
Hub ---- eth0 -7300- ppp0 - Modem --- Web.
So you have to MASQ the ppp0 interface. This eth0 is the gateway for all iMacs.
Thanks, and my apologies for not being clearer: by modem I meant a *cable* modem, hence the perceived need for a second Ethernet card on this (Power Mac) 7300. Now I'm trying to follow this suggestion (from comp.os.linux.powerpc): Brian Victor writes:
1) Do I understand correctly?
Yes. Your diagram could be put in a textbook. ;)
2) If yes, I need to add a Network card in one the 7300's PCI slots. What's a good choice? (Price, Linux support,...)
I had success with the $20 Netgear FA311. http://lists.linuxppc.org/listarcs/linuxppc-user/200105/msg00158.html
I got the card yesterday, and have been trying to get it recognized today... to no avail yet. Not sure where the crux lies, so I've tried to include all relevant messages below. Further help would be greatly appreciated - I have 14 days to get this card working, or return it and try another. (Suggestions still welcome!) Thanks again, hysterion ========================== Kernel: 2.2.16 from SuSE Linux 7.0 PPC. Machine: Power Mac 7300/180. Netgear FA311 installed in one of the PCI slots. Goal: get it recognized as eth1 (eth0 is the built-in card). 1) Following http://www.scyld.com/network/updates.html (section "Drivers may be updated individually..."), I downloaded these to a directory /usr/src/modules/: natsemi.c kern_compat.h pci-scan.c pci-scan.h I do have the necessary file /usr/include/linux/version.h . 2) Compilation produces natsemi.o and pci-scan.o, but with these warnings: $ gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c natsemi.c In file included from natsemi.c:107: /usr/include/linux/string.h:28: warning: conflicting types for built-in function `memset' /usr/include/linux/string.h:29: warning: conflicting types for built-in function `memcpy' /usr/include/linux/string.h:32: warning: conflicting types for built-in function `memcmp' $ gcc -DMODULE -D__KERNEL__ -DEXPORT_SYMTAB -Wall -Wstrict-prototypes -O6 -c pci-scan.c In file included from /usr/include/linux/signal.h:64, from /usr/include/linux/sched.h:23, from /usr/include/linux/mm.h:4, from pci-scan.c:60: /usr/include/linux/string.h:28: warning: conflicting types for built-in function `memset' /usr/include/linux/string.h:29: warning: conflicting types for built-in function `memcpy' /usr/include/linux/string.h:32: warning: conflicting types for built-in function `memcmp' 3) "Testing the module": pci-scan.o loads, but *not* natsemi.o: $ insmod -v pci-scan.o Using pci-scan.o Symbol version prefix '' $ insmod -v natsemi.o Using natsemi.o Symbol version prefix '' natsemi.o: init_module: Device or resource busy Hint: this error can be caused by incorrect module parameters, including invalid IO or IRQ parameters $ lsmod Module Size Used by pci-scan 3408 0 ipv6 121832 -1 (autoclean) memstat 1960 0 (unused) $ dmesg (...) natsemi.c:v1.07 1/9/2001 Written by Donald Becker <becker@scyld.com> http://www.scyld.com/network/natsemi.html 4) At no point does the card trigger an LED on my hub, nor appear in ifconfig nor in cat /proc/net/dev. On reboot I get boot messages like these: (...) eth0: MACE at 00:05:02:a8:78:12, chip revision 25.64 (...) Setting up network device eth0 done Setting up network device eth1 SIOCSIFADDR: No such device eth1: unknown interface: No such device SIOCSIFBRDADDR: No such device eth1: unknown interface: No such device SIOCSIFNETMASK: No such device eth1: unknown interface: No such device failed (...) 5) For the record, I have config files as follows: $ more /etc/rc.config (...) # networking # # number of network cards: "_0" for one, "_0 _1 _2 _3" for four cards # NETCONFIG="_0 _1" (...) IPADDR_0="192.168.0.99" IPADDR_1="192.168.0.100" (...) NETDEV_0="eth0" NETDEV_1="eth1" (...) IFCONFIG_0="192.168.0.99 broadcast 192.168.0.255 netmask 255.255.255.0 up" IFCONFIG_1="192.168.0.100 broadcast 192.168.0.255 netmask 255.255.255.0 up" (...) $ more /etc/modules.conf (...) # Aliases - specify your hardware alias eth0 off alias eth1 off (...) ==========================