Hello new Genasha user here, using it under Ubuntu for serving NFS4. Problem: ======== If I configure ganesha to bind to ipv4 address it serves NFS4 alright: NFS_CORE_PARAM { Protocols = 4; Bind_addr = 192.168.0.47; } However if I bind it to the IPv6 address on the same Ethernet interface, the dæmon fails to start: NFS_CORE_PARAM { Protocols = 4; Bind_addr = fe80::39a5:1385:634b:cb87; } The error is: Cannot bind NFS udp6 socket, error 22 (Invalid argument) Full error log at the end of the mail. Attempts to solve: ================== Since the error indicates a problem in binding NFS, I thought to try 9P just to see if the problem is NFS-specific. So I changed the configuration to: NFS_CORE_PARAM { Protocols = 9P; Bind_addr = fe80::39a5:1385:634b:cb87; } And the dæmon starts successfully without error, however, it was bound to *:564 Result is that other hosts can connect to port 564 using IPv4 address, not what I thought Bind_addr does. I suspect there is a bug in this behaviour. Full Error Log (with NFS4) ========================== 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5836[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 3.0.3 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper. 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized. 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: =ep cap_sys_resource-ep 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] Bind_sockets_V6 :DISP :WARN :Cannot bind NFS udp6 socket, error 22 (Invalid argument) 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd-5842[main] Bind_sockets :DISP :FATAL :Error binding to V6 interface. Cannot continue.
You are hitting one of the areas where our IPv6 support is incomplete. None of the major project contributors has had IPv6 support as a primary feature support so testing has been limited. We really need to clean this all up and properly test... Frank
-----Original Message----- From: a@colourful.land [mailto:a@colourful.land] Sent: Monday, March 15, 2021 6:35 PM To: support@lists.nfs-ganesha.org Subject: [NFS-Ganesha-Support] How to bind to ipv6 address?
Hello new Genasha user here, using it under Ubuntu for serving NFS4.
Problem: ========
If I configure ganesha to bind to ipv4 address it serves NFS4 alright:
NFS_CORE_PARAM { Protocols = 4; Bind_addr = 192.168.0.47; }
However if I bind it to the IPv6 address on the same Ethernet interface, the dæmon fails to start:
NFS_CORE_PARAM { Protocols = 4; Bind_addr = fe80::39a5:1385:634b:cb87; }
The error is:
Cannot bind NFS udp6 socket, error 22 (Invalid argument)
Full error log at the end of the mail.
Attempts to solve: ==================
Since the error indicates a problem in binding NFS, I thought to try 9P just to see if the problem is NFS-specific. So I changed the configuration to:
NFS_CORE_PARAM { Protocols = 9P; Bind_addr = fe80::39a5:1385:634b:cb87; }
And the dæmon starts successfully without error, however, it was bound to
*:564
Result is that other hosts can connect to port 564 using IPv4 address, not what I thought Bind_addr does. I suspect there is a bug in this behaviour.
Full Error Log (with NFS4) ==========================
16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5836[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 3.0.3 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper. 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized. 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: =ep cap_sys_resource-ep 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] Bind_sockets_V6 :DISP :WARN :Cannot bind NFS udp6 socket, error 22 (Invalid argument) 16/03/2021 12:21:10 : epoch 60500806 : vnaeli-ga990fxaud5 : ganesha.nfsd- 5842[main] Bind_sockets :DISP :FATAL :Error binding to V6 interface. Cannot continue.
participants (2)
-
a＠colourful.land -
Frank Filz