From: Scott S. <sw...@ch...> - 2004-06-30 15:17:15
|
I am a novice Linux user, so I hope this wasn't already covered in another post, if it has, please point me in the right direction. I am working on creating a NAT/Router from a Dell Optiplex with an on-board NIC (3Com). I scraped up a few old NICs (mainly LNE TX100s .. LinkSys and a 3Com 3C905TXM). My intention is to use the on-board NIC as the eth0, the outbound/Internet connection, and the other 3 as internal eth1, eth2 and eth3. The external interface handled by the ISPs DHCP and the internals will be servicing PCs with static IPs. The situation I run into is that when I setup Devil-Linux without the other NICs (on-board only) it setup nicely, but when I installed the NICs it automatically chose the 3C905 as eth0. I tried installing one at a time, and when I finally installed the 3C905 it always was designated as eth0 no matter what. First question: Why would it do that? Second question: How would I get Devil-Linux to setup like I had planned? Like I said earlier, I am a bit of a novice Linux user, and really wanna learn this. Point me to some documentation (I hope I didn't overlook some) and I will dive in. I just hope it wasn't something silly I overlooked. Thanks for any assistance. -- Scott S. swarty(at)charter(dot)net "If you understand what you are doing, you are not learning anything." - anonymous |
From: Tim T. <t....@co...> - 2004-06-30 16:47:13
|
Scott S. wrote: >I am a novice Linux user, so I hope this wasn't already covered in >another post, if it has, please point me in the right direction. > >I am working on creating a NAT/Router from a Dell Optiplex with an >on-board NIC (3Com). I scraped up a few old NICs (mainly LNE TX100s .. >LinkSys and a 3Com 3C905TXM). My intention is to use the on-board NIC >as the eth0, the outbound/Internet connection, and the other 3 as >internal eth1, eth2 and eth3. The external interface handled by the >ISPs DHCP and the internals will be servicing PCs with static IPs. > >The situation I run into is that when I setup Devil-Linux without the >other NICs (on-board only) it setup nicely, but when I installed the >NICs it automatically chose the 3C905 as eth0. I tried installing one >at a time, and when I finally installed the 3C905 it always was >designated as eth0 no matter what. > >First question: Why would it do that? > >Second question: How would I get Devil-Linux to setup like I had >planned? > >Like I said earlier, I am a bit of a novice Linux user, and really wanna >learn this. Point me to some documentation (I hope I didn't overlook >some) and I will dive in. I just hope it wasn't something silly I >overlooked. > >Thanks for any assistance. > There was an length discussion of this before, though somewhat fruitless. The one post of much use (as well as the rest of the thread) can be found here: <http://sourceforge.net/mailarchive/message.php?msg_id=7307817> There is also a link to a howto on interface naming: <http://www.xenotime.net/linux/doc/network-interface-names.txt> It is my belief (though not thoroughly tested) that the NIC discovery order is based on PCI slots. If you switch two cards, their eth# should switch. Of course the on-board NIC can't be switched. The only sure handle on a NIC is the embedded MAC# which is usually printed on the better qualiy cards (like 3Com's). I have started writing the MAC# on the backplate of my NICs so I can see it w/o opening the chassis. The onboard NIC MAC# can usually be gotten from the BIOS. The naming scheme discussed in the link lets you name cards based on the MAC address. I have not tried this though I mean to. Good luck and please post your results if you get it working:) Tim |
From: Scott S. <sw...@ch...> - 2004-06-30 22:49:54
|
On Wed, 2004-06-30 at 11:48, Tim Tait wrote: > Scott S. wrote: > > >I am a novice Linux user, so I hope this wasn't already covered in > >another post, if it has, please point me in the right direction. > > > >I am working on creating a NAT/Router from a Dell Optiplex with an > >on-board NIC (3Com). I scraped up a few old NICs (mainly LNE TX100s .. > >LinkSys and a 3Com 3C905TXM). My intention is to use the on-board NIC > >as the eth0, the outbound/Internet connection, and the other 3 as > >internal eth1, eth2 and eth3. The external interface handled by the > >ISPs DHCP and the internals will be servicing PCs with static IPs. > > > >The situation I run into is that when I setup Devil-Linux without the > >other NICs (on-board only) it setup nicely, but when I installed the > >NICs it automatically chose the 3C905 as eth0. I tried installing one > >at a time, and when I finally installed the 3C905 it always was > >designated as eth0 no matter what. > > > >First question: Why would it do that? > > > >Second question: How would I get Devil-Linux to setup like I had > >planned? > > > >Like I said earlier, I am a bit of a novice Linux user, and really wanna > >learn this. Point me to some documentation (I hope I didn't overlook > >some) and I will dive in. I just hope it wasn't something silly I > >overlooked. > > > >Thanks for any assistance. > > > > There was an length discussion of this before, though somewhat > fruitless. The one post of much use (as well as the rest of the thread) > can be found here: > > <http://sourceforge.net/mailarchive/message.php?msg_id=7307817> > > There is also a link to a howto on interface naming: > <http://www.xenotime.net/linux/doc/network-interface-names.txt> > > It is my belief (though not thoroughly tested) that the NIC discovery > order is based on PCI slots. If you switch two cards, their eth# should > switch. Of course the on-board NIC can't be switched. The only sure > handle on a NIC is the embedded MAC# which is usually printed on the > better qualiy cards (like 3Com's). I have started writing the MAC# on > the backplate of my NICs so I can see it w/o opening the chassis. The > onboard NIC MAC# can usually be gotten from the BIOS. The naming scheme > discussed in the link lets you name cards based on the MAC address. > > I have not tried this though I mean to. Good luck and please post your > results if you get it working:) > > Tim Thanks for your reply Tim! I should have mentioned that I did try rearranging the order of NICs and/or cards. Every time I added the 3C905TX it took the eth0 spot. Even if I put the others in first and saved the good config, then added the 3C905, it changed the config on me. I did see a sale on NICs at my local Radio Shack, LinkSys LNE TX100 for $4.99. Maybe I'll just hope on down and pick up a few. Can't go too wrong there. Have some on hand in case I need an extra. But I would really like to know the how and why. Also, I managed to keep most of the NICs on their own IRQs, but their is one pair that are sharing an IRQ. Some hardware can share IRQs just fine and some do not. Will this NIC IRQ sharing impose a performance hit and if so any idea of how much? Thanks also for the links!! -- Scott S. swarty(at)charter(dot)net "If you understand what you are doing, you are not learning anything." - anonymous |
From: Bruce S. <bw...@ar...> - 2004-07-01 00:48:45
|
> Thanks for your reply Tim! I should have mentioned that I did try > rearranging the order of NICs and/or cards. Every time I added the > 3C905TX it took the eth0 spot. Even if I put the others in first and > saved the good config, then added the 3C905, it changed the config on > me. I did see a sale on NICs at my local Radio Shack, LinkSys LNE TX100 > for $4.99. Maybe I'll just hope on down and pick up a few. Can't go > too wrong there. Have some on hand in case I need an extra. But I > would really like to know the how and why. > > Also, I managed to keep most of the NICs on their own IRQs, but their is > one pair that are sharing an IRQ. Some hardware can share IRQs just > fine and some do not. Will this NIC IRQ sharing impose a performance > hit and if so any idea of how much? > > Thanks also for the links!! Try looking at the ifcfg-eth* files in the /etc/sysconfig/nic directory. Each interface has a "MODULE=..." line. If your cards use different modules, you may be able to shuffle the MODULEs around the way you want. - BS |
From: Dan S. <ds...@tr...> - 2004-07-01 12:52:31
|
I've had a ton of problems with Linksys LNE-100TX nics under both Linux and Windows. I recommend that you look elsewhere. D-Links have been good to me and are pretty cheap. Dan On Wednesday 30 June 2004 04:49 pm, Scott S. wrote: > On Wed, 2004-06-30 at 11:48, Tim Tait wrote: > > Scott S. wrote: > > >I am a novice Linux user, so I hope this wasn't already covered in > > >another post, if it has, please point me in the right direction. > > > > > >I am working on creating a NAT/Router from a Dell Optiplex with an > > >on-board NIC (3Com). I scraped up a few old NICs (mainly LNE TX100s .. > > >LinkSys and a 3Com 3C905TXM). My intention is to use the on-board NIC > > >as the eth0, the outbound/Internet connection, and the other 3 as > > >internal eth1, eth2 and eth3. The external interface handled by the > > >ISPs DHCP and the internals will be servicing PCs with static IPs. > > > > > >The situation I run into is that when I setup Devil-Linux without the > > >other NICs (on-board only) it setup nicely, but when I installed the > > >NICs it automatically chose the 3C905 as eth0. I tried installing one > > >at a time, and when I finally installed the 3C905 it always was > > >designated as eth0 no matter what. > > > > > >First question: Why would it do that? > > > > > >Second question: How would I get Devil-Linux to setup like I had > > >planned? > > > > > >Like I said earlier, I am a bit of a novice Linux user, and really wanna > > >learn this. Point me to some documentation (I hope I didn't overlook > > >some) and I will dive in. I just hope it wasn't something silly I > > >overlooked. > > > > > >Thanks for any assistance. > > > > There was an length discussion of this before, though somewhat > > fruitless. The one post of much use (as well as the rest of the thread) > > can be found here: > > > > <http://sourceforge.net/mailarchive/message.php?msg_id=7307817> > > > > There is also a link to a howto on interface naming: > > <http://www.xenotime.net/linux/doc/network-interface-names.txt> > > > > It is my belief (though not thoroughly tested) that the NIC discovery > > order is based on PCI slots. If you switch two cards, their eth# should > > switch. Of course the on-board NIC can't be switched. The only sure > > handle on a NIC is the embedded MAC# which is usually printed on the > > better qualiy cards (like 3Com's). I have started writing the MAC# on > > the backplate of my NICs so I can see it w/o opening the chassis. The > > onboard NIC MAC# can usually be gotten from the BIOS. The naming scheme > > discussed in the link lets you name cards based on the MAC address. > > > > I have not tried this though I mean to. Good luck and please post your > > results if you get it working:) > > > > Tim > > Thanks for your reply Tim! I should have mentioned that I did try > rearranging the order of NICs and/or cards. Every time I added the > 3C905TX it took the eth0 spot. Even if I put the others in first and > saved the good config, then added the 3C905, it changed the config on > me. I did see a sale on NICs at my local Radio Shack, LinkSys LNE TX100 > for $4.99. Maybe I'll just hope on down and pick up a few. Can't go > too wrong there. Have some on hand in case I need an extra. But I > would really like to know the how and why. > > Also, I managed to keep most of the NICs on their own IRQs, but their is > one pair that are sharing an IRQ. Some hardware can share IRQs just > fine and some do not. Will this NIC IRQ sharing impose a performance > hit and if so any idea of how much? > > Thanks also for the links!! |
From: Bruce S. <bw...@ar...> - 2004-07-01 12:58:15
|
> I've had a ton of problems with Linksys LNE-100TX nics under both Linux ... Which module are you using? There is more than one Linux driver for the "tulip" chipsets, and I've had better luck with some over others. - BS |
From: Scott S. <sw...@ch...> - 2004-07-01 18:50:32
|
On Thu, 2004-07-01 at 07:52, Dan Shadix wrote: > I've had a ton of problems with Linksys LNE-100TX nics under both Linux and > Windows. I recommend that you look elsewhere. D-Links have been good to me > and are pretty cheap. Hmm, I usually had good luck with LinkSys, but usually prefer 3Com. I got 2 more NICs LinkSys LNE 100TX ver 5.1 They all got detected and I got them in the order I wanted with no problems. I gotta double check but for some reason I believe it loaded a different module then the Tulip. I think Adamtek or sumthing similar. I will double check tonight. I am pretty happy thus far, got the onboard 3Com as ETH0 and 4 other NICS and only 1 pair sharing an IRQ. (I hope this will not impose a performance issue.) Now I just gotta read the docs on the setting up the NAT/Firewall. I was planning on using Firewall Builder. Does anybody have any other suggestions, or recommended readings, links? Scott > Dan > > On Wednesday 30 June 2004 04:49 pm, Scott S. wrote: > > On Wed, 2004-06-30 at 11:48, Tim Tait wrote: > > > Scott S. wrote: > > > >I am a novice Linux user, so I hope this wasn't already covered in > > > >another post, if it has, please point me in the right direction. > > > > > > > >I am working on creating a NAT/Router from a Dell Optiplex with an > > > >on-board NIC (3Com). I scraped up a few old NICs (mainly LNE TX100s .. > > > >LinkSys and a 3Com 3C905TXM). My intention is to use the on-board NIC > > > >as the eth0, the outbound/Internet connection, and the other 3 as > > > >internal eth1, eth2 and eth3. The external interface handled by the > > > >ISPs DHCP and the internals will be servicing PCs with static IPs. > > > > > > > >The situation I run into is that when I setup Devil-Linux without the > > > >other NICs (on-board only) it setup nicely, but when I installed the > > > >NICs it automatically chose the 3C905 as eth0. I tried installing one > > > >at a time, and when I finally installed the 3C905 it always was > > > >designated as eth0 no matter what. > > > > > > > >First question: Why would it do that? > > > > > > > >Second question: How would I get Devil-Linux to setup like I had > > > >planned? > > > > > > > >Like I said earlier, I am a bit of a novice Linux user, and really wanna > > > >learn this. Point me to some documentation (I hope I didn't overlook > > > >some) and I will dive in. I just hope it wasn't something silly I > > > >overlooked. > > > > > > > >Thanks for any assistance. > > > > > > There was an length discussion of this before, though somewhat > > > fruitless. The one post of much use (as well as the rest of the thread) > > > can be found here: > > > > > > <http://sourceforge.net/mailarchive/message.php?msg_id=7307817> > > > > > > There is also a link to a howto on interface naming: > > > <http://www.xenotime.net/linux/doc/network-interface-names.txt> > > > > > > It is my belief (though not thoroughly tested) that the NIC discovery > > > order is based on PCI slots. If you switch two cards, their eth# should > > > switch. Of course the on-board NIC can't be switched. The only sure > > > handle on a NIC is the embedded MAC# which is usually printed on the > > > better qualiy cards (like 3Com's). I have started writing the MAC# on > > > the backplate of my NICs so I can see it w/o opening the chassis. The > > > onboard NIC MAC# can usually be gotten from the BIOS. The naming scheme > > > discussed in the link lets you name cards based on the MAC address. > > > > > > I have not tried this though I mean to. Good luck and please post your > > > results if you get it working:) > > > > > > Tim > > > > Thanks for your reply Tim! I should have mentioned that I did try > > rearranging the order of NICs and/or cards. Every time I added the > > 3C905TX it took the eth0 spot. Even if I put the others in first and > > saved the good config, then added the 3C905, it changed the config on > > me. I did see a sale on NICs at my local Radio Shack, LinkSys LNE TX100 > > for $4.99. Maybe I'll just hope on down and pick up a few. Can't go > > too wrong there. Have some on hand in case I need an extra. But I > > would really like to know the how and why. > > > > Also, I managed to keep most of the NICs on their own IRQs, but their is > > one pair that are sharing an IRQ. Some hardware can share IRQs just > > fine and some do not. Will this NIC IRQ sharing impose a performance > > hit and if so any idea of how much? > > > > Thanks also for the links!! -- Scott S. swarty(at)charter(dot)net "If you understand what you are doing, you are not learning anything." - anonymous |
From: Heiko Z. <he...@zu...> - 2004-07-01 19:05:21
|
> On Thu, 2004-07-01 at 07:52, Dan Shadix wrote: >> I've had a ton of problems with Linksys LNE-100TX nics under both Linux >> and >> Windows. I recommend that you look elsewhere. D-Links have been good >> to me >> and are pretty cheap. > > Hmm, I usually had good luck with LinkSys, but usually prefer 3Com. I > got 2 more NICs LinkSys LNE 100TX ver 5.1 They all got detected and I > got them in the order I wanted with no problems. I gotta double check > but for some reason I believe it loaded a different module then the > Tulip. I think Adamtek or sumthing similar. I will double check > tonight. I am pretty happy thus far, got the onboard 3Com as ETH0 and 4 > other NICS and only 1 pair sharing an IRQ. (I hope this will not impose > a performance issue.) > > Now I just gotta read the docs on the setting up the NAT/Firewall. I > was planning on using Firewall Builder. Check out our sample files /etc/init.d/firewall.rules.* Those files also have some good links in the header. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: yanu <ya...@ad...> - 2004-07-01 20:01:05
|
Op (01/07/04 13:46), Scott S. schreef: > On Thu, 2004-07-01 at 07:52, Dan Shadix wrote: > > Now I just gotta read the docs on the setting up the NAT/Firewall. I > was planning on using Firewall Builder. > > Does anybody have any other suggestions, or recommended readings, links? I'm using this script, for me it does all that i need: http://monmotha.mplug.org/~monmotha/firewall/firewall/2.3/ |