Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Originally posted by tr4nce how to do to share internet with the rest of my net via DHCP?
If you are unfamiliar with networking in Linux I have found this: http://firestarter.sourceforge.net/ to be a very easy way to get a firewall AND setup internet connection sharing all at the same time.
BTW - you do want to use DHCP if that is how your network is set up with WIN ME. You will make your 'gateway machine' a DHCP server. Your other machines will need to 'broadcst' for an I.P. address. This is the same in windows only it sets things up the one and only way possible and you don't see what goes on behind the scenes. It's easy with Firestarter.
Last edited by rickenbacherus; 03-23-2003 at 01:30 PM.
DHCP is kind of cool because it is such powerful software and it is actually how most people connect with their Internet Service Provider. For just a few computers it is easier to use a static IP address which is how the serious sites that you actually find on the internet get their IP addresses. But, they use a different, much larger range of numbers.
This site explains this pretty well and shows you how to use Masquerade which not only connects your LAN to the internet, but gives you a firewall too:
Originally posted by SparceMatrix For just a few computers it is easier to use a static IP address
imho Static is not better because you have to do the extra task of assigning an I.P. address to each machine. If you have a machine that travels and connects to different networks then Static is really a pain. If you set up Static addressing now then you'll have to change you WIN ME machine AND all the machines on your network since you are already using DHCP with WIN ME so why change? Additionally you'd have to set up ICS in windows in an entirely different matter because windoze ICS is not very configurable. In fact you can't configure anything- either it's on or off. You should leave it as it is. Of course we all have our own situations and it isn't hard to assign I.P. addresses. I posted the link to Firestarter because it will do almost everything for you. Just install it, run the wizard and it will start on boot for you and it will serve up I.P. addresses for any machine on your network to grab. Then you can go learn about iptables and such.
Last edited by rickenbacherus; 03-23-2003 at 04:28 PM.
... If you set up Static addressing now then you'll have to change you WIN ME machine AND all the machines on your network since you are already using DHCP with WIN ME so why change? Additionally you'd have to set up ICS in windows in an entirely different matter because windoze ICS is not very configurable. In fact you can't configure anything- either it's on or off. You should leave it as it is. ...
Actually, I've used a Masquerade firewall to access the internet with both Windows 98SE and Windows XP Pro and it works much better then the Internet Connection Sharing (ICS) that you can get in Windows. I tried Internet Connection Sharing before Masquerade and prefer Masquerade. Masquerade is also known as NAT or Network Address Translation. You can get ethernet hubs with modems that provide the same feature.
If you have a lot of machines to set up on a network, then static addresses are going to be fussier to setup. The more you have, the more DHCP becomes the only alternative, unless you are actually on the internet in which static is also mandatory.
I have four computers on my little experimental LAN, three of which dual boot, so that is actually seven machines to set up and it is no big deal.
I agree - windows ICS sucks. BUT the reason I said for tr4nce to keep DHCP is because windows ICS is ONLY DHCP. If you set I.P.s on your other machines then ICS in windows stops working and you have to use a proxy. What an unnecessary pain. Apparently tr4nce likes to boot his gateway machine into windows & linux therefor it's much easier for him to use DHCP.
I too have a network
166MHz w/Coyote Linux is my firewall-router-DHCPserver and it doesn't even have a hard drive.
3 Linux boxes all set to broadcast for I.P. from DHCP server.2 of which dual boot.
1 windows laptop that travels to multiple corporate networks all of which use DHCP. You can simply bring the laptop home, connect the RJ45 and bam! you're online. If the laptop had to have a static I.P.for the home network then you'd have to set up multiple configurations and select which one you wanted at boot or change it every time from DHCP to STATIC. and we all know how long it takes to reboot a windows machine. <reboot> go take a nap-come back - hopefully it's up. There is nothing wrong with Static I.P.s certainly, I just thought that he would have alot less to do by keeping his current configuration. Afterall everything already works except for ICS on his Linux box right? So nothing else would need to be changed except for setting up ICS on the Linux box. Firestarter is the answer for those who don't know alot about home networking.
... I said for tr4nce to keep DHCP is because windows ICS is ONLY DHCP. If you set I.P.s on your other machines then ICS in windows stops working and you have to use a proxy. ...
Only if your gateway is a Windows machine. If your gateway is a Linux Masqueraded machine, then you can use static IP addresses on your Windows machine and still reach the internet.
I agree that if you have a laptop that also connects somewhere else outside your LAN, then DHCP is the best practical solution.
Congratulations on your diskless router. This is in store for me too. I may wind up with DHCP yet, since I have these diskless ambitions. See my other threads here about my Boot ROM problems. Also at Motherboards.org, user name FiberBundle.
Apologies to the initiator of this thread, the subject is drifting.
I am a complete newbie. I just installed Lycrois Linux today and I want to setup internet connection sharing over a 56k modem via a network through my win xp pro machine. I went to download Firestarter but I am confused on which version to get I'm not sure what version Lycrois is. I read that is was an Amethyst edition but I don't really know what that means. I need to know which version to download. My choices are: Red Hat 8.x RPM, Red Hat 7.x RPM, Mandrake 9.x RPM, Debian DEB, Source RPM, Source tarball, and MD5 checksums. I know this is a stupid question and I am terribly sorry but I don't know the answer so if you do please help me out. Iím guessing not Red Hat, Mandrake, or Debian.
I don't know the first thing about Lycoris but it is sometimes possible to use different packaging systems. That would best be answered by someone other than myself. You can always get the source tarball and do this (as root)
tar xzvf firestarter 0.1.2.tar.gz
then you do a
cd firestarter 0.1.2
After you give the 'ls' command you will see several files. and most likely one will be named INSTALL or README so use your favorite editor (mine is midnight commander) to read them like this:
That should give you details on how to install. Like I said it's usually the format I gave above but not necessarily.
There's more to it than that but there's an example for you. I don't know what the actual Firestarter tarball is named. Do searches for 'compiling from source'.