I don’t think RD is using vpnkit so WSL is managing the /20 that is allocated I believe. And WSL does that dynamically because it uses the hosts route table for some of the flows and it needs to be sure it doesn’t select an existing valid route. any reason you need to control the ip the node is using?

I have a real computer ip is : 10.1.1.11, RD installed on another computer, ip is: 10.1.1.12. how do I access a nginx pod from 10.1.1.11? Thank u

did you configure a service and ingress for your pod?

I configure a service, nginx can be accessed from RD computer 10.1.1.12[hostname:n2] use the node'Internal Ip:30030 . I can ping n2 from 10.1.1.11[hostname:n1]. However, http://n1:30030 cannot be accessed from [n1]

feels like you might be stretching what RD can do. Guessing it is a port forwarding issue as there are some limits there. you can dig through the github issues to see if there is a workaround that meets the need.

This is the static IP problem of windows WSL. I am studying it. Thank U