Windows

Posted on Edited on In , ,
Some Configuration on Windows

1. Proxy

1.1. In WSL

1.1.1. Use the Windows proxy in WSL1

1
2
export http_proxy=socks://127.0.0.1:10808
export https_proxy=socks://127.0.0.1:10808

For fish user

1
2
3
4
if test $(grep Microsoft /proc/version)
  set -x http_proxy socks://127.0.0.1:10808
  set -x https_proxy socks://127.0.0.1:10808
end

Then verify the setting with curl google.com.

When http(s)_proxy is set you can see the log in your proxy on Windows when you run curl google.com. Be careful about the 127.0.0.1 which is the loop back address of local host, the port 10808 which is defined in your windows proxy app, and socks is the protocol which also defined in your windows proxy app.

Sometimes there is an error curl: (6) SOCKS4 connection to 2404:6800:4003:c0f::65 not supported. It is the error of socks. Use socks5,

1
2
3
4
if test $(grep Microsoft /proc/version)
  set -x http_proxy socks5://127.0.0.1:10808
  set -x https_proxy socks5://127.0.0.1:10808
end

1.1.2. Use the Windows proxy in WSL2

cat /etc/resolv.conf to obtain the target ip.

1
2
3
4
if test $(grep Microsoft /proc/version)
  set -x http_proxy socks://target ip:10808
  set -x https_proxy socks://target ip:10808
end

For the windows side, open allow the connection from local area network in your agent software.

2. X server

2.1. On the Windows side: Xming

I also tried VcXsrv. However, it failed to be launch. Thus I installed xming. After installing, notice that No Access Control may should be picked when start Xlaunch. Then a progress xming server will be started (see it in your task bar).

Windows Side Done.

2.2. On the linux side: $DISPLAY

The DISPLAY variable should be set as :0.0. For bash shell, write export DISPLAY=:0.0 in your .bashrc. For fish shell, write set -x DISPLAY :0.0 in your fish configuration file.

Then you can run a gui program on your linux and get the window on the Windows side.

2.3. For Remote Linux

Add the following lines in your bashrc.

1
2
export DISPLAY=local ip:0.0
export $(dbus-launch)

Be careful, when you start your Xming, pick No Access Control. When you use local wsl, No Access Control makes no sense.