search

wiresock / proxifyre

ProxiFyre: SOCKS5 Proxifier for Windows
https://www.ntkernel.com
GNU Affero General Public License v3.0
216 stars 18 forks source link

Not working - config and log provided #18

Closed emily785 closed 6 months ago

emily785 commented 1 year ago

I am simply testing with Tor and msedge (tor socks is running and listening on 127.0.0.1:9050)

I also tried with a remote socks5 and it never actually connects to it.

Could it be finding the wrong network interface? Is there any conflict if I'm using wiresock vpn client at the same time? (note that my Wiresock config only has 10.20.1.0/24 in AllowedIPs)


 "logLevel": "All",
 "proxies": [
         {
         "appNames": ["msedge"],
         "socks5ProxyEndpoint": "127.0.0.1:9050",      
         "supportedProtocols": ["TCP"]
         }
     ]
}

`2023-09-15 13:41:17.6108|INFO|ProxiFyre.ProxiFyreService|Successfully associated msedge to 127.0.0.1:9050 SOCKS5 proxy with protocols TCP!
2023-09-15 13:41:17.6637|INFO|ProxiFyre.ProxiFyreService|ProxiFyre Service is running...
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::Creating SOCKS5 Local Router instance...::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::SOCKS5 Local Router instance successfully created.::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::Local TCP proxy for 127.0.0.1:9050 is listening port: 50824::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::socks5_local_router:: Detected default interface {675D97D3-0744-40EF-AD34-BB3227972487}::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::SOCKS5 Local Router instance started successfully.::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::Redirecting TCP: 192.168.1.195 : 50827 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::NEW TCP: 192.168.1.195 : 50827 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::Redirecting TCP: 192.168.1.195 : 50829 -> 52.123.245.98 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::NEW TCP: 192.168.1.195 : 50829 -> 52.123.245.98 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::Redirecting TCP: 192.168.1.195 : 50830 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::NEW TCP: 192.168.1.195 : 50830 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50831 -> 52.123.245.98 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::NEW TCP: 192.168.1.195 : 50831 -> 52.123.245.98 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50827 -> 40.71.99.188 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50829 -> 52.123.245.98 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50830 -> 40.71.99.188 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:26::Message::Redirecting TCP: 192.168.1.195 : 50831 -> 52.123.245.98 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:26::Message::Redirecting TCP: 192.168.1.195 : 50834 -> 142.250.74.132 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:26::Message::NEW TCP: 192.168.1.195 : 50834 -> 142.250.74.132 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50844 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50844 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50845 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50845 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50846 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50846 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50850 -> 96.16.49.223 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50850 -> 96.16.49.223 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50851 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50851 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50852 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50852 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50853 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50853 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50854 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50854 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50855 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50855 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50834 -> 142.250.74.132 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50845 -> 142.250.74.131 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50846 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50844 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50850 -> 96.16.49.223 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50853 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50852 -> 142.250.74.131 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50851 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50854 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50855 -> 204.79.197.239 : 443::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::Redirecting TCP: 192.168.1.195 : 50857 -> 51.195.60.196 : 80::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::NEW TCP: 192.168.1.195 : 50857 -> 51.195.60.196 : 80::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::Redirecting TCP: 192.168.1.195 : 50858 -> 51.195.60.196 : 80::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::NEW TCP: 192.168.1.195 : 50858 -> 51.195.60.196 : 80::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::Redirecting TCP: 192.168.1.195 : 50859 -> 51.195.60.196 : 80::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::NEW TCP: 192.168.1.195 : 50859 -> 51.195.60.196 : 80::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50864 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50864 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50865 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50865 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50868 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50868 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50869 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50869 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50870 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50870 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50871 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50871 -> 204.79.197.239 : 443::0```
emily785 commented 1 year ago

Tried in a VM now where I also run wiresock vpn client.

It works fine in VM. So there's no conflict with wiresock vpn client at least.

But I still can't get it working on my machine!

emily785 commented 1 year ago 
Caption                                              GUID
[00000000] Microsoft Kernel Debug Network Adapter
[00000001] Intel(R) I211 Gigabit Network Connection  {49193F35-C824-49AD-B13F-8B82CD420C92}
[00000002] WAN Miniport (SSTP)
[00000003] WAN Miniport (IKEv2)
[00000004] WAN Miniport (L2TP)
[00000005] WAN Miniport (PPTP)
[00000006] WAN Miniport (PPPOE)
[00000007] WAN Miniport (IP)
[00000008] WAN Miniport (IPv6)
[00000009] WAN Miniport (Network Monitor)
[00000010] Hyper-V Virtual Switch Extension Adapter
[00000011] Hyper-V Virtual Ethernet Adapter          {772A9012-459A-4E1C-9444-F7C13A2D7D88}
[00000012] Hyper-V Virtual Ethernet Adapter          {675D97D3-0744-40EF-AD34-BB3227972487}
[00000013] Hyper-V Virtual Ethernet Adapter          {9AA67482-6380-4F45-9BA3-18F03E9D4661}
[00000014] WireSock Virtual Adapter                  {0C3525F0-CDFB-4001-ACAE-887A222D6E08}
[00000017] Hyper-V Virtual Switch Extension Adapter

Proxifyre seems to be selecting

[00000012] Hyper-V Virtual Ethernet Adapter          {675D97D3-0744-40EF-AD34-BB3227972487}
wiresock commented 1 year ago

Hmm, to better diagnose the issue, could you please furnish us with more comprehensive information about your network configuration? ProxiFyre's goal is to pinpoint the default Internet interface for filtering purposes, and additional details will aid in troubleshooting.