blocks|key|240137|text|TL;DR：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|240138|将以下内容添加到~/.bashrc中|offset|length|style|CODE|240139|export+DISPLAY=$(ip+route+list+default+%7C+awk+'{print+$3}'):0
export+LIBGL_ALWAYS_INDIRECT=1|code-block|syntax|javascript|240140|在Windows的X11服务器上启用公共访问。*|BOLD|240141|将单独的入站规则用于TCP端口6000到windows防火墙，以允许WSL访问X服务器，正如wsl-windows-工具栏-启动器人员所描述的那样。|240142|正如mod在编辑所指出的，正如您可以在微软关于WSL2的文档中看到的那样，WSL2体系结构使用虚拟化的网络组件。这意味着WSL2的IP地址与主机不同。这解释了为什么X11转发设置WSL1不能简单地传输到WSL2。|240143|在有关WSL的Ubuntu页面上，您已经可以在运行图形应用程序下找到适合于运行图形应用程序的配置。上述Reddit用户也提出了类似的配置，他还提供了解决方案的另一部分:在X11服务器上启用Windows下的公共访问。|240144|这意味着在~/.bashrc中添加以下内容|240145|export+DISPLAY=$(ip+route+list+default+%7C+awk+'{print+$3}'):0
export+LIBGL_ALWAYS_INDIRECT=1|240146|和在X11服务器上为Windows启用公共访问。|240147|在Windows+10上启用X11+WSL2转发的最重要部分仍然缺少:默认情况下，Windows防火墙通过为WSL2配置的网络接口阻塞连接。|240148|需要一个单独的入站规则用于TCP端口6000，以允许WSL访问X服务器。在创建规则之后，正如wsl-windows-工具栏-启动器人员所描述的那样，IP地址范围可以限制在新创建规则的设置中的WSL子网中，在作用域：172.16.0.0/12下。|240149|*：如果使用VcXSrv，则可以通过禁用额外设置上的访问控制来启用X服务器的公共访问：|240150|📷|atomic|240151|或者使用vcxsrv.exe标志ac：vcxsrv.exe+-ac直接调用github，这是阿米诺在github问题上指出的。|240152|或者，这就是答案展示了如何通过.Xauthority文件共享密钥，从而使您拥有完整的访问控制。|240153|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/cascadium/wsl-windows-toolbar-launcher#firewall-rules|1|https://www.reddit.com/r/bashonubuntuonwindows/comments/dq541z/megathread_if_you_are_using_wsl2_networking_is/|2|https://learn.microsoft.com/en-us/windows/wsl/wsl2-faq#will-wsl-2-be-able-to-use-networking-applications|3|https://wiki.ubuntu.com/WSL#Running_Graphical_Applications|4|5|6|https://sourceforge.net/projects/vcxsrv/|7|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/51e7cb31bdf64bf6a30b81612253d747.png|imageAlt|8|https://github.com/microsoft/WSL/issues/4106#issuecomment-502989345|9|https://stackoverflow.com/a/66768217/9343156^0|0|8|9|0|0|0|M|0|4|4|A|9|1A|J|0|0|2|6|1|J|B|2|0|N|8|3|11|8|4|0|5|9|0|0|1|M|0|0|7|4|D|9|2V|3|1A|J|5|0|6|6|6|0|0|1|7|0|4|A|G|2|J|E|1A|3|8|0|3|5|9|0^^$0|@$1|2|3|4|5|6|7|26|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|27|8|@$D|28|E|29|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|2A|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|2B|8|@$D|2C|E|2D|F|O]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|2E|8|@$D|2F|E|2G|F|O]|$D|2H|E|2I|F|O]]|9|@$D|2J|E|2K|1|2L]]|A|$]]|$1|R|3|S|5|6|7|2M|8|@]|9|@$D|2N|E|2O|1|2P]|$D|2Q|E|2R|1|2S]]|A|$]]|$1|T|3|U|5|6|7|2T|8|@]|9|@$D|2U|E|2V|1|2W]|$D|2X|E|2Y|1|2Z]]|A|$]]|$1|V|3|W|5|6|7|30|8|@$D|31|E|32|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|J|7|33|8|@]|9|@]|A|$K|L]]|$1|Z|3|10|5|6|7|34|8|@$D|35|E|36|F|O]]|9|@]|A|$]]|$1|11|3|12|5|6|7|37|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|38|8|@$D|39|E|3A|F|O]|$D|3B|E|3C|F|O]|$D|3D|E|3E|F|O]]|9|@$D|3F|E|3G|1|3H]]|A|$]]|$1|15|3|16|5|6|7|3I|8|@]|9|@$D|3J|E|3K|1|3L]]|A|$]]|$1|17|3|18|5|19|7|3M|8|@]|9|@$D|3N|E|3O|1|3P]]|A|$]]|$1|1A|3|1B|5|6|7|3Q|8|@$D|3R|E|3S|F|G]|$D|3T|E|3U|F|G]|$D|3V|E|3W|F|G]]|9|@$D|3X|E|3Y|1|3Z]]|A|$]]|$1|1C|3|1D|5|6|7|40|8|@]|9|@$D|41|E|42|1|43]]|A|$]]|$1|1E|3|-4|5|6|7|44|8|@]|9|@]|A|$]]]|1F|$1G|$5|1H|1I|1J|A|$1K|1L]]|1M|$5|1H|1I|1J|A|$1K|1N]]|1O|$5|1H|1I|1J|A|$1K|1P]]|1Q|$5|1H|1I|1J|A|$1K|1R]]|1S|$5|1H|1I|1J|A|$1K|1R]]|1T|$5|1H|1I|1J|A|$1K|1L]]|1U|$5|1H|1I|1J|A|$1K|1V]]|1W|$5|1X|1I|1Y|A|$1Z|20|21|-4]]|22|$5|1H|1I|1J|A|$1K|23]]|24|$5|1H|1I|1J|A|$1K|25]]]]

<h3>TL;DR:</h3>
Add the following to your <code>~/.bashrc</code>:
<pre class="lang-bash prettyprint-override"><code>export DISPLAY=$(ip route list default | awk '{print $3}'):0
export LIBGL_ALWAYS_INDIRECT=1
</code></pre>
Enable Public Access on your X11 server for Windows.*
Add a separate inbound rule for TCP port 6000 to the windows firewall in order to allow WSL access to the X server, as described by the <a href="https://github.com/cascadium/wsl-windows-toolbar-launcher#firewall-rules" rel="noreferrer">wsl-windows-toolbar-launcher</a> people.
<hr />
As pointed out <a href="https://www.reddit.com/r/bashonubuntuonwindows/comments/dq541z/megathread_if_you_are_using_wsl2_networking_is/" rel="noreferrer">by WSL_subreddit_mod on reddit</a> and as you can read in <a href="https://learn.microsoft.com/en-us/windows/wsl/wsl2-faq#will-wsl-2-be-able-to-use-networking-applications" rel="noreferrer">Microsoft's documentation on WSL2</a>, the WSL2 architecture uses virtualized network components. This means that WSL2 has a different IP address than the host machine.
This explains why the X11 forwarding settings of WSL1 cannot simply be transferred to WSL2.
On the Ubuntu Wiki page about WSL you can already find a configuration adapted for WSL2 under <a href="https://wiki.ubuntu.com/WSL#Running_Graphical_Applications" rel="noreferrer">Running Graphical Applications</a>. A similar configuration is also suggested by the above mentioned Reddit User, who also contributes another part of the solution: Enable Public Access on the X11 server under Windows.
This means add the following to your <code>~/.bashrc</code>:
<pre class="lang-bash prettyprint-override"><code>export DISPLAY=$(ip route list default | awk '{print $3}'):0
export LIBGL_ALWAYS_INDIRECT=1
</code></pre>
And Enable Public Access on your X11 server for Windows.*
The most important part to enable X11 forwarding for WSL2 on Windows 10 is still missing: the Windows firewall blocks connections via the network interface configured for WSL by default. 
A separate inbound rule for TCP port 6000 is required to allow WSL access to the X server. After the rule has been created, as described by the <a href="https://github.com/cascadium/wsl-windows-toolbar-launcher#firewall-rules" rel="noreferrer">wsl-windows-toolbar-launcher</a> people, the IP address range can be restricted to the WSL subnet in the settings of the newly created rule, under Scope: 172.16.0.0/12.
*: If you use <a href="https://sourceforge.net/projects/vcxsrv/" rel="noreferrer">VcXSrv</a> you can enable public access for your X server by disabling Access Control on the Extra Settings: 
<a href="https://i.stack.imgur.com/6C7AT.png" rel="noreferrer"><img src="https://i.stack.imgur.com/6C7AT.png" alt="Disable access control VcXSrv" /></a> 
Or by calling <code>vcxsrv.exe</code> directly with the <code>ac</code> flag: <code>vcxsrv.exe -ac</code> as pointed out by <a href="https://github.com/microsoft/WSL/issues/4106#issuecomment-502989345" rel="noreferrer">ameeno</a> on the github issue.
Alternatively <a href="https://stackoverflow.com/a/66768217/9343156">this SO answer</a> shows how to share keys via .Xauthority files, leaving you with intact access control.

blocks|key|871426|text|我不知道这是否特定于我的配置，但这些解决方案不能在我的计算机上工作。他们返回地址192.168.0.254，这是我的网关，而不是我的主机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|871427|为了使它正常工作，我必须在我的Ubuntu/WSL2+2上使用以下内容：|871428|export+DISPLAY="`ip+-4+address+%7C+grep+-A1+eth0+%7C+grep+inet+%7C+cut+-d'+'+-f6+%7C+cut+-d/+-f1`:0"|code-block|syntax|javascript|871429|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I don't know if that's specific to my configuration but these solutions don't work on my computer. They return the address 192.168.0.254 which is my gateway and not my host computer.
To make it work I had to use the following on my Ubuntu/WSL2 :
<pre><code>export DISPLAY=&quot;`ip -4 address | grep -A1 eth0 | grep inet | cut -d' ' -f6 | cut -d/ -f1`:0&quot;
</code></pre>

blocks|key|871477|text|对于那些可能使用模拟引擎的人，如ROS/Gazebo、Unity等，还需要另一种配置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|871478|将这些添加到~/.bashrc中|CODE|871479|export+DISPLAY=$(awk+'/nameserver+/+{print+$2;+exit}'+/etc/resolv.conf+2>/dev/null):0
export+LIBGL_ALWAYS_INDIRECT=0|code-block|syntax|javascript|871480|确保在windows中为您的服务器启用公共访问和私有访问。还禁用X11服务器支持的任何访问控制。|871481|如果您使用VcXSrv，取消检查本机opengl。VcXSrv的最终配置如下：|871482|​|871483|📷|atomic|871484|871485|另一种较好的X11服务器是X410和MobaXterm，它们的难度较小。有关此配置的一些详细信息，请参阅这里和这里。|871486|entityMap|0|LINK|mutability|MUTABLE|url|https://sourceforge.net/projects/vcxsrv/|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/70f1696576ad56a9f9d5374e3babd110.png|imageAlt|2|https://x410.dev/|3|https://mobaxterm.mobatek.net/|4|https://discourse.ubuntu.com/t/getting-graphical-applications-to-work-on-wsl2/11868|5|https://medium.com/fresnostatedx/ros-environment-setup-for-windows-without-virtualbox-8fc14faad59e^0|8|4|G|A|0|6|9|0|0|E|5|T|J|0|0|13|5|6|0|0|0|1|0|0|1|0|1|1|0|0|1|0|0|1M|D|4|2|I|9|3|1G|2|4|1J|2|5|0^^$0|@$1|2|3|4|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1Q|8|@$9|1R|A|1S|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1T|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1U|8|@$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1Z|8|@$9|20|A|21|B|C]]|D|@$9|22|A|23|1|24]]|E|$]]|$1|R|3|S|5|6|7|25|8|@$9|26|A|27|B|C]]|D|@]|E|$]]|$1|T|3|U|5|V|7|28|8|@$9|29|A|2A|B|C]]|D|@$9|2B|A|2C|1|2D]]|E|$]]|$1|W|3|S|5|6|7|2E|8|@$9|2F|A|2G|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|2H|8|@$9|2I|A|2J|B|C]]|D|@$9|2K|A|2L|1|2M]|$9|2N|A|2O|1|2P]|$9|2Q|A|2R|1|2S]|$9|2T|A|2U|1|2V]]|E|$]]|$1|Z|3|-4|5|6|7|2W|8|@]|D|@]|E|$]]]|10|$11|$5|12|13|14|E|$15|16]]|17|$5|18|13|19|E|$1A|1B|1C|-4]]|1D|$5|12|13|14|E|$15|1E]]|1F|$5|12|13|14|E|$15|1G]]|1H|$5|12|13|14|E|$15|1I]]|1J|$5|12|13|14|E|$15|1K]]]]

For those who may work with simulation engines such as ROS/Gazebo, Unity and so on, another configuration is needed.
Add these to <code>~/.bashrc</code>:
<pre><code>export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2&gt;/dev/null):0
export LIBGL_ALWAYS_INDIRECT=0
</code></pre>
Be sure to enable both Public Access and Private Access for your X11 server in windows. Also disable any access control your X11 server supports.
If you use <a href="https://sourceforge.net/projects/vcxsrv/" rel="noreferrer">VcXSrv</a> uncheck Native opengl. Final config for VcXSrv will be like:
<a href="https://i.stack.imgur.com/Oa55F.png" rel="noreferrer"><img src="https://i.stack.imgur.com/Oa55F.png" alt="enter image description here" /></a>
Alternative good X11 servers with less difficulties are <a href="https://x410.dev/" rel="noreferrer">X410</a> and <a href="https://mobaxterm.mobatek.net/" rel="noreferrer">MobaXterm</a>. For some details about this configuration refer <a href="https://discourse.ubuntu.com/t/getting-graphical-applications-to-work-on-wsl2/11868" rel="noreferrer">here</a> and <a href="https://medium.com/fresnostatedx/ros-environment-setup-for-windows-without-virtualbox-8fc14faad59e" rel="noreferrer">here</a>.

blocks|key|1083952|text|使用/etc/resolv.conf名称服务器不适合我，因为我在/etc/wsl.conf中禁用了resolv.conf生成(我有一个自定义的resolv.conf)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1083953|最终，您需要WSL2主机IP地址，这也应该是您的默认路由。下面是我的Debian+WSL2发行版的WSL2条目：|1083954|export+DISPLAY=$(ip+route+%7C+awk+'/%5Edefault/{print+$3;+exit}'):0|code-block|syntax|javascript|1083955|entityMap^0|2|G|W|D|1D|B|1Z|B|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

Using <code>/etc/resolv.conf</code> nameserver won't work for me since I disabled <code>resolv.conf</code> generation in <code>/etc/wsl.conf</code> (I have a custom <code>resolv.conf</code>).
Ultimately you want the WSL2 host IP address, which should also be your default route. Here's my <code>~/.bashrc</code> entry for my Debian WSL2 distro:
<pre><code>export DISPLAY=$(ip route | awk '/^default/{print $3; exit}'):0
</code></pre>

blocks|key|240345|text|对于一些只允许我这样的私人网络的人来说，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|240346|虽然是，但它们都应该是|offset|length|style|BOLD|240347|​|240348|📷|atomic|240349|240350|它应该在Windows防御防火墙上有停止标志|240351|240352|240353|240354|双击它并允许为私有和公共连接，|240355|240356|240357|240358|所以这四个项目都应该是绿色的。|240359|然后@NicolasBrauer的上述回答是为我工作的。|240360|例如，当您的XLaunch和|240361|export+DISPLAY=$(awk+'/nameserver+/+{print+$2;+exit}'+/etc/resolv.conf+2>/dev/null):0
export+LIBGL_ALWAYS_INDIRECT=1|code-block|syntax|javascript|240362|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/1b6bdc79e951cd20a9646b051d2e4a98.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/1bc7a0722fb8b48a0d0d66619e85ebbb.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/ea89bfef59da56c2d370e09c2bbb36e7.png^0|0|3|8|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1M|8|@$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1P|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1Q|8|@]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|M|3|I|5|6|7|1U|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1V|8|@]|9|@]|A|$]]|$1|P|3|I|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Q|3|K|5|L|7|1X|8|@]|9|@$D|1Y|E|1Z|1|20]]|A|$]]|$1|R|3|I|5|6|7|21|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|22|8|@]|9|@]|A|$]]|$1|U|3|I|5|6|7|23|8|@]|9|@]|A|$]]|$1|V|3|K|5|L|7|24|8|@]|9|@$D|25|E|26|1|27]]|A|$]]|$1|W|3|I|5|6|7|28|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|29|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2A|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2B|8|@]|9|@]|A|$]]|$1|13|3|14|5|15|7|2C|8|@]|9|@]|A|$16|17]]|$1|18|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|1F|1G|-4]]|1H|$5|1B|1C|1D|A|$1E|1I|1G|-4]]|1J|$5|1B|1C|1D|A|$1E|1K|1G|-4]]]]

For some people who allowed only for private networks like me,
although they Should have been Both Ticked
<a href="https://i.stack.imgur.com/8jLEn.png" rel="noreferrer"><img src="https://i.stack.imgur.com/8jLEn.png" alt="enter image description here" /></a>
It should have stop signs on Windows Defender firewall
<a href="https://i.stack.imgur.com/AVL5m.png" rel="noreferrer"><img src="https://i.stack.imgur.com/AVL5m.png" alt="enter image description here" /></a>
Double click it and allow the connection for both private and public,
<a href="https://i.stack.imgur.com/P0z22.png" rel="noreferrer"><img src="https://i.stack.imgur.com/P0z22.png" alt="enter image description here" /></a>
So all the 4 items should be ticked green.
Then the above answer from @NicolasBrauer was working for me.
Like disabling the access control when you XLaunch and
<pre><code>export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2&gt;/dev/null):0
export LIBGL_ALWAYS_INDIRECT=1
</code></pre>

blocks|key|871632|text|抄袭了这个github问题的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|871633|这个想法是利用这种能力通过stdio进行交流。|871634|先决条件|871635|这样我们就可以在Windows主机上使用socat，您需要运行WSL1的发行版。我相信你可以在powershell中做到这一点，但我没有时间去研究这个问题。也许有人可以在powershell中编写一个stdio->tcp重定向器，那么我们就不需要有2个WSL发行版了。|unordered-list-item|871636|如何转发X-服务器连接|871637|让您最喜欢的X服务器在Windows上运行。默认情况下，他们会监听6000端口。|ordered-list-item|871638|在WSL2发行版中，在后台运行以下命令(ubuntu是安装了socat的WSL1发行版的名称)：|style|CODE|871639|mkdir+-p+/tmp/.X11-unix/
socat+UNIX-LISTEN:/tmp/.X11-unix/X0,fork+EXEC:"/mnt/c/Windows/System32/wsl.exe+-d+Ubuntu+socat+-+TCP\:localhost\:6000"|code-block|syntax|javascript|871640|基本上，这会建立一个隧道，从普通的tunnel域套接字到主机的端口6000。|871641|如何将任何TCP连接转发回主机|871642|让我们假设Windows上端口5555上有一个tcp服务正在运行。在WSL2发行版中，在后台运行以下命令(ubuntu是安装了socat的WSL1发行版的名称)：|871643|socat+TCP-LISTEN:5555,fork+EXEC:"/mnt/c/Windows/System32/wsl.exe+-d+ubuntu+socat+-+TCP\:localhost\:5555"|871644|如何将来自主机的TCP连接转发到WSL2|871645|这只是在做同样的事情，但却是相反的方向。您可以在WSL1发行版中运行以下命令：|871646|socat+TCP-LISTEN:5555,fork+EXEC:"/mnt/c/Windows/System32/wsl.exe+-d+ubuntuwsl2+socat+-+TCP\:localhost\:5555"|871647|性能|871648|在我的电脑上，它可以处理高达150+my+/s的数据，所以它不是最快的，但对大多数应用程序来说足够快。|871649|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/WSL/issues/4619#issuecomment-678652118^0|3|A|0|0|0|0|0|0|0|K|6|0|0|0|0|1H|6|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@$A|1P|B|1Q|1|1R]]|C|$]]|$1|D|3|E|5|6|7|1S|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1T|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1U|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1V|8|@]|9|@]|C|$]]|$1|M|3|N|5|O|7|1W|8|@]|9|@]|C|$]]|$1|P|3|Q|5|O|7|1X|8|@$A|1Y|B|1Z|R|S]]|9|@]|C|$]]|$1|T|3|U|5|V|7|20|8|@]|9|@]|C|$W|X]]|$1|Y|3|Z|5|6|7|21|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|22|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|23|8|@$A|24|B|25|R|S]]|9|@]|C|$]]|$1|14|3|15|5|V|7|26|8|@]|9|@]|C|$W|X]]|$1|16|3|17|5|6|7|27|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|28|8|@]|9|@]|C|$]]|$1|1A|3|1B|5|V|7|29|8|@]|9|@]|C|$W|X]]|$1|1C|3|1D|5|6|7|2A|8|@]|9|@]|C|$]]|$1|1E|3|1F|5|6|7|2B|8|@]|9|@]|C|$]]|$1|1G|3|-4|5|6|7|2C|8|@]|9|@]|C|$]]]|1H|$1I|$5|1J|1K|1L|C|$1M|1N]]]]

Copied my answer from <a href="https://github.com/microsoft/WSL/issues/4619#issuecomment-678652118" rel="noreferrer">this github issue</a>.
The idea is to use the ability to communicate over stdio.
<h3>Prerequisite</h3>
<ul>
<li>Just so we can use socat in Windows host, you need a distribution running WSL1. I am sure you can do this in powershell but I didn't have time to research this. Maybe someone can write a stdio-&gt;tcp redirector in powershell, then we wouldn't need to have 2 WSL distros.</li>
</ul>
<h3>How to forward X-server connection</h3>
<ol>
<li>Have your favorite X server running on Windows. By default they would listen to port 6000.</li>
<li>In the WSL2 distro, run the following command in the background (<code>ubuntu</code> is the name of the WSL1 distro with socat installed):</li>
</ol>
<pre><code>mkdir -p /tmp/.X11-unix/
socat UNIX-LISTEN:/tmp/.X11-unix/X0,fork EXEC:&quot;/mnt/c/Windows/System32/wsl.exe -d Ubuntu socat - TCP\:localhost\:6000&quot;
</code></pre>
Basically this sets up a tunnel from the normal X unix domain socket into the host's port 6000.
<h3>How to forward any TCP connection back to host</h3>
Let's assume there is a tcp service running at port 5555 on Windows. In the WSL2 distro, run the following command in the background (<code>ubuntu</code> is the name of the WSL1 distro with socat installed):
<pre><code>socat TCP-LISTEN:5555,fork EXEC:&quot;/mnt/c/Windows/System32/wsl.exe -d ubuntu socat - TCP\:localhost\:5555&quot;
</code></pre>
<h3>How to forward any TCP connection from host into WSL2</h3>
This is simply doing the same thing, but in the opposite direction. You can run the following in your WSL1 distro:
<pre><code>socat TCP-LISTEN:5555,fork EXEC:&quot;/mnt/c/Windows/System32/wsl.exe -d ubuntuwsl2 socat - TCP\:localhost\:5555&quot;
</code></pre>
<h3>Performance</h3>
On my PC, it can handle up to 150MB/s of data so it's not the fastest but fast enough for most applications.

blocks|key|240391|text|我成功地使用了开箱即用的VcXsrv防火墙配置(即不需要覆盖/禁用任何防火墙规则)，方法是使用Windows主机的局域网适配器IP。将以下内容添加到我的~/.bash_aliases中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|240392|export+DISPLAY=$(pwsh.exe+-c+ipconfig+%7C+grep+-A+3+lan+%7C+grep+IPv4+%7C+head+-1+%7C+awk+'{+print+$NF+}'):0|code-block|syntax|javascript|240393|其中lan是我特定于连接的DNS后缀(您的可能不同，在这种情况下，您应该在上面的命令行中替换它)。|240394|entityMap^0|24|F|0|0|2|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

I've managed to work with the out-of-the-box VcXsrv firewall configuration (i.e., no need to override/disable any firewall rules) by using the LAN adapter IP of the Windows host. Added the below to my <code>~/.bash_aliases</code>
<pre><code>export DISPLAY=$(pwsh.exe -c ipconfig | grep -A 3 lan | grep IPv4 | head -1 | awk '{ print $NF }'):0
</code></pre>
where <code>lan</code> is my Connection-specific DNS Suffix (yours may differ, in which case you should replace it in the command line above).

blocks|key|871684|text|以下解决方法适用于我：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|871685|-Name+$(Get).NetworkCategory+-DisabledInterfaceAliases+$(Get)|871686|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The following workaround works for me:
Set-NetFirewallProfile -Name $(Get-NetConnectionProfile).NetworkCategory -DisabledInterfaceAliases $(Get-NetAdapter | Where-Object Name -like 'WSL').Name

blocks|key|1084160|text|我使用以下bash设置显示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084161|export+DISPLAY=$(powershell.exe+-c+ipconfig+%7C+grep+-A4+WSL+%7C+tail+-1+%7C+awk+'{+print+$NF+}'+%7C+tr+-d+'\r'):0|code-block|syntax|javascript|1084162|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I used the following bash to set display:
<pre><code>export DISPLAY=$(powershell.exe -c ipconfig | grep -A4 WSL | tail -1 | awk '{ print $NF }' | tr -d '\r'):0
</code></pre>

blocks|key|1084187|text|我宁愿在来宾中设置ssh服务器，在主机上安装像Xming这样的X11服务器，并通过putty与X11转发连接到本地主机。不篡改防火墙规则，不需要主机IP。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084188|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would rather set up an ssh server in the guest,
install an X11 server like Xming on the host
and connect to localhost via putty with X11 forwarding.
No fiddling with firewall rules, host IP is not required.

blocks|key|240527|text|我发现有一份关于Ubuntu的正式文件，这份文件很全面，供你参考。正如我们所知道的，这个技巧同样适用于Debian/WSL2+2。https://wiki.ubuntu.com/WSL|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|240528|谢谢Kennyhyun和其他人的股份。在我的计算机上，所有这些都是如何或某种方式来启用托管在X11上的WSL2上的Windows10服务器。因为WSL2是作为VM的，所以不再是WSL1的基础结构。我确实花了些时间来经历它。|240529|请允许我简单地添加一些关于如何在WSL2上显示应用程序的内容。|240530|在WLS2终端上运行ip路由。
ip路由默认通过.b.c.1+dev+eth0+a.b.c.0/20+dev+eth0+proto内核范围链接src+x.x|ordered-list-item|240531|将"dev+eth0“的IP地址添加到”导出$DISPLAY=“中
导出$DISPLAY=a.b.c.1:0.0|240532|运行xming服务器。然后您可以运行运行在WSL2+Linux上的应用程序。但是对于X11，您可能需要遵循Ubuntu的文档。|240533|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.ubuntu.com/WSL^0|1T|R|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|C|$]]|$1|K|3|L|5|J|7|13|8|@]|9|@]|C|$]]|$1|M|3|N|5|J|7|14|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

I found there is a official document fro Ubuntu which is comprehensive for your reference. As we know, this tip will work on Debian/WSL2 as well.
<a href="https://wiki.ubuntu.com/WSL" rel="nofollow noreferrer">https://wiki.ubuntu.com/WSL</a>
Thanks for Kennyhyun and other people's shares. All of them are some how or some way works on my computer to enable X11 server on WSL2 hosted on Windows10. Since the WSL2 is as a VM not longer be the same infrastructure as WSL1 anymore. It did take me some time to go through it.
Please let me add something briefly about how to make app on WSL2 show up.
<ol>
<li>run 'ip route' on WLS2 terminal.
ip route
default via a.b.c.1 dev eth0
a.b.c.0/20 dev eth0 proto kernel scope link src x.x.x.x
</li>
<li>add this IP address of the &quot;dev eth0&quot; into &quot;export $DISPLAY=&quot;
export $DISPLAY=a.b.c.1:0.0
</li>
<li>Run xming server.
Then you could run the APP which is running on the WSL2 Linux. But for the X11, you may need to follow the document from Ubuntu.
</li>
</ol>

blocks|key|1084254|text|我不知道为什么，但上面的答案对我都没有用。我运行在一个带有AMD和Nvidia图形的ROG+Zephyrus上，我确信这引起了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084255|whme描述的防火墙设置很重要，但是linux环境变量对我来说不起作用。配置文件中有几个条目被标记为名称服务器，其中不允许连接。|1084256|最后我把他们设为：|1084257|export+DISPLAY=$HOSTNAME:0.0
export+LIBGL_ALWAYS_INDIRECT=|code-block|syntax|javascript|1084258|我正在使用VcXsrv作为X服务器.我还必须将参数设置为-nowgl|offset|length|style|CODE|1084259|entityMap^0|0|0|0|0|S|6|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I'm not sure why but none of the above answers worked for me. I'm running on an ROG Zephyrus with AMD and Nvidia graphics which I'm sure caused issues.
The firewall settings described by whme are important, but the linux environment variables did not work for me. I had several entries in the config file labeled as nameserver, non of which allowed connections.
I ended up setting them to:
<pre><code>export DISPLAY=$HOSTNAME:0.0
export LIBGL_ALWAYS_INDIRECT=
</code></pre>
I'm using VcXsrv as the X-server. I had to also set the parameters to <code>-nowgl</code>

blocks|key|871788|text|我找到了一个对我有用的解决方案，如下所示:在WSL2上设置图形|type|unstyled|depth|inlineStyleRanges|entityRanges|data|871789|1.++++++Start+ssh+service
1.1.+++Open+WSL
1.2.+++Type:+sudo+service+ssh+start
2.++++++Get+Windows+(WSL+net)+IP
2.1.+++Open+Powershell
2.2.+++Type:+(ipconfig+%7C+Select-String+-Pattern+'WSL'+-Context+1,+5).Context.PostContext+%7C+Select-String+-Pattern+'IPv4'
2.3.+++Get+the+received+IP
3.++++++Set+environment+variable
3.1.+++In+WSL2+terminal+type:+export+DISPLAY=172.23.64.1:0.0+with+the+IP+of+the+windows+entity+(2.3)+instead+of+the+place+holder
4.++++++Launch+Xming
4.1.+++Open+Xlaunch+and+go+with+the+defaults+In+Specify+parameter+settings:+Check+No+Access+Control
5.++++++Good+luck!|code-block|syntax|javascript|871790|以下链接：k4g8LCjxX23VX7E|offset|length|871791|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.google.com/document/d/1ao3vjbC3lCDc9kvybOT5PbuGhC4_k4g8LCjxX23VX7E^0|0|0|5|F|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I found a solution that worked for me, following:
Set Graphics on WSL2
<pre><code>1. Start ssh service
1.1. Open WSL
1.2. Type: sudo service ssh start
2. Get Windows (WSL net) IP
2.1. Open Powershell
2.2. Type: (ipconfig | Select-String -Pattern 'WSL' -Context 1, 5).Context.PostContext | Select-String -Pattern 'IPv4'
2.3. Get the received IP
3. Set environment variable
3.1. In WSL2 terminal type: export DISPLAY=172.23.64.1:0.0 with the IP of the windows entity (2.3) instead of the place holder
4. Launch Xming
4.1. Open Xlaunch and go with the defaults In Specify parameter settings: Check No Access Control
5. Good luck!
</code></pre>
Following link:
<a href="https://docs.google.com/document/d/1ao3vjbC3lCDc9kvybOT5PbuGhC4_k4g8LCjxX23VX7E" rel="nofollow noreferrer">https://docs.google.com/document/d/1ao3vjbC3lCDc9kvybOT5PbuGhC4_k4g8LCjxX23VX7E</a>

blocks|key|240646|text|来自https://github.com/microsoft/WSL/issues/4793#issuecomment-588321333的解决方案使用VcXsrv作为X服务器，我在这里得到了这个答案(为可读性做了一些编辑)。请注意，原稿正在由作者更新，所以不要忘记重新检查。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|240647|为了使它发挥作用：|blockquote|240648|在Windows上，通过以下操作，将E:\VcXsrv更改为安装所在的位置，并将其保存为Windows启动文件夹(例如，C:\Users\Me\AppData\Roaming\Microsoft\Windows\Start+Menu\Programs\Startup+)中的xxx.bat，如果愿意，您可以在启动时使其运行：|ordered-list-item|style|CODE|240649|@ECHO+OFF+REM启动wsl一次创建WSL网络接口WSL退出REM查找IP+for+WSL网络接口集WSL_IF_IP=调用:GetIp+"vEthernet+(WSL)“WSL_IF_IP+ECHO+WSL_IF_IP=%25WSL_IF_IP%25+setx+"WSL_IF_IP”"%25WSL_IF_IP%25“setx+"WSLENV”"WSL_IF_IP/u“REM更改E:\VcXsrv到VcXsrv安装文件夹Start+/D+"E:\VcXsrv”/B+vcxsrv.exe+-multiwindow+-clipboard+-nowglac+-displayfd+720+GOTO+:EOF+:+aInterface(+aIp+)(+SETLOCAL+EnableExtensions+EnableDelayedExpansion+FOR+/f+"tokens=3+delims=：“%25i+IN+('netsh接口ip显示地址"%25~1”%5E+findstr+IP')+DO+(+SET+RET=%25%25i+))(+ENDLOCAL集"%25~2=%25RET%25“退出/B+)|240650|在WSL中，编辑~/..bashrc文件以添加以下行：|240651|导出DISPLAY=$WSL_IF_IP:0未设置LIBGL_ALWAYS_INDIRECT|240652|这就是让WSL2自动工作的全部内容。其思想是在Windows上获取WSL接口的专用局域网IP，并使用环境变量将其传递给WSL。然后，WSL更新此LAN+IP以显示X连接.|240653|剪贴板的工作也很好，与此设置。我用Ubuntu20.04LTS的WSL2安装进行了测试。|240654|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/WSL/issues/4793#issuecomment-588321333^0|2|1V|0|0|0|I|9|1O|21|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|18|8|@$A|19|B|1A|J|K]|$A|1B|B|1C|J|K]]|9|@]|C|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|C|$]]|$1|N|3|O|5|I|7|1E|8|@]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1F|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|1G|8|@]|9|@]|C|$]]|$1|T|3|U|5|6|7|1H|8|@]|9|@]|C|$]]|$1|V|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]]]

The solution from <a href="https://github.com/microsoft/WSL/issues/4793#issuecomment-588321333" rel="nofollow noreferrer">https://github.com/microsoft/WSL/issues/4793#issuecomment-588321333</a> uses VcXsrv as the X-server, and it is where I'm getting this answer (slightly edited for readability). Note that the original is being updated by its author, so don't forget to re-check.
<blockquote>
To make it work:
<ol>
<li>On Windows, with the following, change <code>E:\VcXsrv</code> to where your installation is, and save it as xxx.bat in your Windows startup folder, e.g., <code>C:\Users\Me\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup</code>, and you can make it run when boot if you like:</li>
</ol>
<pre><code>@ECHO OFF

REM Start WSL once to create WSL network interface
wsl exit

REM Find IP for WSL network interface
SET WSL_IF_IP=
CALL :GetIp &quot;vEthernet (WSL)&quot; WSL_IF_IP
ECHO WSL_IF_IP=%WSL_IF_IP%
setx &quot;WSL_IF_IP&quot; &quot;%WSL_IF_IP%&quot;
setx &quot;WSLENV&quot; &quot;WSL_IF_IP/u&quot;

REM Change E:\VcXsrv to your VcXsrv installation folder
START /D &quot;E:\VcXsrv&quot; /B vcxsrv.exe -multiwindow -clipboard -nowgl -ac -displayfd 720
GOTO :EOF



:GetIp ( aInterface , aIp )
(
 SETLOCAL EnableExtensions EnableDelayedExpansion
 FOR /f &quot;tokens=3 delims=: &quot; %%i IN ('netsh interface ip show address &quot;%~1&quot; ^| findstr IP') DO (
 SET RET=%%i
 )
)
(
 ENDLOCAL
 SET &quot;%~2=%RET%&quot;
 EXIT /B
)
</code></pre>
<ol start="2">
<li>In WSL, edit ~/.bashrc file to add following lines:</li>
</ol>
<pre><code>export DISPLAY=$WSL_IF_IP:0
unset LIBGL_ALWAYS_INDIRECT
</code></pre>
That's all to make WSL2 work automatically. The idea is to get the private LAN IP of WSL interface on Windows, and use Environment variable to pass it to WSL. WSL then updates this LAN IP to DISPLAY for X-Server connection.
</blockquote>
The clipboard works well, too, with this setup. I tested this with a WSL2 install of Ubuntu 20.04 LTS.

blocks|key|1084393|text|下面是我编写的两篇文章，介绍如何为不同类型的用例设置x11：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084394|在WSL2中安装具有图形用户界面的程序：本文将介绍如何安装vcxsrv，将环境变量添加到bashrc配置文件中，并以编程方式调度vcxsrv在启动时使用命令行参数启动。它还包括安装和启动火狐作为一个独立的程序在WSL2。|ordered-list-item|offset|length|1084395|在WSL2中使用图形用户界面安装Ubuntu本文介绍了安装vcxsrv、dotNet、genie和Ubuntu桌面的过程。它包括创建导出环境变量的脚本，启动vcxsrv，启动gnome桌面环境，并创建将它们连接在一起的快捷方式。它还包括运行Ubuntu桌面、防止屏幕锁定错误和安装Store。|1084396|entityMap|0|LINK|mutability|MUTABLE|url|https://thealtruist.medium.com/how-to-install-programs-with-a-graphical-user-interface-gui-in-wsl2-e8ea9476cb78|1|https://thealtruist.medium.com/how-to-install-ubuntu-with-a-graphical-user-interface-gui-in-wsl2-5c188c0a261a^0|0|0|J|0|0|0|M|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@$E|U|F|V|1|W]]|A|$]]|$1|G|3|H|5|D|7|X|8|@]|9|@$E|Y|F|Z|1|10]]|A|$]]|$1|I|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]|Q|$5|L|M|N|A|$O|R]]]]

Here are two articles I wrote that walks through setting up x11 for different types of use cases:
<ol>
<li><a href="https://thealtruist.medium.com/how-to-install-programs-with-a-graphical-user-interface-gui-in-wsl2-e8ea9476cb78" rel="nofollow noreferrer">Install a Program With a Graphical User Interface in WSL2</a>: This article walks through installing vcxsrv, adding the environment variables to the bashrc configuration file, and programmatically scheduling vcxsrv to launch with command-line parameters at startup. It also covers installing and launching Firefox as a standalone program in WSL2.</li>
<li><a href="https://thealtruist.medium.com/how-to-install-ubuntu-with-a-graphical-user-interface-gui-in-wsl2-5c188c0a261a" rel="nofollow noreferrer">Install Ubuntu Desktop with a Graphical User Interface in WSL2</a> This article walks through installing vcxsrv, dotNet, genie, and the Ubuntu desktop. It covers creating the scripts that exports the environment variables, launches vcxsrv, starts the gnome desktop environment, and creates the shortcut that ties them all together. It also covers running the Ubuntu desktop, preventing a screen lock bug, and installing the Snap Store.</li>
</ol>

blocks|key|872101|text|如何在X11中设置WSL2转发|type|unstyled|depth|inlineStyleRanges|entityRanges|data|872102|这个答案假设您已经在您的Windows主机上运行了一个工作的XServer和PulseAudio配置，因为您已经在使用WSL1。(您还可能必须将-ac参数添加到命令行中，以使您的XServer使用WSL2。)|872103|为了确保在X11主机上使用静态IP地址或DHCP，甚至无论主机名或网络位置是否更改，我都要将以下内容添加到~/..bashrc文件中：|872104|#+Get+the+IP+Address+of+the+Windows+10+Host+and+use+it+in+Environment.
HOST_IP=$(host+`hostname`+%7C+grep+-oP+'(\s)\d%2B(\.\d%2B){3}'+%7C+tail+-1+%7C+awk+'{+print+$NF+}'+%7C+tr+-d+'\r')
export+LIBGL_ALWAYS_INDIRECT=1
export+DISPLAY=$HOST_IP:0.0
export+NO_AT_BRIDGE=1
export+PULSE_SERVER=tcp:$HOST_IP|code-block|syntax|javascript|872105|完成上述操作后，无论主机的主机名或IP地址是什么，每次在WSL2中启动BASH会话时，都会将其放置在环境中。通过从命令行运行firefox来测试它，并观看一个YouTube视频。你应该能够听到声音，也可以看到应用程序本身来观看视频。另外，通过从命令行启动其他GUI应用程序来进行测试。|872106|它所做的:它使用主机命令从输出中提取与主机名关联的IPv4地址，对与包含您的Windows+IPv4地址的行匹配的地址进行排序，除去除IP地址之外的其余信息，然后将其挂起并打印到变量中，并对输出进行修剪。然后使用它作为字符串提供必要的IP地址，以便在允许转发X11和声音输出的环境变量中使用。|872107|如果其他方法对你不起作用，希望它对你有效(就像它们对我一样)。|872108|大多数CLI应用程序可以从BASH提示符运行，也可以从Windows终端运行。如果您想要创建快捷方式，大多数CLI应用程序可以像下面的任何一个示例一样设置(在这种情况下不需要X11转发，只有Links2这样的应用程序除外)：|872109|C:\Windows\System32\wsl.exe+-e+htop
C:\Windows\System32\wsl.exe+lynx|872110|如果您想为Linux应用程序创建桌面快捷方式，除非您可以在启动程序之前从~/..bashrc文件中获取环境变量，否则必须使用以下模板创建快捷方式，并将程序名称替换为{+you+}：|872111|C:\Windows\System32\wsl.exe+LIBGL_ALWAYS_INDIRECT=Yes+IP=$(host+`hostname`+%7C+grep+-oP+'(\s)\d%2B(\.\d%2B){3}'+%7C+tail+-1+%7C+awk+'{+print+$NF+}'+%7C+tr+-d+'\r')+DISPLAY=$IP:0.0+PULSE_SERVER=tcp:$IP+{yourprogram}|872112|对于许多程序，您不必放置完整的命令行。对于基于PERL的程序或基于PYTHON的程序，有时需要添加PERL和PYTHON的路径以及程序的完整路径，才能在Linux中使用WSL2运行这样的GUI程序。对于我的一个perl程序，我必须这样做：|872113|C:\Windows\System32\wsl.exe+IP=$(host+`hostname`+%7C+grep+-oP+'(\s)\d%2B(\.\d%2B){3}'+%7C+tail+-1+%7C+awk+'{+print+$NF+}'+%7C+tr+-d+'\r')+;+export+LIBGL_ALWAYS_INDIRECT=Yes+export+DISPLAY=$IP:0.0+;+cd+/mnt/c/Users/{yourusername}/Desktop+;+/usr/bin/perl+~/wget-gui.pl|872114|为了让一些应用程序正常工作，你可能需要做一些实验。例如，您可能需要启动一个应用程序，并需要在程序名之前将该命令添加到快捷方式中。|872115|C:\Windows\System32\wsl.exe+LIBGL_ALWAYS_INDIRECT=Yes+IP=$(host+`hostname`+%7C+grep+-oP+'(\s)\d%2B(\.\d%2B){3}'+%7C+tail+-1+%7C+awk+'{+print+$NF+}'+%7C+tr+-d+'\r')+DISPLAY=$IP:0.0+PULSE_SERVER=tcp:$IP+dbus-launch+--exit-with-session+gedit|872116|在某些情况下，您可能需要使用较短的变量名。有些应用程序不能很好地工作，如果有的话，但这种情况随着时间的推移正在改善。另外，不要尝试从Windows提示符或PowerShell运行上述命令。它会抛出关于“grep”不被识别为内部或外部命令的错误，等等。|872117|下面是在我的Windows+10系统上运行的几个Linux应用程序的屏幕截图，以及在X11上运行的WSL2转发。|872118|​|872119|📷|atomic|offset|length|872120|872121|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/be6260e41b88ff6dfb7b0a218d0b3420.jpg|imageAlt^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1T|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1U|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1V|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1W|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1X|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|1Z|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|20|8|@]|9|@]|A|$]]|$1|W|3|X|5|H|7|21|8|@]|9|@]|A|$I|J]]|$1|Y|3|Z|5|6|7|22|8|@]|9|@]|A|$]]|$1|10|3|11|5|H|7|23|8|@]|9|@]|A|$I|J]]|$1|12|3|13|5|6|7|24|8|@]|9|@]|A|$]]|$1|14|3|15|5|H|7|25|8|@]|9|@]|A|$I|J]]|$1|16|3|17|5|6|7|26|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|27|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|28|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|1E|7|29|8|@]|9|@$1F|2A|1G|2B|1|2C]]|A|$]]|$1|1H|3|1B|5|6|7|2D|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]]|1J|$1K|$5|1L|1M|1N|A|$1O|1P|1Q|-4]]]]

<h2>How to Setup X11 forwarding in WSL2</h2>
This answer assumes that you already have a working XServer and PulseAudio configuration running on your Windows host because you already were using WSL1. (You also may have to add the -ac parameter to the command line to get your XServer of choice to work with WSL2.)
The way that I do this, and to ensure that I get X11 forwarding no matter whether I am using a static IP address or DHCP on the Windows host, or even whether my hostname or network location changes, I add the following to my ~/.bashrc file:
<pre><code># Get the IP Address of the Windows 10 Host and use it in Environment.
HOST_IP=$(host `hostname` | grep -oP '(\s)\d+(\.\d+){3}' | tail -1 | awk '{ print $NF }' | tr -d '\r')
export LIBGL_ALWAYS_INDIRECT=1
export DISPLAY=$HOST_IP:0.0
export NO_AT_BRIDGE=1
export PULSE_SERVER=tcp:$HOST_IP
</code></pre>
After doing the above, no matter what my Hostname or IP address of the Host is, it will be placed in the environment each time a BASH session is started in WSL2. Test it by running firefox from the command line and watch a YouTube video. You should be able to hear the sound as well as see the app itself to watch the video. Test by launching other GUI apps from the command line in addition.
What it does: It uses the host command to pull the IPv4 Addresses associated with the Hostname from the output, greps the address that matches the line that contains your Windows Host IPv4 address, strips the rest of the information except for the IP Address, and then awks that and prints it into the variable, with the output trimmed. This then is used to provide the necessary IP address as a string for use in the environment variables that allow for forwarding of X11 and sound output.
Hopefully it works for you if the other methods don't work for you (as they didn't for me).
Most CLI apps can be run either from the BASH Prompt or from Windows Terminal. If you want to make a shortcut, most CLI apps can be set up like either of the following examples (no need for X11 forwarding in such cases except apps like Links2):
<pre><code>C:\Windows\System32\wsl.exe -e htop
C:\Windows\System32\wsl.exe lynx
</code></pre>
If you want to create desktop shortcuts for Linux GUI apps, unless you can get the environment variables from your ~/.bashrc file to be used before launching the programs, you will have to create shortcuts using the following template, and put the program name in place of {yourprogram}:
<pre><code>C:\Windows\System32\wsl.exe LIBGL_ALWAYS_INDIRECT=Yes IP=$(host `hostname` | grep -oP '(\s)\d+(\.\d+){3}' | tail -1 | awk '{ print $NF }' | tr -d '\r') DISPLAY=$IP:0.0 PULSE_SERVER=tcp:$IP {yourprogram}
</code></pre>
You do not have to place the full command line for many programs. For PERL-based programs or Python-based programs, you sometimes will have to add the path for PERL and PYTHON, as well as your program's full path, to run such GUI programs in Linux using WSL2. For one of my perl programs, I have to do it this way:
<pre><code>C:\Windows\System32\wsl.exe IP=$(host `hostname` | grep -oP '(\s)\d+(\.\d+){3}' | tail -1 | awk '{ print $NF }' | tr -d '\r') ; export LIBGL_ALWAYS_INDIRECT=Yes export DISPLAY=$IP:0.0 ; cd /mnt/c/Users/{yourusername}/Desktop ; /usr/bin/perl ~/wget-gui.pl
</code></pre>
You may have to experiment a bit to get some apps working properly. For example, you might need to dbus-launch an app, and will need to add that command to the shortcut just before the program name.
<pre><code>C:\Windows\System32\wsl.exe LIBGL_ALWAYS_INDIRECT=Yes IP=$(host `hostname` | grep -oP '(\s)\d+(\.\d+){3}' | tail -1 | awk '{ print $NF }' | tr -d '\r') DISPLAY=$IP:0.0 PULSE_SERVER=tcp:$IP dbus-launch --exit-with-session gedit
</code></pre>
And you might have to use a shorter variable name in some circumstances. Some apps just won't work well, if at all, but this situation is improving over time. Also, don't try to run the above from a Windows Command Prompt or from PowerShell. It will throw errors about 'grep' not being recognized as an internal or external command, etc.
Following is a screenshot of a few Linux GUI apps running on my Windows 10 system, with working X11 forwarding on WSL2.
<a href="https://i.stack.imgur.com/H2utv.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/H2utv.jpg" alt="enter image description here" /></a>

blocks|key|240920|text|您可以连接到X服务器，而无需禁用服务器上的访问控制。您可以在服务器上使用xauth生成cookie，然后将其加载到Linux端的xauth中。您可以从/etc/rupv.conf获取服务器IP。在我的.bashrc中有以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|240921|k=$('/mnt/c/Program+Files/VcXsrv/xauth.exe'+-f+'C:\Users\xxx\Documents\scratch.xauth'+-i+-n+-q+2>/dev/null+<<EOF
generate+localhost:0+.+trusted+timeout+604800
list
quit
EOF
)
if+[+-n+"$k"+]
then
++++++++export+DISPLAY=$(sed+'/%5Enameserver/+{s/%5Enameserver\s\s*$[0-9][0-9.]*$[%5E0-9.]*$/\1/;p;};d'+/etc/resolv.conf):0
++++++++xauth+-q+add+$DISPLAY+.+${k##*+}
++++++++export+LIBGL_ALWAYS_INDIRECT=true
fi
unset+k|code-block|syntax|javascript|240922|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can get connect to the X server without disabling access control on the server. You use xauth on the server to generate a cookie, then load it into Linux with xauth on the Linux side. You can get the server IP from /etc/resolv.conf. The following is in my .bashrc:
<pre><code>k=$('/mnt/c/Program Files/VcXsrv/xauth.exe' -f 'C:\Users\xxx\Documents\scratch.xauth' -i -n -q 2&gt;/dev/null &lt;&lt;EOF
generate localhost:0 . trusted timeout 604800
list
quit
EOF
)
if [ -n &quot;$k&quot; ]
then
 export DISPLAY=$(sed '/^nameserver/ {s/^nameserver\s\s*$[0-9][0-9.]*$[^0-9.]*$/\1/;p;};d' /etc/resolv.conf):0
 xauth -q add $DISPLAY . ${k##* }
 export LIBGL_ALWAYS_INDIRECT=true
fi
unset k
</code></pre>

blocks|key|1084660|text|我不想扰乱对X服务器和Windows防火墙的公共访问。我的解决方案是在X转发中使用ssh+(也适用于VirtualBox+)。此外，WSL自动转发从主机到客户侦听套接字，所以我不关心哪个IP实际分配给来宾。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084661|这些步骤如下：|1084662|安装VcXSrv。使用所有默认值运行它，但将显示号设置为0+(-1将选择0，如果没有X实例正在运行)。不要在其中启动任何客户端(这样可以在同一个X服务器实例上启动更多的应用程序)。|ordered-list-item|1084663|打开WSL并配置ssh服务器。对我来说，它就像sudo+service+ssh+start一样简单。使用命令行创建Windows快捷方式：wsl+sudo+service+ssh+start。|offset|length|style|CODE|1084664|安装Git+for+Windows。实际上，我之所以使用它，只是因为它的ssh版本能够进入ssh+-f的后台。Windows版本的ssh在这个特性上是错误的，否则它适合在不使用背景或ssh+-n的情况下使用。|1084665|配置从Git-Bash到来宾的无密码登录。ssh+user@127.0.0.1在这一点上应该可以工作，因为主机端口被转发到客户端。|1084666|验证来自Git-Bash：DISPLAY=127.0.0.1:0+ssh+-Y+user@127.0.0.1+xeyes的X转发工作。我认为xeyes安装在每个X发行版中。|1084667|在WSL中安装您选择的文件管理器或终端。例如，pcmanfm。创建一个Windows快捷方式："C:\Program+Files\Git\git-bash.exe"+-c+"DISPLAY=127.0.0.1:0+ssh+-Y+-f+user@127.0.0.1+'bash+-l+-c+pcmanfm+>/dev/null+2>&1'"。在这里，bash+-l标志有助于设置环境，这可能是重要的，也可能不重要，这取决于您运行的应用程序。|1084668|当然，通过使用VcXSrv内置的ssh客户端，我可以在不使用git-bash的情况下进行同样的操作，但是它需要将ssh键转换成PuTTY格式，而且我已经安装了git-bash。此外，内置的客户端显示重用也不适用于我。|1084669|entityMap^0|0|0|0|N|M|1X|Q|0|19|6|2J|6|0|L|I|0|D|1B|0|1B|3E|4U|7|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|11|8|@$I|12|J|13|K|L]|$I|14|J|15|K|L]]|9|@]|A|$]]|$1|M|3|N|5|F|7|16|8|@$I|17|J|18|K|L]|$I|19|J|1A|K|L]]|9|@]|A|$]]|$1|O|3|P|5|F|7|1B|8|@$I|1C|J|1D|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1E|8|@$I|1F|J|1G|K|L]]|9|@]|A|$]]|$1|S|3|T|5|F|7|1H|8|@$I|1I|J|1J|K|L]|$I|1K|J|1L|K|L]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1M|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|X|$]]

I do not want to mess with public access to X server and Windows firewall. My solution is using ssh with X forwarding (works for VirtualBox as well). Additionally, WSL auto-forwards from host to guest listening sockets, so I don't care which IP is actually assigned to guest.
So the steps are these:
<ol>
<li>Install VcXSrv. Run it with all defaults but set Display number to 0 (-1 will choose 0 if no X instances are already running). Do not start any client in it (this gives a benefit that you can start more apps on the same X server instance).</li>
<li>Open WSL and configure ssh server. For me it's as simple as <code>sudo service ssh start</code>. Create a Windows shortcut with command line: <code>wsl sudo service ssh start</code>.</li>
<li>Install Git for Windows. I actually use it only because its version of ssh is capable of going into background with <code>ssh -f</code>. Windows version of ssh is buggy on this feature, otherwise it's suitable without going to background or with <code>ssh -n</code>.</li>
<li>Configure passwordless login from Git-Bash to the guest. <code>ssh user@127.0.0.1</code> should work at this point, because the host port is forwarded to the guest.</li>
<li>Verify X forwarding works from Git-Bash: <code>DISPLAY=127.0.0.1:0 ssh -Y user@127.0.0.1 xeyes</code>. I think xeyes is installed with each X distribution.</li>
<li>Install file manager or terminal of your choice in WSL. For example, pcmanfm. Create a Windows shortcut: <code>&quot;C:\Program Files\Git\git-bash.exe&quot; -c &quot;DISPLAY=127.0.0.1:0 ssh -Y -f user@127.0.0.1 'bash -l -c pcmanfm &gt;/dev/null 2&gt;&amp;1'&quot;</code>. Here <code>bash -l</code> flag helps setting up environment which may or may not be important depending on apps you run.</li>
</ol>
Of course, I can do the same without git-bash by using VcXSrv built-in ssh client but it requires converting ssh keys to PuTTY format and I had git-bash already installed. Also, with built-in client display reuse did not work for me.

blocks|key|1084744|text|正如其他人指出的那样，我在windows+10上提出了一个使用vxcsrv的解决方案。也可以在windows+11上工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084745|XServer+Windows+-+WSL1+&+WSL2：|1084746|安装|1084747|https://sourceforge.net/projects/vcxsrv/|offset|length|1084748|在WSL区设置前向显示|1084749|配置显示|style|BOLD|1084750|如果您运行WSL1|unordered-list-item|1084751|export+LIBGL_ALWAYS_INDIRECT=1
export+DISPLAY=localhost:0|code-block|syntax|javascript|1084752|如果您运行WSL2|1084753|export+LIBGL_ALWAYS_INDIRECT=1
export+DISPLAY=$(awk+'/nameserver+/+{print+$2;+exit}'+/etc/resolv.conf+2>/dev/null):0|1084754|(如果禁用了resolv.conf，请使用以下定义：https://stackoverflow.com/a/63092879/11473934)|CODE|1084755|然后(安装x11应用程序)|1084756|sudo+apt+update
sudo+apt+install+x11-apps|1084757|在Windows上启动XLaunch|1084758|多窗口|1084759|不启动客户端|1084760|禁用本机opengl|1084761|启用禁用访问控制|1084762|试试看|1084763|在wsl中:输入xcalc+-计算器应该在Windows10中打开|1084764|如果一切顺利|1084765|并且您希望在您的wsl发行版中保持设置。将它们存储在您的~/.bashrc中。|1084766|sudo+nano+~/.bashrc|1084767|复制这两行(从WSL区域配置显示中的Set显示)，两行结束并保存它。|1084768|添加到自动启动|1084769|运行对话框参见Windows上的Start+XLaunch|ordered-list-item|1084770|保存配置|1084771|按Windows+%2BR|1084772|输入:shell:启动|1084773|复制保存的配置：*.launch+(在步骤2中生成)到此文件夹(步骤4)|1084774|现在，XServer将在windows启动时启动。|1084775|我把它用在罗斯身上了。为我工作。|1084776|我的XServer在互联网上是不可用的，所以可以禁用访问控制。|1084777|entityMap|0|LINK|mutability|MUTABLE|url|1|https://stackoverflow.com/a/63092879/11473934^0|0|0|0|0|14|0|0|0|0|4|0|5|4|0|0|5|4|0|0|6|B|Q|19|1|0|0|D|0|0|0|0|0|0|0|0|0|0|S|9|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2O|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|2P|8|@]|9|@$H|2Q|I|2R|1|2S]]|A|$]]|$1|J|3|K|5|6|7|2T|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|2U|8|@$H|2V|I|2W|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|2X|8|@$H|2Y|I|2Z|N|O]]|9|@]|A|$]]|$1|S|3|T|5|U|7|30|8|@]|9|@]|A|$V|W]]|$1|X|3|Y|5|R|7|31|8|@$H|32|I|33|N|O]]|9|@]|A|$]]|$1|Z|3|10|5|U|7|34|8|@]|9|@]|A|$V|W]]|$1|11|3|12|5|R|7|35|8|@$H|36|I|37|N|13]]|9|@$H|38|I|39|1|3A]]|A|$]]|$1|14|3|15|5|6|7|3B|8|@$H|3C|I|3D|N|O]]|9|@]|A|$]]|$1|16|3|17|5|U|7|3E|8|@]|9|@]|A|$V|W]]|$1|18|3|19|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|R|7|3G|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|R|7|3H|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|R|7|3I|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|R|7|3J|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3K|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3N|8|@$H|3O|I|3P|N|13]]|9|@]|A|$]]|$1|1Q|3|1R|5|U|7|3Q|8|@]|9|@]|A|$V|W]]|$1|1S|3|1T|5|6|7|3R|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1W|3|1X|5|1Y|7|3T|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|1Y|7|3U|8|@]|9|@]|A|$]]|$1|21|3|22|5|1Y|7|3V|8|@]|9|@]|A|$]]|$1|23|3|24|5|1Y|7|3W|8|@]|9|@]|A|$]]|$1|25|3|26|5|1Y|7|3X|8|@]|9|@]|A|$]]|$1|27|3|28|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|29|3|2A|5|6|7|3Z|8|@]|9|@]|A|$]]|$1|2B|3|2C|5|6|7|40|8|@]|9|@]|A|$]]|$1|2D|3|-4|5|6|7|41|8|@]|9|@]|A|$]]]|2E|$2F|$5|2G|2H|2I|A|$2J|G]]|2K|$5|2G|2H|2I|A|$2J|2L]]]]

I come up with a solution using vxcsrv on windows 10, as others pointed out. Also working on windows 11.
<h2>XServer Windows - WSL1 &amp; WSL2:</h2>
<h3>Install X-Server Windows</h3>
<a href="https://sourceforge.net/projects/vcxsrv/" rel="noreferrer">https://sourceforge.net/projects/vcxsrv/</a>
<h3>Set Display forward in WSL Distro</h3>
Configure Display:
<ul>
<li>If you running WSL1:</li>
</ul>
<pre class="lang-bash prettyprint-override"><code>export LIBGL_ALWAYS_INDIRECT=1
export DISPLAY=localhost:0
</code></pre>
<ul>
<li>If you running WSL2:</li>
</ul>
<pre class="lang-bash prettyprint-override"><code>export LIBGL_ALWAYS_INDIRECT=1
export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2&gt;/dev/null):0
</code></pre>
<ul>
<li>(If you have disabled <code>resolv.conf</code> use this definition: <a href="https://stackoverflow.com/a/63092879/11473934">https://stackoverflow.com/a/63092879/11473934</a>)</li>
</ul>
and then (install x11-apps):
<pre class="lang-bash prettyprint-override"><code>sudo apt update
sudo apt install x11-apps
</code></pre>
<h3>Start XLaunch on Windows</h3>
<ul>
<li>Multiple Windows</li>
<li>Start no client</li>
<li>disable Native opengl</li>
<li>enable Disable access control</li>
</ul>
<h3>Test it</h3>
In wsl: enter xcalc - Calculator should open in Windows10
<h3>If everything worked</h3>
And you want to persist the settings in your wsl distro. Store them in your <code>~/.bashrc</code>.
<pre class="lang-bash prettyprint-override"><code>sudo nano ~/.bashrc
</code></pre>
Copy the two lines (from Set Display forward in WSL Distro - Configure Display), two the end and save it.
<h3>Add it to autostart</h3>
<ol>
<li>Run Dialog see Start XLaunch on Windows</li>
<li>Save configuration</li>
<li>Press Windows + R</li>
<li>Enter: shell:startup</li>
<li>Copy saved configuration: *.launch (Generated in step 2) to this folder (step 4)</li>
</ol>
Now the XServer will be started with windows startup.
I’m using it for ROS. Works for me.
My XServer isn’t available over internet so its okay to disable access control.

blocks|key|872344|text|我的错误是，当我的xserver在windows上运行时，我使用了linux+wsl2实例的名称服务器。因此显示变量必须设置为我的windows+ipv4地址。只在powershell或cmd中键入ipconfig并使用ipv4+ethernet+address。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|872345|entityMap^0|1G|S|2R|8|32|L|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|D]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|P|8|@]|E|@]|F|$]]]|H|$]]

My mistake was that I took the nameserver of my linux wsl2 instance while my xserver runs on windows. So the DISPLAY variable had to be set to my windows ipv4 address.
Just type <code>ipconfig</code> in powershell or cmd and use the <code>ipv4 ethernet address</code>.

blocks|key|241107|text|我也经历了困难的开放X11图形界面从WSL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|241108|我在检测正确的IP时遇到了问题，有时X11服务器会采取奇怪的偏移，有时出现在0-17上是随机的。|241109|我编写了以下脚本来自动处理此问题，但它几乎没有依赖项：|241110|这是在CentOS7映像下测试和运行的。|unordered-list-item|241111|在linux发行版上安装X11应用程序，使其具有“`xset”|241112|安装“超时”应用程序|241113|通过source+./find_display_ip.sh执行脚本。注意源！您将希望在运行的shell中具有显示环境变量。|offset|length|style|CODE|BOLD|241114|只通过"Windows终端“或在WSL+shell中增加窗口”路径“的内容运行脚本。例如，在windows提示符`+`cmd中，这对我来说不是默认的。|241115|显然，确保您的X11服务器完全访问("xhost+%2B“或"X11远程访问”已满)|241116|没有进一步的到期，这是脚本源代码：|241117|#!/bin/bash

start_index=$1
start=${start_index:-0}
#+check+current+settings
declare+-i+stop=0
if+[+!+-z+"$DISPLAY"+];+then
++++timeout+1s+xset+-display+$DISPLAY+q+&>+/dev/null;
++++[[+"$?"+-eq+0+]]+&&+echo+"Already+Set+to+$DISPLAY"+&&+stop=1;
fi

#+scan+displays+0-17
for+port+in+$(seq+$start+17);
do
++++[[+1+-eq+$stop+]]+&&+break;
++++grp="ipconfig.exe+%7C+grep+IPv4+%7C+tr+-d+'\015'+%7C+sed+'s#.*:+$.*$\$#\1:${port}.0#;'"
++++for+ipd+in+$(eval+$grp)
++++do
++++++++echo+Trying+$ipd;
++++++++timeout+1s+xset+-display+$ipd+q+&>+/dev/null;

++++++++#+command+was+sucessful
++++++++[[+"$?"+-eq+0+]]+&&+export+DISPLAY=$ipd+&&+echo+$ipd+was+set+&&+stop=1;

++++++++##echo+"Trying+next+IP...";
++++done
done|code-block|syntax|javascript|241118|entityMap^0|0|0|0|0|0|0|2|R|10|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|1C|8|@$O|1D|P|1E|Q|R]|$O|1F|P|1G|Q|S]]|9|@]|A|$]]|$1|T|3|U|5|H|7|1H|8|@]|9|@]|A|$]]|$1|V|3|W|5|H|7|1I|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Z|3|10|5|11|7|1K|8|@]|9|@]|A|$12|13]]|$1|14|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|15|$]]

I also experienced hardships in opening X11 GUIs from WSL.
I had a problem detecting the correct IP and sometimes the X11 server took weird offsets which sometimes appeared as random on 0-17.
I coded the following script to automate this issue, but it has few dependencies:
<ul>
<li>This was tested and run under CentOS7 image</li>
<li>install X11-apps on your linux distribution to have `xset</li>
<li>install &quot;timeout&quot; app</li>
<li>Execute script by <code>source ./find_display_ip.sh</code>. note the source! You will want to have DISPLAY environment variable on your running shell.</li>
<li>Run the script only through &quot;Windows Terminal&quot; or something that incoprates windows &quot;PATH&quot; inside the WSL shell. This didn't use to be default for me in windows prompt `cmd, for example.</li>
<li>Obviously make sure your X11 server has full access (&quot;xhost +&quot; or &quot;X11 remote access&quot; is full)</li>
</ul>
Without further a due, this is the script source code:
<pre><code>#!/bin/bash

start_index=$1
start=${start_index:-0}
# check current settings
declare -i stop=0
if [ ! -z &quot;$DISPLAY&quot; ]; then
 timeout 1s xset -display $DISPLAY q &amp;&gt; /dev/null;
 [[ &quot;$?&quot; -eq 0 ]] &amp;&amp; echo &quot;Already Set to $DISPLAY&quot; &amp;&amp; stop=1;
fi

# scan displays 0-17
for port in $(seq $start 17);
do
 [[ 1 -eq $stop ]] &amp;&amp; break;
 grp=&quot;ipconfig.exe | grep IPv4 | tr -d '\015' | sed 's#.*: $.*$\$#\1:${port}.0#;'&quot;
 for ipd in $(eval $grp)
 do
 echo Trying $ipd;
 timeout 1s xset -display $ipd q &amp;&gt; /dev/null;

 # command was sucessful
 [[ &quot;$?&quot; -eq 0 ]] &amp;&amp; export DISPLAY=$ipd &amp;&amp; echo $ipd was set &amp;&amp; stop=1;

 ##echo &quot;Trying next IP...&quot;;
 done
done
</code></pre>

blocks|key|241215|text|截至2021-04-27，Windows+11和Windows+10的内部构建包括WSLg.它只适用于™。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|241216|注意:目前，所有支持WSLg的Windows版本都是内幕版本，通常不推荐用于日常使用。然而，"WSLg将与即将发布的Windows一起普遍可用“。|241217|来自https://github.com/microsoft/wslg+(原公告)。|241218|Prerequisites:|blockquote|241219|确保使用Windows+10内部构建21362%2B|ordered-list-item|241220|推荐:为vGPU安装驱动程序：英特尔+AMD+Nvidia|241221|“系统信息”应用程序会告诉你你当前的版本号。|241222|WSL1与WSLg不兼容。新的WSL2实例将只运行™。|241223|现有的WSL2系统需要“更新”：|241224|241225|在管理PowerShell中：wsl+--update|CODE|241226|wsl+--shutdown强制重新启动WSL|241227|不要忘记删除您可能对DISPLAY所做的任何其他修改。|241228|证明它有效：|241229|📷|atomic|241230|​|241231|虽然官方公告中说，某些构建了Windows+10+support+WSLg__，并且它是在Windows+10__上演示的，但目前似乎没有任何公开可用的内幕E+251构建的<代码>E+152Windows+10<代码>E+253E+253支持E+154WSLg<代码>E+255__。|241232|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/wslg|1|https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps|2|https://downloadcenter.intel.com/download/29526|3|https://www.amd.com/en/support/kb/release-notes/rn-rad-win-wsl-support|4|https://developer.nvidia.com/cuda/wsl|5|https://github.com/microsoft/wslg#install-instructions-existing-wsl-install|6|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/7291a1596fec5c982c7da4a03118822c.png|imageAlt^0|D|A|O|A|15|4|0|A|4|Q|2|0|2|X|0|11|3|1|0|0|E|0|4|K|0|F|3|2|J|3|3|N|6|4|0|0|0|C|5|0|0|0|F|C|0|0|E|0|A|7|0|0|6|0|0|1|6|0|0|E|A|X|4|19|A|24|1U|26|5|3D|I|0^^$0|@$1|2|3|4|5|6|7|22|8|@$9|23|A|24|B|C]|$9|25|A|26|B|C]|$9|27|A|28|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|29|8|@$9|2A|A|2B|B|C]|$9|2C|A|2D|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|2E|8|@]|D|@$9|2F|A|2G|1|2H]|$9|2I|A|2J|1|2K]]|E|$]]|$1|J|3|K|5|L|7|2L|8|@$9|2M|A|2N|B|C]]|D|@]|E|$]]|$1|M|3|N|5|O|7|2O|8|@$9|2P|A|2Q|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|O|7|2R|8|@]|D|@$9|2S|A|2T|1|2U]|$9|2V|A|2W|1|2X]|$9|2Y|A|2Z|1|30]]|E|$]]|$1|R|3|S|5|6|7|31|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|32|8|@]|D|@$9|33|A|34|1|35]]|E|$]]|$1|V|3|W|5|6|7|36|8|@]|D|@]|E|$]]|$1|X|3|-4|5|L|7|37|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|O|7|38|8|@$9|39|A|3A|B|10]]|D|@]|E|$]]|$1|11|3|12|5|O|7|3B|8|@$9|3C|A|3D|B|10]]|D|@]|E|$]]|$1|13|3|14|5|6|7|3E|8|@$9|3F|A|3G|B|10]]|D|@]|E|$]]|$1|15|3|16|5|6|7|3H|8|@$9|3I|A|3J|B|C]]|D|@]|E|$]]|$1|17|3|18|5|19|7|3K|8|@]|D|@$9|3L|A|3M|1|3N]]|E|$]]|$1|1A|3|1B|5|6|7|3O|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|3P|8|@$9|3Q|A|3R|B|C]|$9|3S|A|3T|B|C]|$9|3U|A|3V|B|C]|$9|3W|A|3X|B|C]|$9|3Y|A|3Z|B|10]|$9|40|A|41|B|10]]|D|@]|E|$]]|$1|1E|3|-4|5|6|7|42|8|@]|D|@]|E|$]]]|1F|$1G|$5|1H|1I|1J|E|$1K|1L]]|1M|$5|1H|1I|1J|E|$1K|1N]]|1O|$5|1H|1I|1J|E|$1K|1P]]|1Q|$5|1H|1I|1J|E|$1K|1R]]|1S|$5|1H|1I|1J|E|$1K|1T]]|1U|$5|1H|1I|1J|E|$1K|1V]]|1W|$5|1X|1I|1Y|E|$1Z|20|21|-4]]]]

Windows 11, and Insider builds of Windows 10, as of 2021-04-27, include WSLg. It just works™.
Note: Currently, all versions of Windows that support WSLg are Insider builds which are not typically recommended for daily use. However, &quot;WSLg is going to be generally available alongside the upcoming release of Windows&quot;.
From <a href="https://github.com/microsoft/wslg" rel="nofollow noreferrer">https://github.com/microsoft/wslg</a> (<a href="https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps" rel="nofollow noreferrer">original announcement</a>).
<blockquote>
Prerequisites:
<ol>
<li>Ensure using Windows 10 Insider build 21362+</li>
<li>Recommended: Install driver for vGPU: <a href="https://downloadcenter.intel.com/download/29526" rel="nofollow noreferrer">Intel</a> <a href="https://www.amd.com/en/support/kb/release-notes/rn-rad-win-wsl-support" rel="nofollow noreferrer">AMD</a> <a href="https://developer.nvidia.com/cuda/wsl" rel="nofollow noreferrer">Nvidia</a></li>
</ol>
</blockquote>
The &quot;System Information&quot; App will tell you your current build number.
<a href="https://github.com/microsoft/wslg#install-instructions-existing-wsl-install" rel="nofollow noreferrer">WSL1 is not compatible with WSLg</a>. New WSL2 instances will just work™.
Existing WSL2 systems will need to be &quot;updated&quot;:
<blockquote>
<ol>
<li>In administrative PowerShell: <code>wsl --update</code></li>
<li><code>wsl --shutdown</code> to force a restart of the WSL</li>
</ol>
</blockquote>
Don't forget to remove any other modifications to <code>DISPLAY</code> that you may have made.
Proof that it works:
<a href="https://i.stack.imgur.com/WrQEf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/WrQEf.png" alt="Proof that it works" /></a>
While the official announcements say that certain Insider builds of Windows 10 support WSLg, and it was demoed on Windows 10, there currently don't seem to be any publicly available Insider builds of Windows 10 that do support WSLg.

blocks|key|872535|text|2021+Windows+10的答案|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|872536|如果从resolv.conf获取IP不起作用，请检查这个答案。|872537|在WSL2中使用以下命令查找Windows地址(是，linux中的.exe文件)：|872538|ipconfig.exe+|code-block|syntax|javascript|872539|使用下面的命令设置显示(用IP填充YOUR_IP_ADDRESS+)：|872540|export+DISPLAY=YOUR_IP_ADDRESS:0|872541|检查您的GUI应用程序是否正确工作。|872542|对于每一种情况，自动化可能没有什么不同，但我将举个例子：|872543|ipconfig.exe+%7C+grep+'IPv4+Address'+%7C+grep+'10\.'+%7C+cut+-d+":"+-f+2+%7C+cut+-d+"+"+-f+2+|872544|说明:我找到了所有的IPv4地址(在我的例子中有3个IP)。我知道我的IP只从‘10’开始所以我使用第二个grep选择了这一行。接下来，我处理了整条线路，只获取IP。|872545|entityMap^0|0|F|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|17|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|18|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|19|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|1A|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1B|8|@]|D|@]|E|$]]|$1|W|3|X|5|L|7|1C|8|@]|D|@]|E|$M|N]]|$1|Y|3|Z|5|6|7|1D|8|@]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|11|$]]

2021 answer for Windows 10
Check this answer if getting IP from resolv.conf doesn't work.
Find your Windows IP address using following command in your WSL2 (yes, .exe file inside linux):
<pre><code>ipconfig.exe 
</code></pre>
Use command below to set display (fill YOUR_IP_ADDRESS with your IP):
<pre><code>export DISPLAY=YOUR_IP_ADDRESS:0
</code></pre>
Check if your GUI app works correctly.
Automation can be little different for each case but I'll give example:
<pre><code>ipconfig.exe | grep 'IPv4 Address' | grep '10\.' | cut -d &quot;:&quot; -f 2 | cut -d &quot; &quot; -f 2 
</code></pre>
Explanation: I found all IPv4 addresses (3 IPs in my case). I know that my IP starts only from '10.' so I chose this line using second grep. Next I processed whole line to get the IP only.

When moving from WSL1 to WSL2 many things change; apparently this applies to X11 forwarding as well. 
What steps do I need to make in order to use X11 forwarding with WSL2 on Windows 10 as I did with WSL1?

How to set up working X11 forwarding on WSL2

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

当从WSL1迁移到WSL2时，很多事情都会发生变化；显然，这也适用于X11转发。我需要采取哪些步骤才能像对X11一样在WSL2 10上使用WSL2转发？

问如何在X11上设置工作WSL2转发
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在X11上设置工作WSL2转发EN