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.
hi,
just to clarify.
I have a server with 2 NICs.
The I/O network traffic that come and exit using the 2 NICs will use firewalld process in centos 7.right?
Firewalld looks in firewall table for every packet that come using evey NIC.right?
firewall-cmd --zone=public --add-port=161/udp --permanent -means that the traffic on port 161 is allowed?
tnx
hi,
just to clarify.
I have a server with 2 NICs.
The I/O network traffic that come and exit using the 2 NICs will use firewalld process in centos 7.right?
Firewalld looks in firewall table for every packet that come using evey NIC.right?
firewall-cmd --zone=public --add-port=161/udp --permanent -means that the traffic on port 161 is allowed?
tnx
Perhaps a better name for your thread might have been, "Advice with configuring firewalld"
Take note of what the --permanent option will and will not do for you. I.e. you need to either reload, or issue the same command without the --permanent qualifier to have it effective at runtime.
As far as I know, it’s the netfilter kernel module that processes network traffic, and firewalld is a front-end to netfilter. You don’t need firewalld and the firewall-cmd to implement a firewall.
Packets that enter and leave through any NIC are processed according to netfilter rules.
The firewall-cmd command in the question allows traffic to port 161 that comes from interfaces in the public zone, but as rmistler says, you need to reload (or reboot), or issue the same command without the permanent option.
Last edited by berndbausch; 04-24-2019 at 03:22 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
