Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
1 - why is iptables logging my VOIP traffic and could this be the reason that my voip recepetions is bad because of this logging of the packets. The VOIP company told me to put my machine in its own DMZ.
2 - I am still having trouble trying to setup in iptables my VOIP modem on it own DMZ. Can somebody please help me
1. It isn't. Log entries you've shown are DHCP AFAIK. Unless you've got a combo old CPU and bad logging filters (logging too much) I wouldn't say Iptables logging would make for that much of a performance drop (and you got rate limiting on, right?). Besides that logging has no effect on how packets are filtered.
2. Ze wwules, show us ze wwules!
OK. Some questions. Did they give you a public IP for the phone as per your other thread? Do you know which protocols this phone uses? If it uses H323, did you try h323-conntrack-nat like Fdetienn suggested?
They did not give me a static IP they just told me to throw it behind my firewall and assign it a private IP. It is not using H323 protocol. It uses Vocoders - G.711,G.723.1,G.729.1,G729a,ab and G729 protocols. Echo Translation - G.168. They use TAS (Transparent address sharing). The name of my VOIP modem is Mediatrix 2102. IT uses SIP.
Last edited by metallica1973; 11-21-2005 at 05:03 PM.
It's explained pretty good what a mess trying to route these protocols will be. Next to having one port (5060) as control channel and the need for a dynamic port range (10000:20000 IIRC) you will need to open up the DMZ for --state NEW traffic or else noone will be able to call you.
would I set this up in the same way as I would setup a web server?
AFAIK, yes, since the module is supposed to handle RTP you should only have to allow any SIP traffic on TCP+UDP/5060.
I'd recommend adding logging rules so you know if its missing something.