Re: Setting up eth1 interface
Sean Norris,,, [EMAIL PROTECTED] writes: Thanks for the really quick replies. Bud Rogers wrote: You probably need to add static to that line. And you will need to add at least address and netmask entries for that interface. Man interfaces for details. iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 I added these lines and the static option ( thanks for the man reference ). However, I still get the same error when I use #ifup eth1. Leen Besselink wrote: Are you sure the module loaded ? sounds like some kind of driver problem. 'lsmod' will tell you more about that, also you could take a look at the output of 'dmesg'. Maybe that will tell you what went wrong. Hope this helps. I am as sure as I can be with my experience. That is, I have full web access and am sending this email over the eth0 card with that module. I did #lsmod Module Size Used by loop7808 0 (unused) tulip 30680 1 sound 57356 0 (unused) soundlow 344 0 [sound] No errors were found when I looked at dmesg. So what type of card is your second ethernet adapter? Unless you're using one whose driver is built into the kernel there isn't a kernel module being loaded for it. If it's a tulip based card, like your original, then you should see: Module Size Used by tulip 30264 2 Note the 2 under Used by. This is the setup I have and I didn't have to do anything for the tulip module to recognize the second ethernet card. Gary
re: setting up eth1 interface
###network modules alias eth0 tulip alias eth1 tulip What if you added the right IO, to the lines above ? Did you try that ? Although I'm not sure, as far as I could tell that module didn't have options. #options tulip io=0x400,0x800 This was for both cards right ? The options line is now commented out since neither card would work with that line. modprobe -v eth1 was silent, no errors or messages in /var/log/messages If it's silent that meant it didn't do anything. Maybe you need a different driver then the Tulip one, otherwise I would think he'd find it (especially if you added the IO-parameters). If you run out of ideas I found an other one: compile into the kernel and add this to your lilo: ether=0,0,0,0 eth0 ether=0,0,0,eth1 or something like that. Also did you try looking at the diagnostic program at his webpage ? http://www.scyld.com/network/tulip.html And you could also try downloading the latest driver there. Compile that and try it. BTW, what happends if you haven't inserted the module yet (there is no eth0) and the insert with the right options to find eth1 ? Other ideas, not yet, maybe later. ;) (I'm sure this can work in some way). Now I've gotta go and shower and get to work fast, Lennie.
Re: Setting up eth1 interface
What you need is load the module twice ! One for each NIC. I have that setup on my LAN as I use 2 ne2000 clones : (You will have to adapt this to your tulip module) First edit the /etc/modutils/aliases file and add : -- cut here -- # Aliases for using twice the ne2000 module (ne) alias ne0 ne alias ne1 ne -- cut here -- Then create a file /etc/modutils/ne to specifiy options : -- cut here -- options ne0 io=0x300 irq=10 -o ne0 options ne1 io=0x280 irq=15 -o ne1 -- cut here -- (the trick is to actually rename each module with a name neX ( -o neX ) Then here is /etc/network/interfaces : -- cut here -- # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # ADSL interface auto eth0 iface eth0 inet static address 10.0.0.10 netmask 255.255.255.0 network 10.0.0.0 broadcast 10.0.0.255 up /etc/network/ipchains.rules # Local network auto eth1 iface eht1 inet static address 192.168.1.1 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 -- cut here -- Maybe that should be documented in some FAQ because I haven't found any easy-to-find doc about that besides looking in the kernel doc how to load modules and rename them. Silver - Original Message - From: Sean Norris,,, [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Thursday, November 23, 2000 7:23 PM Subject: Setting up eth1 interface Hello All, I have been trying to set up a small local network with a linux box as a gateway and my wife's win98 laptop. I am running potato with a fresh 2.2.17 kernel from kernel.org. Currently, a D-link DE-530TX is working well with a tulip driver loaded as a module to connect to my cable modem. The second NIC is a linksys LNE-100TX ver. 4.0, which also uses the tulip driver. However, I cannot get the eth1 interface to initialize. #ifconfig eth1 10.0.0.1 netmask 255.0.0.0 up SIOCSIFADDR: No such device eth1: unknown interface: No such device SIOCSIFNETMASK: No such device eth1: unknown interface: No such device In my /etc/network/interfaces file there is no entry for eth1. eth0 is : iface eth0 inet dhcp so I tried adding : iface eth1 inet Now with #ifup eth1, I get the error /etc/network/interfaces: too few parameters for iface line So, I think that I am almost there I just cannot find any information on what options should be on that line. Or am I not really supposed to be editing that file directly? Any help would be appreciated. Thanks in advance. Sean [EMAIL PROTECTED]
Re: Setting up eth1 interface
Hello all, This is just to thank all those who offered advice. I finally managed to bring up the eth1 interface. I tried all the suggestions, aliases with a single tulip driver, aliases with 2 tulip drivers, compiled the tulip driver into the kernel and passed ether arguments with lilo. Obviously, the last thing I tried, adding a tulip module when tulip was already compiled in the kernel, worked. As a theoretical question, why can't the tulip driver that is compiled into the kernal recognize both cards? From http://www.securityportal.com, I understand there are some security concerns with having a kernel load modules, so shouldn't you be able to support 2+ cards with a monolithic kernel? Anyway, all is working. Thanks again. On to setting up samba. Sean
Re: Setting up eth1 interface
On Thursday 23 November 2000 12:23, Sean Norris,,, wrote: In my /etc/network/interfaces file there is no entry for eth1. eth0 is : iface eth0 inet dhcp so I tried adding : iface eth1 inet Now with #ifup eth1, I get the error /etc/network/interfaces: too few parameters for iface line So, I think that I am almost there I just cannot find any information on what options should be on that line. Or am I not really supposed to be editing that file directly? You probably need to add static to that line. And you will need to add at least address and netmask entries for that interface. Man interfaces for details. iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 -- Bud Rogers [EMAIL PROTECTED] http://www.sirinet.net/~budr/zamm.html All things in moderation. And not too much moderation either.
Re: Setting up eth1 interface
On Thu, 23 Nov 2000, Sean Norris,,, wrote: Hello All, I have been trying to set up a small local network with a linux box as a gateway and my wife's win98 laptop. I am running potato with a fresh 2.2.17 kernel from kernel.org. Currently, a D-link DE-530TX is working well with a tulip driver loaded as a module to connect to my cable modem. The second NIC is a linksys LNE-100TX ver. 4.0, which also uses the tulip driver. However, I cannot get the eth1 interface to initialize. #ifconfig eth1 10.0.0.1 netmask 255.0.0.0 up SIOCSIFADDR: No such device eth1: unknown interface: No such device SIOCSIFNETMASK: No such device eth1: unknown interface: No such device Are you sure the module loaded ? sounds like some kind of driver problem. 'lsmod' will tell you more about that, also you could take a look at the output of 'dmesg'. Maybe that will tell you what went wrong. Hope this helps.
Re: Setting up eth1 interface
Thanks for the really quick replies. Bud Rogers wrote: You probably need to add static to that line. And you will need to add at least address and netmask entries for that interface. Man interfaces for details. iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 I added these lines and the static option ( thanks for the man reference ). However, I still get the same error when I use #ifup eth1. Leen Besselink wrote: Are you sure the module loaded ? sounds like some kind of driver problem. 'lsmod' will tell you more about that, also you could take a look at the output of 'dmesg'. Maybe that will tell you what went wrong. Hope this helps. I am as sure as I can be with my experience. That is, I have full web access and am sending this email over the eth0 card with that module. I did #lsmod Module Size Used by loop7808 0 (unused) tulip 30680 1 sound 57356 0 (unused) soundlow 344 0 [sound] No errors were found when I looked at dmesg. tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED] eth0: Digital DC21041 Tulip rev 33 at 0xc400, 00:80:C8:6C:61:3C, IRQ 5. eth0: 21041 Media table, default media 0800 (Autosense). eth0: 21041 media #0, 10baseT. eth0: 21041 media #4, 10baseT-FD. eth0: 21143 10baseT link beat good. eth0: 21143 10baseT link beat good. However, there were some errors that flew by at boot that are not there. From what I saw they were modprobe errors complaining about my lp module. How can I see the complete log of what flashes by at boot? I looked at the man dmesg, but the -n switch just returned no messages at all. I had some trouble with modules but I thought that had been resolved with a fresh install this morning and the recompiled kernel from fresh sources. ( I have been fighting with this problem on and off for over a month, but I will fix it today if the coffee holds out) By the way, I have a gnome ( with helix gnome ) desktop. Currently, using Mozilla for mail since my local mail also isn't yet working. Is there a way to directly send standard output to the gnome clipboard instead of dmesg dmesg.txt and then cutting from there? Thanks Sean
re: setting up eth1 interface
Still no luck, Leen Besselink wrote: a good idea could be is make a modules alias for each card (I think it goes in /etc/modutils/aliases): alias eth0 de4x5 alias eth1 3c59x or whatever you need. This could also help... (then just do: modprobe -v eth0 modprobe -v eth1 ) Hope this helps, Lennie. - New things are always on the horizon. added some aliases to /etc/modutils/aliases, ran update-modules and the right lines appeared in modules.conf, then depmod -a ###network modules alias eth0 tulip alias eth1 tulip #options tulip io=0x400,0x800 The options line is now commented out since neither card would work with that line. modprobe -v eth1 was silent, no errors or messages in /var/log/messages still when I try to bring up eth1 I get the following message #ifconfig eth1 10.0.0.1 netmask 255.0.0.0 up SIOCSIFADDR: No such device eth1: unknown interface: No such device SIOCSIFNETMASK: No such device eth1: unknown interface: No such device I don't know what else to try, except compiling the tulip driver into the kernel. Would that make a difference? I tried compiling the tulip.c from Linksys but it wouldn't compile. Struggling on, any help appreciated. Sean
Re: Setting up eth1 interface
Sean Norris,,, [EMAIL PROTECTED] writes: Hello All, I have been trying to set up a small local network with a linux box as a gateway and my wife's win98 laptop. I am running potato with a fresh 2.2.17 kernel from kernel.org. Currently, a D-link DE-530TX is working well with a tulip driver loaded as a module to connect to my cable modem. The second NIC is a linksys LNE-100TX ver. 4.0, which also uses the tulip driver. I had a similar problem when I had two ne2000 (clones) in my machine. Obviously, the module (not compiled in the kernel!) couldn't handle two nics right away. Now I use one ne2000-isa and one pci. The problem was, that the module ne was already in use when I wanted to load the second module for the second card. Solution was to compile ne into the kernel and load ne-pci as a module (or vice versa). -- Tschoe, Jens
