Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 old 166Mhz with 32MB EDO-RAM, about 1GB hard disk and 2 NIC's. I want to turn this into a bridge, so I need a linux-distro with a low-memory footprint, as well as the ability to block ports (example: block everything, except 80) on the bridge-ing NIC's.
Any suggestion would be appreciated!
The problem is that I'm not looking for routing/firewalling, I'm looking for bridging (with an old computer). In the article you mentioned, ports aren't even an issue (and that's neccesary if you read my story).
If you have any other tip/hints you're welcome to post them, I'll surely read them.
Now I have a big problem. I want to block some ports. Somehow IPtables from the howto I mentioned above, doesn't drop/block anything. Even with NO rules, the bridge works fine. I want to be able to block ports like 22, 80 etc.. How can I realize this? HELP!
I need a bridge, because I want to put a PC (the bridge) between my switch and my router. Since my router doesn't allow portblocking, I want to do this with the bridge. I will have LAN party soon, and am sick and tired of people playing WoW online. That's about my background information.
I'd personally put something like smoothwall (or just use iptables) on the PC (create router) and put connect the switch (lan party) to the red interface and the existing router to the green interface. Then block everything. I think that's the right connections. You could set it up with a pc on the green side to access the web interface of the smoothwall box, then move that box later to the red side if you wanted. That would block outgoing connections (you already have a router blocking the incomming).
A bridge is more like a switch. I don't think you can block ports with a bridge...
But then I'm thinking if you are blocking everything, then why not just unplug the router and disconnect the internet completely while you run the lan party? Normally you would only put a router in this situation if you wanted to block most ports and just leave a couple open... I guess you just want to leave 80 open and such...
Smoothwall REQUIRES 2 seperate subnets (which basically SUCKS if you want to use it as a bridge). I just used a plain Debian 3.0 "Sarge" install, which installed without too much problems. I'm using that and IPtables now as my bridge. I still have to check the performance, but I love that I can block certain ports now. I'm also writing my own little howto for it
By the way, my bridge-pc is transparant (it does have an IP) and doesn't reply to ping
I don't see a problem since it seems that one subnet is just the firewall to existing router connection. The smothwall box can do any dhcp itself anyway? But anyway, you'll have to show how you did the router without any NAT or extra subnet as it would be interesting to see and could be usefull to others.
For an ethernet bridge (what I needed). So it just forwards all traffic from one NIC to the other NIC and it filters some ports out (so it's NOT a router). My network is now like this: Internet <---> Router <---> Debian (bridge) <---> LAN (switch). I followed this howto: http://www.faqs.org/docs/Linux-HOWTO...UP_Linux_brctl
I needed something that was 'invisble' and wouldn't require messing with the existing network, which I succeeded in. Just follow the howto above and you can forward/block ports with IPtables, very easy.