Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I currently have forwarding available on ipchains for everything to get out through the firewall. I want to keep Kazaa (port 1214) from getting in or out. I have put rules to deny in all chains (input, output, forwarding) and still kazaa connects. If I disable forwarding kazaa stops working. That is great accept that nothing else works. I want to stay away from making special rules for everything else to get out. Please give me an idea as to why this is not working. Thanks in advance.
I gues you don't have all Kazaa ports blocked. Turn forwarding on, run tcpdump on the router and connect to Kazaa from one of the machines inside yur local network. Tcpdump will show you what ports were used.
i have done that and 1214 is the first port that it communicates with. Also all of the Kazaa forums say that 1214 is the port that needs to be opened in order for it to work.
First of all INPUT and OUTPUT don't affect the KaZaA connections if the KaZaA connections are coming from the internal network. So what you must do is this. So make all DENY entries in the FORWARD chain. run tcpdump and find the ports it uses to connect like Mara said and then make entries in your firewall script to block the ports. Although since you can change what ports are used for KaZaA I would also make entries to block the servers that list where P2P peers are located.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.