SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I have a computer that I am currently setting up for my school as a content filter. The machine has 2 network cards in it. I have one card setup perfectly to work as the receiving end of the internet. My question is, what do I have to do to get the OTHER card setup as the output to the rest of the network? Thanks
PS I am still working on Squid and Dan's filter. Any suggestions would be appreciated.
depends how you want this all to work really. if this box is ONLY for web, then you should run it as a proxy, let them connect to squid and let that go off to the internet seperately. in this scenario there is really very little networking to do, it simply is on two networks at once. squid does not "output" to a network, it simply responds back to whoever asked it to do something, and if that client was on the internal side, then that's where it will reply to. if the internal network contains more than just the local network then you would need to add on manual routes to all other networks reachable internally.
well that's not http proxying then.. that's natting... which is what i would recommend against. if you only want web, do the networking at a higher applicatino level where you are only interested in http gets and posts. doing a nat / masq towards the internet could give a vast amount more access than is intended.
well laregly as above but essentially.. your subnets there are a complete mess, i'd suggest reading up on subnetting and ip in general, as one network clearly contains the network of the other in a larger mask.. that's a mess and little else.