Thorsten Kukuk wrote:
On Tue, Mar 13, Per Jessen wrote:
On a test system with leap15 -
Yesterday when I was playing with the yast nfs client module, I noticed it was using ipv4 for the rpc call to "rainbow" (the nfs server) to list the exported shares. The test system is dual-stack, so I thought that was odd. I then booted it as ipv6-only, and now it used ipv6 to query the nfs server. Revert to dual-stack, and it defaults to ipv4 again.
Other tools - e.g. ping and nfs-ls, correctly use the ipv6 address.
What is correct? I don't know the current situation, but I know a lot of tools of complicated algorithm to find out if ipv4 or ipv6 would be the better match. And if it is dual-stack, it shouldn't matter what is used.
For RPC: the config file is /etc/netconfig. And there, IPv4 is before IPv6.
From the changelog of libtirpc, I see you fixed something for SLES12:
* Thu Jan 21 2016 kukuk@suse.de - Remove 004-netconfig-prefer-IPv6.patch for SLES12. Anyway, it's not important, I was just surprised that something should want to override /etc/gai.conf. -- Per Jessen, Zürich (7.7°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org