CADO-NFS on windows

[Andy]

Hi,


I try to build cado-nfs, but run into following issue.
Appreciate for any help

$ make
[  0%] Configuring gf2x
Configuring gf2x with options --disable-shared --disable-dependency-tracking --enable-fft-interface CC=/usr/bin/cc CXX=/usr/bin/c++.exe CFLAGS=-std=c99 -g -W -Wall -O2  -I/usr/include -I/home/myUser/BC/cado-nfs CXXFLAGS=-std=c++11 -Wno-c++11-compat -g -W -Wall -O2  -Wno-literal-suffix -I/usr/include -I/home/myUser/BC/cado-nfs LDFLAGS=-Wl,-rpath,/usr/lib -L/usr/lib
configure: error: cannot run /bin/sh /home/myUser/BC/cado-nfs/gf2x/config/config.sub
make[2]: *** [CMakeFiles/gf2x-build.dir/build.make:64: gf2x/Makefile] Error 2
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/gf2x-build.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
make: *** [Makefile:7: all] Error 2

[wombatman]

For anyone operating with WSL2 and trying to connect to a CADO-NFS server hosted within WSL2, you have to do something particular to connect the virtual ethernet adapter created for WSL2 with your actual network connection. See link:

https://www.williamjbowman.com/blog/...er-from-wsl-2/

In particular, this step:

netsh interface portproxy add v4tov4 listenport=$PORT listenaddress=0.0.0.0 connectport=$PORT connectaddress=127.0.0.1

followed by setting an inbound rule for the port of choice.

I've done this and can confirm that it works. What I'm not clear on is whether you will have to repeat this process every time you restart WSL2/your computer as I've not done that yet.

[henryzz]

If you do need to repeat it after rebooting you could add it to .bashrc

[wombatman]

Originally Posted by henryzz

If you do need to repeat it after rebooting you could add it to .bashrc

It needs to be run in Windows Powershell, but someone posted a Powershell script for it elsewhere.

https://dev.to/vishnumohanrk/wsl-port-forwarding-2e22

I haven't tried this script, but it does the same thing more or less.