Re: firewalld

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Samuel,

On Tue, 2020-10-27 at 01:58 -0700, Samuel Sieb wrote:
> On 10/26/20 7:44 AM, Michael J. Baars wrote:
> > I'm writing a client and server program for cluster computation. I noticed that nmap sees a specific port as open on Fedora Server and as filtered on Fedora
> > Workstation when the server is running and sees this port as closed on Fedora Server and as filtered on Fedora Workstation when the server is not running.
> 
> You don't say which port, so it makes it impossible to give you useful 
> advice.

The exact ports are of no importance :)

> 
> > While looking into the firewalld configuration I found that Fedora Workstation and Fedora Server have one major difference their configuration files:
> > 
> >    <port protocol="udp" port="1025-65535"/>
> >    <port protocol="tcp" port="1025-65535"/>
> 
> You don't say what the difference is.  Which one has that and where?

These are Fedora Workstation configuration settings.

> 
> > After removing these specific lines from /etc/firewalld/zones/FedoraWorkstation.xml, using firewall-cmd, the ports are still accessible by the client and
> > server
> > program.
> 
> Since you say "still", I assume you mean on the Server.  You modified 
> the workstation config file, why would it change anything?
> 
> > Can someone please tell me how to close these ports on Fedora Workstation? And why does nmap report the ports as filtered on Fedora Workstation and as
> > open/close on Fedora Server?
> 
> What do you mean by closed?  The reason they show up as filtered is 
> because they are blocked on Workstation and not on Server.

I might indeed have accidentally mixed the two up. Everythings works just fine now, don't exactly know why though, perhaps a malfunctioning 'systemctl restart
firewalld'? Strange, I almost know for sure that it was the Workstation ports that were reported as filtered.

> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux