On 2018-06-12 18:23, Simon Becherer wrote:
I but found out that:
rpcinfo -p
shows me for "status" and for "nlockmgr" on all machines different ports, so i read after searching, that this ports normally will be assigned dynamically different. ok, so far.
BUT why was this setup working with SUSEfirewall2 and NOT with firewalld
i have not changed anything to my nfs settings.
how made the trick to let firewalld find and open this dynamically changing port-numbers as (it must be i think) susefirewall2 has done automatically???????????
or is the only solution to gave here fix numbers? i found hundred of hits at a search, but this would be a back-step in compare to susefirewall2 and this i will not believe....
Indeed SuSEfirewall2 knows how to handle those dynamic ports. The words "rpc" apply: FW_SERVICES_EXT_RPC="mountd nfs" FW_CONFIGURATIONS_EXT="nfs-client nfs-kernel-server" FW_SERVICES_ACCEPT_EXT="192.168.1.0/24,_rpc_,nfs 192.168.1.0/24,tcp,nfs" FW_TRUSTED_NETS="192.168.1.0/24,tcp,nfs" How any of that is done with firewalld I have no idea, sorry. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.0 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org