wsl not working... #1091
Comments
|
Don't know about WSL not starting but I never got my WSL to work consistently with portmaster regardless of the version or settings, I resorted to editing /etc/resolv.conf and having it ask an external DNS server. You can find out what your "host" ip is in WSL (run Also, you need to make /etc/resolv.conf not editable or disable WSL's rewriting of resolv.conf on guest bootup to maintain your manual settings. See here. Just keep in mind that WSL runs its own networking stack and service and it's embedded into windows via This is what I use on the windows side in powershell when WSL fails to forward ports normally: Syntax: # If elevation needed, start new process
If (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator))
{
# Relaunch as an elevated process:
Start-Process powershell.exe "-File",('"{0}"' -f $MyInvocation.MyCommand.Path),"$Args runas" -Verb RunAs
exit
}
$numOfArgs = $args.Length
if ($numOfArgs -eq 0) {
Write-Host "Not enough ports to go by :)"
exit
}
$Ports=@()
for ($i=0; $i -le $numOfArgs; $i++)
{
$Ports+=@($($args[$i]))
}
# Check WSL ip address
wsl hostname -I | Set-Variable -Name "PRE"
$WSL = Write-Output $PRE.split(" ") | Select-Object -first 1
$found = $WSL -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}';
if (-not $found) {
Write-Output "WSL2 cannot be found. Terminate script.";
exit;
}
# Add each port into portproxy
$Addr = "0.0.0.0"
Foreach ($Port in $Ports) {
if ($Port) {
$doIHaveDoublePorts = $Port -match '^[^:]+:[^:]+$'
if( $doIHaveDoublePorts ) {
$hostPort = @($Port -split ':')[0]
$wslPort = @($Port -split ':')[1]
Invoke-Expression "netsh interface portproxy delete v4tov4 listenaddress=$Addr listenport=$hostPort | Out-Null";
if ($Args[0] -ne "delete") {
Invoke-Expression "netsh interface portproxy add v4tov4 listenaddress=$Addr listenport=$hostPort connectaddress=$WSL connectport=$wslPort";
Write-Output "$hostPort forwarded for $wslPort in WSL."
}
} else {
Invoke-Expression "netsh interface portproxy delete v4tov4 listenaddress=$Addr listenport=$Port | Out-Null";
if ($Args[0] -ne "delete") {
Invoke-Expression "netsh interface portproxy add v4tov4 listenaddress=$Addr listenport=$Port connectaddress=$WSL connectport=$Port";
Write-Output "$Port forwarded - symmetrical."
}
}
}
} |
|
@working-name the method doing the works but it's a too much of a work cuz for every i.e for every different netsh work I've to port again and again like firt i did for opening the wsl after that i tried cloning git repo's it results in Another thing is portmaster doesn't show Terminal Preview app in it all other active apps are shown even cmd is shown if I open it but idk Terminal Preview doesn't shows, thats another problem if it can be shown then i should have allowed the app in monitor section and it can work :) |
|
@working-name Just tried disabling the global incoming connection, its working fine now :) |
|
Yeah, portmaster used to be much more user friendly in the past - there was a way to monitor all connections and it would update live, and the connection prompt had its own dedicated sidebar which allowed you to keep an eye on what's going on without having to activate Portmaster, and then click yet another button to just get a tiny window that you have to scroll through to find what you want. It also auto-collapses the current details on refresh.... a bunch of oddities. But yeah I disable that global incoming block as well. I'm already behind a NAT, doubt this makes it any more or less secure. |
|
Auto-closing this issue after waiting for input for a month. If anyone finds the time to provide the requested information, please re-open the issue and we will continue handling it. |
|
This issue seems to have been mislabeled. Reopening. |
|
Duplicate of #502, already found a solution in that issue. |
Pre-Submit Checklist:
What happened:
I've installed debian as wsl interface, After I start portmaster wsl distro's doesn't start, Sometimes if it starts then process related to network doesn't work
What did you expect to happen?:
It should allows wsl, outbound connections to be bypassed
How did you reproduce it?:
I checked apps bar in portmaster there's also issue with it's application detection as per above image i'm using Terminal Preview but inside portmaster it doesn't shows
Debug Information:
Portmaster
version 1.0.6
commit tags/v1.0.6-0-g0ee078d911665739696ed89e2582768e0ba6b864
built with go1.19 (gc) windows/amd64
using options main.go
by user@docker
on 30.01.2023
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
System: Microsoft Windows 10 Home Single Language windows (Standalone Workstation) 10.0.19045 Build 19045
Kernel: 10.0.19045 Build 19045 x86_64
ActiveSecurityLevel: Trusted
SelectedSecurityLevel: Off
ThreatMitigationLevel: Trusted
CaptivePortal:
OnlineStatus: Online
core/expertiseLevel: developer
dns/nameservers: [redacted]
Cloudflare (dot://cloudflare-dns.com:853#config)
dot://cloudflare-dns.com:853#config
Failing: false
Cloudflare (dot://cloudflare-dns.com:853#config)
dot://cloudflare-dns.com:853#config
Failing: false
192.168.43.251 (dns://192.168.43.251:53#system)
dns://192.168.43.251:53#system
Failing: false
HomeHubID:
HomeHubName:
HomeHubIP:
Transport:
Client: true
PublicHub: false
HubHasIPv4: false
HubHasIPv6: false
Edge traversal Teredo Authorization Sublayer SubLayer Edge traversal Teredo Authorization Sublayer {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
IPxlat Forward IPv4 filter Callout Filters forwarded IPv4 packets into synthetic IPv6 packets {b255c296-7e0c-4115-95f3-b7f24a8a1162} [no provider key] FWPM_LAYER_IPFORWARD_V4
IPxlat Forward IPv4 sub layer SubLayer Sub layer for filtering forwarded IPv4 packets into synthetic IPv6 packets {4351e497-5d8b-46bc-86d9-abccdb868d6d}
IPxlat Inbound IPv6 filter Callout Filters incoming IPv6 packets into synthetic IPv4 packets {93bb703d-0502-42e2-8e30-a14576e5085d} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6
IPxlat Inbound IPv6 sub layer SubLayer Sub layer for filtering incoming IPv6 packets into synthetic IPv4 packets {dfb035ca-c2a7-4684-97b6-4dbc57c63590}
IPxlat Outbound IPv4 filter Callout Filters outgoing IPv4 packets into synthetic IPv6 packets {66d52657-1979-4e58-b3f7-4756434c4880} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4
IPxlat Outbound IPv4 sub layer SubLayer Sub layer for filtering outgoing IPv4 packets into synthetic IPv6 packets {d3e70856-fc90-4c0a-b9b2-a6f73e20b5cc}
PortmasterInboundV4Callout Callout This callout is used by the Portmaster to intercept inbound IPv4 traffic. {05c55149-4732-4857-8d10-f178f3a06f8c} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4
PortmasterInboundV4Filter Filter This filter is used by the Portmaster to intercept inbound IPv4 traffic. {7954cc61-9b78-4d77-a402-3675c81adcfe} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterInboundV6Callout Callout This callout is used by the Portmaster to intercept inbound IPv6 traffic. {ceff1df7-2baa-44c5-a6e5-73a95849bcff} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6
PortmasterInboundV6Filter Filter This filter is used by the Portmaster to intercept inbound IPv6 traffic. {2ca99a9a-824c-4472-bee3-e4cff5a21279} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV4Callout Callout This callout is used by the Portmaster to intercept outbound IPv4 traffic. {41162b9e-8473-4b88-a5eb-04cf1d276b06} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4
PortmasterOutboundV4Filter Filter This filter is used by the Portmaster to intercept outbound IPv4 traffic. {6cb02efd-a1ac-4c0c-8759-2074bc1b9e27} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV6Callout Callout This callout is used by the Portmaster to intercept outbound IPv6 traffic. {32bad112-6af4-4109-809b-c07570ba01b4} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6
PortmasterOutboundV6Filter Filter This filter is used by the Portmaster to intercept outbound IPv6 traffic. {0e40fcc6-0ecb-4362-8318-a6ccde9370ef} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterSublayer SubLayer The Portmaster sublayer holds all it's filters. {a87fb472-fc68-4805-8559-c6ae774773e0}
Teredo socket option opt out block filter Filter [no description] {771f05e2-9802-4f69-b2ac-0a6e7f5b72bb} {efe67ac7-cbe5-4019-ad82-1f0a9204b866} FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
VPN Reconnect Sublayer SubLayer [no description] {9367171b-3264-4f09-a0e8-81b38c162f17}
230209 15:59:31.107 entication:291 > WARN 002 api: denying api access from 12x.xx
230209 15:59:33.499 v/location:299 > WARN 004 netenv: failed to get IPv4 device location from traceroute: did not receive any actionable ICMP reply
230209 15:59:59.178 pat/module:108 > ERRO 006 compat: self-check #2: dns integration check failed: did not receive test query after 20s
230209 16:00:24.195 pat/module:108 > ERRO 008 compat: self-check #2: dns integration check failed: did not receive test query after 20s
230209 16:00:37.881 olver-mdns:114 > WARN 010 intel(mdns): failed to create udp6 listen multicast socket: listen udp6 [fx]: setsockopt: not supported by windows
230209 16:00:49.200 pat/module:108 > ERRO 012 compat: self-check #2: dns integration check failed: did not receive test query after 20s
230209 18:51:27.394 CURRENT TIME
Active:
all/intel/geoip/geoipv4.mmdb.gz: 20230102.9.32
all/intel/geoip/geoipv6.mmdb.gz: 20230102.13.14
all/intel/lists/base.dsdl: 20221231.23.0
all/intel/lists/index.dsd: 2022.6.7
all/intel/lists/intermediate.dsdl: 20221231.23.0
all/intel/lists/urgent.dsdl: 20230127.10.0
all/intel/portmaster/notifications.yaml: 20221101.12.34
all/ui/modules/assets.zip: 0.3.1
all/ui/modules/portmaster.zip: 0.4.5
windows_amd64/core/portmaster-core.exe: 1.0.6
windows_amd64/kext/portmaster-kext.sys: 1.0.17
windows_amd64/start/portmaster-start.exe: 1.0.2
Selected:
all/intel/geoip/geoipv4.mmdb.gz: 20230102.9.32
all/intel/geoip/geoipv4.mmdb: 20230102.9.32
all/intel/geoip/geoipv6.mmdb.gz: 20230102.13.14
all/intel/geoip/geoipv6.mmdb: 20230102.13.14
all/intel/lists/base.dsdl: 20221231.23.0
all/intel/lists/index.dsd: 2022.6.7
all/intel/lists/intermediate.dsdl: 20221231.23.0
all/intel/lists/urgent.dsdl: 20230127.10.0
all/intel/portmaster/notifications.json: 20211214.14.13
all/intel/portmaster/notifications.yaml: 20221101.12.34
all/intel/spn/main-intel.json: 20220113.8.47
all/intel/spn/main-intel.yaml: 20230207.13.47
all/ui/modules/assets.zip: 0.3.1
all/ui/modules/base.zip: 0.2.11
all/ui/modules/console.zip: 0.1.11
all/ui/modules/monitor.zip: 0.2.4
all/ui/modules/portmaster.zip: 0.4.5
all/ui/modules/profilemgr.zip: 0.1.7
all/ui/modules/settings.zip: 0.1.8
windows_amd64/app/portmaster-app.zip: 0.2.5
windows_amd64/core/portmaster-core.exe: 1.0.6
windows_amd64/hub/spn-hub.exe: 0.6.1
windows_amd64/jess/jess.exe: 0.3.1
windows_amd64/kext/portmaster-kext.dll: 1.0.14
windows_amd64/kext/portmaster-kext.pdb: 1.0.17
windows_amd64/kext/portmaster-kext.sys: 1.0.17
windows_amd64/notifier/portmaster-notifier.exe: 0.3.5
windows_amd64/notifier/portmaster-snoretoast.exe: 0.6.0
windows_amd64/notifier/portmaster-wintoast.dll: 0.1.4
windows_amd64/packages/portmaster-installer.exe: 1.0.0
windows_amd64/start/portmaster-start.exe: 1.0.2
The text was updated successfully, but these errors were encountered: