Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
You'll have to allow for DNS, if needed, and also mind ipv6 (if in use). Your second example does similar: it takes packets on the INPUT chain and then drops tcp/20 packets. If you want that type of rule, look into negation (! --dport 20). Unfortunately, I can't easily test these rules right now but I think you can see what I'm getting at.
You'll have to allow for DNS, if needed, and also mind ipv6 (if in use). Your second example does similar: it takes packets on the INPUT chain and then drops tcp/20 packets. If you want that type of rule, look into negation (! --dport 20). Unfortunately, I can't easily test these rules right now but I think you can see what I'm getting at.
Hello,
Thank you so much for your reply.
Why you changed DROP to ACCEPT in the second rule?
Because the default policy is already DROP and everything is dropped by default. If you don't make any exception, nothing is allowed and you wanted tcp/40.
Quote:
-P, --policy chain target
Set the policy for the built‐in (non‐user‐defined) chain to the
given target. The policy target must be either ACCEPT or DROP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.