Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
Adam Aube wrote: On Thursday 05 February 2004 12:06 pm, Joseph Jones wrote: Adam Aube wrote: Your interfaces file looks fine. Exactly what happens when you try to get your network interface working, and how do you try to do it? I try to get it working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. Sounds like a driver problem to me. What does the output of lspci -vv show? Adam Output follows (hope you don't mind me cc'ing to you and the list): 00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev b2) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Region 0: Memory at f800 (32-bit, prefetchable) [size=64M] Capabilities: [40] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none Capabilities: [60] #08 [2001] 00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2) Subsystem: nVidia Corporation: Unknown device 0c11 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- 00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2) Subsystem: nVidia Corporation: Unknown device 0c11 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- 00:00.3 RAM memory: nVidia Corporation: Unknown device 01aa (rev b2) Subsystem: nVidia Corporation: Unknown device 0c11 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- 00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev c3) Subsystem: nVidia Corporation: Unknown device 0c11 Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Capabilities: [50] #08 [01e1] 00:01.1 SMBus: nVidia Corporation nForce PCI System Management (rev c1) Subsystem: nVidia Corporation: Unknown device 0c11 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 5 Region 0: I/O ports at 5000 [size=16] Region 1: I/O ports at 5500 [size=16] Region 2: I/O ports at 5100 [size=32] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:02.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) (prog-if 10 [OHCI]) Subsystem: nVidia Corporation: Unknown device 0c11 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 10 Region 0: Memory at e680 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:03.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) (prog-if 10 [OHCI]) Subsystem: nVidia Corporation: Unknown device 0c11 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 10 Region 0: Memory at e600 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.0 Ethernet controller: nVidia Corporation nForce Ethernet Controller (rev c2) Subsystem: Asustek Computer, Inc.: Unknown device 0c11 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 (250ns min, 5000ns max) Interrupt: pin A routed to IRQ 10 Region 0: Memory at e580 (32-bit,
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
Joseph Jones wrote: Adam Aube wrote: On Thursday 05 February 2004 12:06 pm, Joseph Jones wrote: I try to get [the network] working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. Sounds like a driver problem to me. What does the output of lspci -vv show? Adam Output follows (hope you don't mind me cc'ing to you and the list): 00:04.0 Ethernet controller: nVidia Corporation nForce Ethernet Controller (rev c2) Subsystem: Asustek Computer, Inc.: Unknown device 0c11 All the Unknown device lines I see indicate to me that your hardware is too new for your kernel to recognize it. What kernel are you running (uname -a)? You might want to upgrade to a newer kernel: apt-cache search kernel-image-2.[whatever, such as 4] find a kernel that matches what you need, for example kernel-image-2.4.24-1-k7 for a 2.4.24 Athlon-tweaked kernel, and install it with a command like: apt-get install kernel-image-2.4.24-1-k7 follow the on-screen instructions reboot If all goes well, hopefully you'll now have networking. Of course, this assumes you have a newer kernel in your apt sources (probably CD?). If not, you may need to try setting up dial-up and grabbing the new kernel via ppp. Or you can boot into Knoppix/Morphix/etc, and if it sees your network, manually download the kernel image and any dependencies (quite painful, but I've done it at least twice) and install them with dpkg -i package_name. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
Joseph Jones wrote: I'm using a custom 2.4.22 kernel with the forcedeth (the reverse engineered driver for my onboard adaptor) patch applied. I'm unfamiliar with this option, but I do recall seeing something about this option in the past couple of days (maybe it was even part of this thread) and I have a vague recollection of it having to do with some sort of bug in the option. If it wasn't part of this thread and you're unaware of what was mentioned, you might want to check the archives for the past couple of days. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
Kent West wrote: Joseph Jones wrote: Adam Aube wrote: On Thursday 05 February 2004 12:06 pm, Joseph Jones wrote: I try to get [the network] working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. Sounds like a driver problem to me. What does the output of lspci -vv show? Adam Output follows (hope you don't mind me cc'ing to you and the list): 00:04.0 Ethernet controller: nVidia Corporation nForce Ethernet Controller (rev c2) Subsystem: Asustek Computer, Inc.: Unknown device 0c11 All the Unknown device lines I see indicate to me that your hardware is too new for your kernel to recognize it. What kernel are you running (uname -a)? You might want to upgrade to a newer kernel: apt-cache search kernel-image-2.[whatever, such as 4] find a kernel that matches what you need, for example kernel-image-2.4.24-1-k7 for a 2.4.24 Athlon-tweaked kernel, and install it with a command like: apt-get install kernel-image-2.4.24-1-k7 follow the on-screen instructions reboot If all goes well, hopefully you'll now have networking. Of course, this assumes you have a newer kernel in your apt sources (probably CD?). If not, you may need to try setting up dial-up and grabbing the new kernel via ppp. Or you can boot into Knoppix/Morphix/etc, and if it sees your network, manually download the kernel image and any dependencies (quite painful, but I've done it at least twice) and install them with dpkg -i package_name. I'm using a custom 2.4.22 kernel with the forcedeth (the reverse engineered driver for my onboard adaptor) patch applied. However, it occurs to me that my USB also appears not to be working, which also has Unknown Device 0c11 for it's subsystem. Could we have found te answer? Maybe, maybe not... Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
On Fri, Feb 06, 2004 at 09:52:36AM -0600, Kent West said Joseph Jones wrote: Output follows (hope you don't mind me cc'ing to you and the list): 00:04.0 Ethernet controller: nVidia Corporation nForce Ethernet Controller (rev c2) Subsystem: Asustek Computer, Inc.: Unknown device 0c11 All the Unknown device lines I see indicate to me that your hardware is too new for your kernel to recognize it. What kernel are you running (uname -a)? No, it means lspci is out of date; the kernel and lspci use different databases to convert the ID codes to names. -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: Soviet nitrate genetic quarter Ortega undercover NSA signature.asc Description: Digital signature
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
On Thu, Feb 05, 2004 at 02:39:34AM +, Joseph Jones said Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. If this isn't the problem, could someone suggest what is? The forcedeth patch installed cleanly, and appears to be trying to work. Many thanks Joe. /etc/network/interfaces follows: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) auto eth0 iface eth0 inet static address 192.168.8.21 netmask 255.255.255.0 network 192.168.8.0 broadcast 192.168.8.255 gateway 192.168.8.1 auto eth1 iface eth1 inet static address 192.168.8.33 netmask 255.255.255.0 network 192.168.8.0 broadcast 192.168.8.255 gateway 192.168.8.1 From the rest of the thread, it seems you're having hardware support problems, but your interfaces file is also setup incorrectly. Why are you trying to put both interfaces on the same network? They can't both be your default route (have gateway lines). If you do get both working with your kernel, you'll have to remove one of the auto lines from your config, since you can't bring these both up at the same time. -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: Blowpipe Ron Brown HAMASMOIS EuroFed Qaddafi ISEC Mossad signature.asc Description: Digital signature
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
Joseph Jones wrote: Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. If this isn't the problem, could someone suggest what is? The forcedeth patch installed cleanly, and appears to be trying to work. To bolster you, I'm running the onboard network interface (epox board 8rda+) with kernel 2.6.1 and the forcedeth patch. And it's working fine right after kernel compile. (I'd suggest, you remove the second network interface unless the internal one runs properly.) As I don't know your Linux skills, let me ask if there are any network related messages in the logs at /var/log/...? Another hint; if you didn't come across it yet: There's also a forum at http://www.nforcershq.com which specialized on nforce boards. Daniel PS: I cannot recommend this board at all. I have trouble with agp and sound eversince! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct (sorry I accidentally replied to you, Adam)
Adam Aube wrote: On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote: Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. If this isn't the problem, could someone suggest what is? The forcedeth patch installed cleanly, and appears to be trying to work. /etc/network/interfaces follows: [snipped] Your interfaces file looks fine. Exactly what happens when you try to get your network interface working, and how do you try to do it? Adam I try to get it working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct (sorry I accidentally replied to you, Adam)
On Thu, 2004-02-05 at 12:08, Joseph Jones wrote: Adam Aube wrote: On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote: Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. If this isn't the problem, could someone suggest what is? The forcedeth patch installed cleanly, and appears to be trying to work. /etc/network/interfaces follows: [snipped] Your interfaces file looks fine. Exactly what happens when you try to get your network interface working, and how do you try to do it? Adam I try to get it working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. It seems like the kernel doesnt support your your card, either because the driver isnt compiled in, or because you havn't inserted the module yet. If you comiled the driver as a module, make sure to load it using /etc/modules so that it is available at boot time. -davidc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct (sorry I accidentally replied to you, Adam)
Joseph Jones wrote: On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote: Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. I try to get it working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. I suspect you don't have the correct module loaded. Try running modconf and see if you can find the appropriate driver for your nforce board. Alternatively, if you know the correct module by name, you can simply modprobe module_name, and if testing shows the network to work, add this module name to /etc/modules. After either the modprobe or the modconf, you'll want to restart your networking with /etc/init.d/networking restart. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct (sorry I accidentally replied to you, Adam)
On 2004-02-05, Joseph Jones penned: Adam Aube wrote: On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote: Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. If this isn't the problem, could someone suggest what is? The forcedeth patch installed cleanly, and appears to be trying to work. /etc/network/interfaces follows: [snipped] Your interfaces file looks fine. Exactly what happens when you try to get your network interface working, and how do you try to do it? Adam I try to get it working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. Joe Does ctrl+s work on bootup to suspend the screen output and let you snag the full message? -- monique -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct (sorry I accidentally replied to you, Adam)
Kent West wrote: Joseph Jones wrote: On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote: Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. I try to get it working by starting up my PC. I was under the impression that that was all was requied after installing the kernel (it's all my Via Rhine based card needed). Upon bootup, it says something along the lines of eth1: ERROR while getting interface flags: No such device (dmesg has ceased to work for some reason, so I had to right it down as it flashed by) about 6 or so times. I suspect you don't have the correct module loaded. Try running modconf and see if you can find the appropriate driver for your nforce board. Alternatively, if you know the correct module by name, you can simply modprobe module_name, and if testing shows the network to work, add this module name to /etc/modules. After either the modprobe or the modconf, you'll want to restart your networking with /etc/init.d/networking restart. It's not compiled as a module. I applied the forcedeth patch to 2.4.22 and selected it in xconfig. Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. If this isn't the problem, could someone suggest what is? The forcedeth patch installed cleanly, and appears to be trying to work. Many thanks Joe. /etc/network/interfaces follows: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) auto eth0 iface eth0 inet static address 192.168.8.21 netmask 255.255.255.0 network 192.168.8.0 broadcast 192.168.8.255 gateway 192.168.8.1 auto eth1 iface eth1 inet static address 192.168.8.33 netmask 255.255.255.0 network 192.168.8.0 broadcast 192.168.8.255 gateway 192.168.8.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help, dual NICs, don't know whether this /etc/network/interfaces file is correct
On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote: Could someone just check over this for me please? I'm having no end of trouble trying to get my nforce's onboard interface working. If this isn't the problem, could someone suggest what is? The forcedeth patch installed cleanly, and appears to be trying to work. /etc/network/interfaces follows: [snipped] Your interfaces file looks fine. Exactly what happens when you try to get your network interface working, and how do you try to do it? Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dual NICs, same brand or not?
Damon Muller wrote: Quoth Ron Farrer, I'm building a firewall out of an old 486 and was wondering if it was best to use two NICs of the same type/brand or to use different ones? Is there any gotchas for doing one over the other? I find that's it's easier to use two different cards (not just different brands, but different chipsets) because you can easily dictate which one will be eth0 and eth1 in /etc/modules.conf. Using the same brands will certainly work, but you'll probably end up juggling them around to work out which one is which. AFAIK the order of the cards is determined by their position on PCI bus, isn't it? e.g. if you have: alias eth08139too alias eth1tulip you cannot just change it to: alias eth0tulip alias eth18139too can you? I have two same card and I just have: alias eth08139too alias eth18139too in modules.conf (really in in /etc/modutils/erik.eth) and I know that eth0 is dsl line and eth1 is home lan, to change this I would have to do HW change, not SW change, regardless of whether the cards are same or not, right? erik
Re: dual NICs, same brand or not?
Ron Farrer wrote: #include hello.h I'm building a firewall out of an old 486 and was wondering if it was best to use two NICs of the same type/brand or to use different ones? Is there any gotchas for doing one over the other? You will have to set the IO to different addresses for the cards, as long as you can do this using the same brand works fine. Using two different brands (or actually chips) you'll probably have to use two modules using more memory (not that I think it will matter much though). Perhaps you will need extra memory even if the cards use the same chip-type with different addresses, but I guess it will at least be less than having two different modules loaded. (Someone please comment this, or more generaly kernel modules memory usage...) Good luck // Emil TIA, Ron -- Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] Part 1.2Type: application/pgp-signature
Re: dual NICs, same brand or not?
Ron Farrer ([EMAIL PROTECTED]) wrote: #include hello.h I'm building a firewall out of an old 486 and was wondering if it was best to use two NICs of the same type/brand or to use different ones? Is there any gotchas for doing one over the other? Thanks to everyone that responded. It seems that eithe way will work. I will try using different brand/type NICs first. If that works well then I'll just leave it. Thanks again, Ron
dual NICs, same brand or not?
#include hello.h I'm building a firewall out of an old 486 and was wondering if it was best to use two NICs of the same type/brand or to use different ones? Is there any gotchas for doing one over the other? TIA, Ron -- Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] pgprVNANKEkhk.pgp Description: PGP signature
Re: dual NICs, same brand or not?
Quoth Ron Farrer, I'm building a firewall out of an old 486 and was wondering if it was best to use two NICs of the same type/brand or to use different ones? Is there any gotchas for doing one over the other? I find that's it's easier to use two different cards (not just different brands, but different chipsets) because you can easily dictate which one will be eth0 and eth1 in /etc/modules.conf. Using the same brands will certainly work, but you'll probably end up juggling them around to work out which one is which. cheers, damon -- Damon Muller :: Department of Criminology :: University of Melbourne The evil that men do lives after them; The good is oft interred with their bones; -- Julius Caesar
Re: dual NICs, same brand or not?
Damon Muller wrote: Quoth Ron Farrer, I'm building a firewall out of an old 486 and was wondering if it was best to use two NICs of the same type/brand or to use different ones? Is there any gotchas for doing one over the other? I find that's it's easier to use two different cards (not just different brands, but different chipsets) because you can easily dictate which one will be eth0 and eth1 in /etc/modules.conf. Using the same brands will certainly work, but you'll probably end up juggling them around to work out which one is which. I have an ether= line to the kernel at boot whether I use the same NICS or different ones. I like to always know which card is which. I learnt this the hard way once, I admin a firewall with 4 NICS in it, with 3 Brands (1 3Com Vortex, 1 Dec Tulip, 2 Intel EEPro100). One day after an apt-get upgrade and a kernel rebuild the cards shuffled themselves. Had a devil of a time sorting what was what (4! permutations), juggling leads (not the cards), while everyone around was screaming I need the network!! at me. John P Foster http://www.golden-orb.com
Re: dual NICs, same brand or not?
On Mon, Oct 15, 2001 at 01:06:29PM +1000, Damon Muller wrote: | Quoth Ron Farrer, | I'm building a firewall out of an old 486 and was wondering if it was | best to use two NICs of the same type/brand or to use different ones? Is | there any gotchas for doing one over the other? | | I find that's it's easier to use two different cards (not just different | brands, but different chipsets) because you can easily dictate which one | will be eth0 and eth1 in /etc/modules.conf. | | Using the same brands will certainly work, but you'll probably end up | juggling them around to work out which one is which. I have 2 tulip cards in this machine (it is my workstation and also gateway for DSL) and I could pick which was which by which PCI slot they were in. The kernel picks it based on the id number. I agree that using different chipsets (regardless of brand) is easier because you can set/switch it with aliases in /etc/modules.conf, but I haven't had any problems with this setup. -D
Re: dual NICs, same brand or not?
[Sun, Oct 14, 2001 at 07:44:52PM -0700] Ron Farrer :
best to use two NICs of the same type/brand or to use different ones?
Is there any gotchas for doing one over the other?
None at all, AFAIK. I am using an Intel Ether Pro+ and an RTL 8029A on
the router. The LAN consists of machines having Via-Rhine, Davicom and
WDC chipset cards.
Maybe at higher speeds this would make a difference, when the cards have
to be made to talk in full-duplex modes ?
--
GPG: 1024D/F1624A6E ragOO, VU2RGU
Helping to keep the Air-Waves FREE Amateur Radio
Helping to keep your Software FREE the GNU Project
Helping to keep the W W W FREE Debian GNU/${kernel}
Re: dual NICs
John Galt wrote: Wrong! eth0:1 and eth0:0... _Never_ say something's impossible... Especially when it is on _Linux_. Oki
Re: dual NICs
On Tue, 15 May 2001, Zac Epkes wrote: You can not have 1 NIC with 2 IPs simply not possible, i think u can buy network cards with upto 4 ports that all act alone, or something similar... Wrong! eth0:1 and eth0:0... _Never_ say something's impossible... - overid3 =) On Tuesday 15 May 2001 14:12, Matthew Sackman wrote: Hay all. Does anyone have any knowledge of a network card that has two independant eth ports on it? The reason I ask is that I've gotta get 4 eth ports into a server squashed into a 2U rack which means I only have 3 expansion cards available... I look forward to hearing from you! Matthew -- a mailto:[EMAIL PROTECTED]Who is John Galt?/a Failure is not an option. It comes bundled with your Microsoft product. -- Ferenc Mantfeld
[: Re: dual NICs]
- Forwarded message from - To: John Galt [EMAIL PROTECTED] Subject: Re: dual NICs On Wed, May 16, 2001 at 01:06:31AM -0600, John Galt wrote: On Tue, 15 May 2001, Zac Epkes wrote: You can not have 1 NIC with 2 IPs simply not possible, i think u can buy network cards with upto 4 ports that all act alone, or something similar... Wrong! eth0:1 and eth0:0... _Never_ say something's impossible... Um I'm getting slightly confused here: what I need is one card which has two or more independant eth ports on it which can be assigned seperate IPs. I.e. not IP aliasing - each eth port has only one IP address, but each eth port must appear to linux as a seperate eth port, appearing in effect as if I have 4x single eth NICs in the box. Is this possible with, say, 2 of the Intel Dual Port Server NICs? Thanks for your help, Matthew - overid3 =) On Tuesday 15 May 2001 14:12, Matthew Sackman wrote: Hay all. Does anyone have any knowledge of a network card that has two independant eth ports on it? The reason I ask is that I've gotta get 4 eth ports into a server squashed into a 2U rack which means I only have 3 expansion cards available... I look forward to hearing from you! Matthew -- a mailto:[EMAIL PROTECTED]Who is John Galt?/a Failure is not an option. It comes bundled with your Microsoft product. -- Ferenc Mantfeld -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Matthew Sackman Nottingham, ENGLAND Using Debian/GNU Linux Enjoying computing - End forwarded message - -- Matthew Sackman Nottingham, ENGLAND Using Debian/GNU Linux Enjoying computing
Re: [: Re: dual NICs]
On Wed, May 16, 2001 at 11:22:06PM +0100, Matthew Sackman wrote: Um I'm getting slightly confused here: what I need is one card which has two or more independant eth ports on it which can be assigned seperate IPs. I.e. not IP aliasing - each eth port has only one IP address, but each eth port must appear to linux as a seperate eth port, appearing in effect as if I have 4x single eth NICs in the box. Is this possible with, say, 2 of the Intel Dual Port Server NICs? If the chipset is supported, you should be able to use them. The card will probably be assigned eth0 and eth1. Check http://www.scyld.com/network/index.html#pci to see if the chipset is listed with any notes. -B -- Brandon High [EMAIL PROTECTED] Just think: in a few million years, Barney will be motor oil.
Re: dual NICs (fwd)
I thought Matthew took this off list. Matthew then forwarded his questions to the list. I now do so with my reply... For the record, I prefer to keep things on-list when possible. -- a mailto:[EMAIL PROTECTED]Who is John Galt?/a Failure is not an option. It comes bundled with your Microsoft product. -- Ferenc Mantfeld -- Forwarded message -- Date: Wed, 16 May 2001 16:56:06 -0600 (MDT) From: John Galt [EMAIL PROTECTED] To: Matthew Sackman [EMAIL PROTECTED] Subject: Re: dual NICs On Wed, 16 May 2001, Matthew Sackman wrote: On Wed, May 16, 2001 at 01:06:31AM -0600, John Galt wrote: On Tue, 15 May 2001, Zac Epkes wrote: You can not have 1 NIC with 2 IPs simply not possible, i think u can buy network cards with upto 4 ports that all act alone, or something similar... Wrong! eth0:1 and eth0:0... _Never_ say something's impossible... eth0:1 is IP aliasing with one wire and one NIC Um I'm getting slightly confused here: what I need is one card which has two or more independant eth ports on it which can be assigned seperate IPs. I.e. not IP aliasing - each eth port has only one IP address, but each eth port must appear to linux as a seperate eth port, appearing in effect as if I have 4x single eth NICs in the box. There were hardware lists... Is this possible with, say, 2 of the Intel Dual Port Server NICs? I think they just show up as 2 eepro100's. I've never actually had one to check, but the code for eepro.o will just go ahead and find all eepro100's (I've used multiple eepro100's in systems, just not the 2-on-a-card ones) in your system, and I assume they use two chips for two ports. The only problem is Intel's networking is a hodgepoge of first approximations and half-supported buyouts, so my guess is that the 2-port will work after a fashion, it may just be painful to see happen. JMHO... Thanks for your help, Matthew - overid3 =) On Tuesday 15 May 2001 14:12, Matthew Sackman wrote: Hay all. Does anyone have any knowledge of a network card that has two independant eth ports on it? The reason I ask is that I've gotta get 4 eth ports into a server squashed into a 2U rack which means I only have 3 expansion cards available... I look forward to hearing from you! Matthew -- a mailto:[EMAIL PROTECTED]Who is John Galt?/a Failure is not an option. It comes bundled with your Microsoft product. -- Ferenc Mantfeld -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- a mailto:[EMAIL PROTECTED]Who is John Galt?/a Failure is not an option. It comes bundled with your Microsoft product. -- Ferenc Mantfeld
dual NICs
Hay all. Does anyone have any knowledge of a network card that has two independant eth ports on it? The reason I ask is that I've gotta get 4 eth ports into a server squashed into a 2U rack which means I only have 3 expansion cards available... I look forward to hearing from you! Matthew -- Matthew Sackman Nottingham, ENGLAND Using Debian/GNU Linux Enjoying computing
Re: dual NICs
Adaptec makes a 4-port PCI card, Intel has some two port cards. I'm sure there are others out there as well. If I remember correctly, the Adaptec unfortunately took an IRQ for each port, which was a bit of a pain. --Rich Matthew Sackman wrote: Hay all. Does anyone have any knowledge of a network card that has two independant eth ports on it? The reason I ask is that I've gotta get 4 eth ports into a server squashed into a 2U rack which means I only have 3 expansion cards available... I look forward to hearing from you! Matthew -- Matthew Sackman Nottingham, ENGLAND Using Debian/GNU Linux Enjoying computing -- _ Rich Puhek ETN Systems Inc. _
Re: dual NICs
You can not have 1 NIC with 2 IPs simply not possible, i think u can buy network cards with upto 4 ports that all act alone, or something similar... - overid3 =) On Tuesday 15 May 2001 14:12, Matthew Sackman wrote: Hay all. Does anyone have any knowledge of a network card that has two independant eth ports on it? The reason I ask is that I've gotta get 4 eth ports into a server squashed into a 2U rack which means I only have 3 expansion cards available... I look forward to hearing from you! Matthew
Re: dual NICs
hi ya if you need 4 eth ports for each different ethernet cable... thats one problem... - use 2x dual nic pic cards.. - use one quad nic pci card - but i sounds like oyu need a quad nic card ( intel, adaptec, dlink ).. if you need 4 virtual ip# and dont care that its on one ethernet cable... than you can use virtual networks ( many different ways ) ( one nic...one rj45 cable ) w.x.y.z eth0 192.168.1.1 eth0:1 10.0.1.1eth0:2 ... ( all traffic on one copper ( eth0 ) = good and bad...depending ) have fun alvin On Tue, 15 May 2001, Zac Epkes wrote: You can not have 1 NIC with 2 IPs simply not possible, i think u can buy network cards with upto 4 ports that all act alone, or something similar... - overid3 =) On Tuesday 15 May 2001 14:12, Matthew Sackman wrote: Hay all. Does anyone have any knowledge of a network card that has two independant eth ports on it? The reason I ask is that I've gotta get 4 eth ports into a server squashed into a 2U rack which means I only have 3 expansion cards available... I look forward to hearing from you! Matthew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dual NICs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... You can not have 1 NIC with 2 IPs simply not possible, Perfectly possible. The mail server at work has 3 IPs. One of the ethernet ports on the firewall has 2 IPs. Think IP aliases (the old more established way): ifconfig eth0 ifconfig eth0:0 ifconfig eth0:1 as well as primary/secondary/tertiary/whatever addresses on each interface (the new way): ip addr add ip number 1/24 bcast broadcast 1 dev eth0 ip addr add ip number 2/24 bcast broadcast 2 dev eth0 ip addr add ip number 3/24 bcast broadcast 3 dev eth0 i think u can buy network cards with upto 4 ports that all act alone, or something similar... I've used Dlink's 4 port cards (they're really 4 individual ethernet adapters on a single card, each with it's own IRQ IO port, as well as some glue to make the card look like a totally separate PCI bus), and I hear Adaptec an Intel make them as well. - -- - -- Phil Brutsche [EMAIL PROTECTED] GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC GPG key id: 50DE1CFC GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7AemF/ZTSZFDeHPwRAowKAKDaQVBaowXnIcNc32pu7qy8Ko0TuQCfQC24 UwRnbZGsnKcbFCL9ldoSBUA= =2Un3 -END PGP SIGNATURE-
Re: dual NICs
hi ya http://www.adaptec.com/worldwide/product/proddetail.html?prodkey=ANA-62022cat=%2fTechnology%2fFast+Ethernet%2fDuraLAN+Network+Interface+Cards Adaptec Duo64 ANA-62022 ( Dual NIC ) http://www.adaptec.com/worldwide/product/proddetail.html?cat=Testprodkey=ANA-62044 Adaptec Quartet 6944A ( Quad NIC tulip driver ) http://www.dlink.com/tech/faq/dfe570tx-faq.htm DLink DFE-570TX ( Quad NIC tulip driver ) http://www.intel.com/network/products/pro100dport_adapter.htm Dual NIC c ya alvin i think u can buy network cards with upto 4 ports that all act alone, or something similar... I've used Dlink's 4 port cards (they're really 4 individual ethernet adapters on a single card, each with it's own IRQ IO port, as well as some glue to make the card look like a totally separate PCI bus), and I hear Adaptec an Intel make them as well.
Dual NICs, no forwarding
Got a question for the group. I've heard at work that I am going to be asked to add a network card in our web server so that our private network (10.1.0.0) can share resources on the web server. The web server will not be allowed to forward any traffic by default. This is being done by another box. Setting up this box for a new NIC is not an issue, but had an application related issue: Is it possible for an application running on this box, the web server, to access both networks (private net and internet)? Is there anything special that needs to be done to do so? Specifically, the application in question will be a bridge between the internet and the private net and will primarily be responding to requests from the internet side, then make connections to servers on the private net side. I guess almost like a proxy server, except no forwarding by default. Is there anything special that needs to be done in the server configuration, or is this really a none issue? Thanks for your time, -Craig Coles _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
