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.
I have my firewall set to let outbound traffic through by default and deny inbound traffic by default. This message should be outbound as my server ip is 192.168.0.50. What is causing this to be blocked and is there a way to let this through?
Code tags - not quote tags. Code tags make the columns line up nicely.
Anyway, the short answer is we can insert an iptables rule in the OUTPUT chain to explicitly allow outbound udp to that port. Is this what you want?
Another consideration is whether firestarter will clobber our new rule as soon as you restart it. I don't use/know firestarter - is there a facility to add your own rules with it?
Note that I'm not advising that you do that. And I'll reiterate that firestarter will probably clobber the rule after you restart it. So if you want this to remain in place permanently, you'll have to find a way to add it through firestarter.
I don't believe I can add lines directly into the firestarter configuration unfortunately. However after playing with the rules and watching the lines I found that if I added 192.168.0.50 to the inbound allow-from servers then this blocking no longer appears.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.