Replies: 1 comment
-
v0.9.0 now supports multiple |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm confused by the host only directive in the context of running on Windows 10 22 H2. When set to hostonly=1 it listens on 0.0.0.0 and hence accept a TCP connection on the port from a remote system. That said, it does not accept a HTTP connect so I assume this directive adds the local interface address to the allow list. Now the .ini file help states:
Now I have tired this with both Hyper-V VMs behind the default Hyper-V switch and WSL but neither work. The reason seems to be that in the
hostonly=1
configuration PX proxy allow list is the virtual interface IP address for the Hyper-V and WSL instances but the VM/WSL traffic does not come to PX proxy via this address it comes via the WSL or VM instance IP address. My only solution has been to create individual instances of PX proxy listening on the individual IP address of these virtual adapters.Beta Was this translation helpful? Give feedback.
All reactions