I still consider myself a newbie with Linux and a complete dummy about networking as I have never dealt with it before. Now that is out of the way, I would like this groups recommendation as to setting up two computer for networking. I have one computer that has Linux installed and one with windows. Each has only the one OS on it. I would also like to be able to use either computer or both at the same time when connected to the internet if this is possible. So I need recommendations for: 1. When networking cards to obtain. 2. Other than the programs installed for networking by 6.3, which other programs would be needed. (Samba, VW, etc) 3. What type of cableing between the two computers is easiest or best. 4. If the phone line is connected to the Linux computer, how do you connect the Windos computer to the telephone line through the Linux machine. 56K modems are installed in both computers. Either may be other questions I should be asking, but cann't think of them right now. I want to get the computers talking to each other first then I'll think about the internet side. I want to do this as cheaply as possible as I am retired on a limited income. I have been thinking about older used networking cards. thanks in advance, Nevada -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Nevada wrote: [ clip ]
1. When networking cards to obtain.
Almost any of the common ethernet cards. Here is a list from the Kernel configuration menu ("make menuconfig"): [*] 3COM cards < > 3c501 support (NEW) < > 3c503 support (NEW) < > 3c505 support (NEW) < > 3c507 support (NEW) < > 3c509/3c579 support (NEW) < > 3c515 ISA Fast EtherLink (NEW) < > 3c90x series "Cyclone/Hurricane/Tornado" support (NEW) < > 3c590 series (592/595/597) "Vortex" support (NEW) < > AMD LANCE and PCnet (AT1500 and NE2100) support [*] Western Digital/SMC cards < > WD80*3 support (NEW) < > SMC Ultra support (NEW) < > SMC Ultra32 EISA support (NEW) < > SMC 9194 Support (NEW) [*] Racal-Interlan (Micom) NI cards < > NI5010 support (NEW) < > NI5210 support (NEW) < > NI6510 support (NEW) < > RealTek 8129/8139 (not 8019/8029!) support < > SiS 900 PCI Fast Ethernet Adapter support < > Packet Engines Yellowfin Gigabit-NIC support [*] Other ISA cards < > AT1700/1720 support (NEW) < > Cabletron E21xx support (NEW) < > DEPCA support (NEW) < > EtherWorks 3 support (NEW) < > EtherExpress support (NEW) < > EtherExpress PRO support (NEW) < > FMV-181/182/183/184 support (NEW) < > HP PCLAN+ (27247B and 27252A) support (NEW) < > HP PCLAN (27245 and other 27xxx series) support (NEW) < > HP 10/100VG PCLAN (ISA, EISA, PCI) support (NEW) < > ICL EtherTeam 16i/32 support (NEW) < > NE2000/NE1000 support (NEW) < > SEEQ8005 support (NEW) [ ] SK_G16 support (NEW) [*] EISA, VLB, PCI and on board controllers < > AMD PCnet32 (VLB and PCI) support < > Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support < > Ansel Communications EISA 3200 support < > Apricot Xen-II on board Ethernet < > CS89x0 support < > PCI DM9102 support < > Generic DECchip & DIGITAL EtherWORKS PCI/EISA < > DECchip Tulip (dc21x4x) PCI support < > Older DECchip Tulip (dc21x4x) PCI support (tulip-old.o < > Digi Intl. RightSwitch support < > EtherExpress PRO/100 support
2. Other than the programs installed for networking by 6.3, which other programs would be needed. (Samba, VW, etc)
You need nothing that doesn't come in the SuSE 6.3 box, but the SuSE web page has a useful addition: http://sdb.suse.de/sdb/en/html/hoe_wv_dod_start.html But setting this up right is a bit advanced, so save it for last.
3. What type of cableing between the two computers is easiest or best.
RJ45, aka twisted pair, aka CAT-5. Use a hub. It actually can be cheaper to use coax since you don't need to buy a hub but you will probably get a hub in the long run so might as well start out right.
4. If the phone line is connected to the Linux computer, how do you connect the Windos computer to the telephone line through the Linux machine. 56K modems are installed in both computers.
If all you want is internet support, don't attempt to make the modem itself available to both machines. Use the linux machine for the dial-up internet connection and use ip masquerading to make the internet available to the Windows system. The Windows system will then simply point to the Linux machine as the gateway and not even be aware that it doesn't have a direct connection to the internet.
Either may be other questions I should be asking, but cann't think of them right now. I want to get the computers talking to each other first then I'll think about the internet side.
For internet access from the Windows system through the Linux system you only need to get TCP/IP working -- if you can ping Linux from Windows you've pretty much got it on the Windows side. You may also want to set up file and print sharing, but this is not needed for internet access from Windows.
I want to do this as cheaply as possible as I am retired on a limited income. I have been thinking about older used networking cards.
NE2000 cards are usually pretty cheap. I've personally used an NE2000 clone, a 3COM 3c509, and an Intel EtherExpress Pro/100. Your choice may depend on what kind of slot you have available: ISA or PCI. -- ____________________________________________________________________ Robert Paulsen http://paulsen.home.texas.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Nevada wrote:
I still consider myself a newbie with Linux and a complete dummy about networking as I have never dealt with it before. Now that is out of the way, I would like this groups recommendation as to setting up two computer for networking.
I have one computer that has Linux installed and one with windows. Each has only the one OS on it. I would also like to be able to use either computer or both at the same time when connected to the internet if this is possible.
So I need recommendations for:
1. When networking cards to obtain.
Well, I have used a number of netword cards (also known as NIC's). I must admit that hands down the BIG hand brand cards are much easier to work with. I only deal with 3COM, but Intel is also a good brand. I recommend looking around for some older name brand NIC's and getting those.
2. Other than the programs installed for networking by 6.3, which other programs would be needed. (Samba, VW, etc)
Everything is on the CD's
3. What type of cableing between the two computers is easiest or best.
There is both BNC (cable like that of cable TV) or RJ45, it looks like telephone wire but with four pair rather then two pair wire. I recommend going with RJ45, but as someone else said, it requires a HUB, BUT you can use crossover cable rather then spending the money on a HUB. I recommend RJ45 because the one crossover cable will be cheaper then the terminators and the cable for BNC, and more importantly it is very easy to mess up the physical connection on BNC.
4. If the phone line is connected to the Linux computer, how do you connect the Windos computer to the telephone line through the Linux machine. 56K modems are installed in both computers.
There is a lot to this one, like someone else said, only use the modem in the Linux box and setup IP Masquerading to allow the Windows box to get to the net. I have aDSL so I don't know how to configure Linux to dial up an ISP, but I do know that you will need to look into configuring ppp. The next question is, do you want the Linux box to dial the net every time either box tries to access the net? If you do, I believe you will want to look into setting up diald, but I might be wrong on this account. What order to do things in? I would first get the NIC installed and get the two boxes talking to one another. Then I would get the Linux box configured to dial up you ISP, if you haven't already. Then setup IP Masqurading. There are other things like Samba that you might want to consider running, also. But before you do, you might want to look into security... It is very easy to end up broadcasting network services like Samba to the Internet if you don't look into security. I have implimented a firewall here just to be safe:) Hope this helps! Sam -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Sam Carleton wrote:
Nevada wrote:
[clip]
3. What type of cableing between the two computers is easiest or best.
There is both BNC (cable like that of cable TV) or RJ45, it looks like telephone wire but with four pair rather then two pair wire. I recommend going with RJ45, but as someone else said, it requires a HUB, BUT you can use crossover cable rather then spending the money on a HUB. I recommend RJ45 because the one crossover cable will be cheaper then the terminators and the cable for BNC, and more importantly it is very easy to mess up the physical connection on BNC.
I agree and retract my earlier statement that BNC might be cheaper. I had forgotten that you can use a crossover RJ45 cable. This might be the simplest way to set up a two-system network. Not only do you not need to buy a hub, you don't need to find a place to put it and a place to plug it in to wall power.
4. If the phone line is connected to the Linux computer, how do you connect the Windos computer to the telephone line through the Linux machine. 56K modems are installed in both computers.
There is a lot to this one, like someone else said, only use the modem in the Linux box and setup IP Masquerading to allow the Windows box to get to the net. I have aDSL so I don't know how to configure Linux to dial up an ISP, but I do know that you will need to look into configuring ppp. The next question is, do you want the Linux box to dial the net every time either box tries to access the net? If you do, I believe you will want to look into setting up diald, but I might be wrong on this account.
The link I gave in my earlier message was for a script SuSE has on its web site that configures wvdial and pppd for demand dialing. I now use this instead of diald. It works flawlessly once set up but it is hard to set up since the script has a few bugs.
What order to do things in? I would first get the NIC installed and get the two boxes talking to one another. Then I would get the Linux box configured to dial up you ISP, if you haven't already. Then setup IP Masqurading. There are other things like Samba that you might want to consider running, also. But before you do, you might want to look into security...
It is very easy to end up broadcasting network services like Samba to the Internet if you don't look into security. I have implimented a firewall here just to be safe:)
SuSE also has a nice firewall package (replacing their older one) called firewals (that odd spelling is correct; apparently used so as not to conflict with the name of their older package). It is in the "sec" group, not the "n" group. -- ____________________________________________________________________ Robert Paulsen http://paulsen.home.texas.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
Anonymous User -
paulsen＠texas.net -
phthor＠isat.com