i get this error

  = note: LINK : fatal error LNK1181: cannot open input file 'Packet.lib'


error: could not compile `dispatch-proxy` due to previous error

Error

Error: 
   0: An error occurred during the proxy handshake procedure
   1: The proxy received `CONNECT mail.google.com:443 HTTP/1.1` (179 additional bytes not shown), which looks like an HTTP request. Please ensure that you have properly configured the proxy as a SOCKS proxy and not an HTTP proxy.

Metadata

|key|value| |--|--| |Version|0.1.0| |OS|Windows 10 Enterprise| |Command|dispatch -d start 192.168.18.7|

SpanTrace

SpanTrace:
   0: dispatch::socks::handle_version_error
           with self=SocksHandshake { reader: ReadHalf(PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:62620, socket: 1752 }) }), writer: WriteHalf(PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:62620, socket: 1752 }) }), dispatcher: WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: 192.168.18.7, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } }) } err=InvalidVersion(67)
             at C:\Users\Norbi\.cargo\registry\src\github.com-1ecc6299db9ec823\dispatch-proxy-0.1.0\src\socks.rs:93
   1: dispatch::server::handle_socket
           with socket=PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:62620, socket: 1752 }) } dispatcher=WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: 192.168.18.7, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } })
             at C:\Users\xxxx\.cargo\registry\src\github.com-1ecc6299db9ec823\dispatch-proxy-0.1.0\src\server.rs:19

Backtrace

Backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: BaseThreadInitThunk
  24: RtlUserThreadStart

Explain please Note: you need to install Npcap and copy the appropriate Packet.lib file from the SDK (x86 or x64) to C:\Users\Username.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\x86_64-pc-windows-msvc\lib in order to build on Windows.

my errror linking with link.exe failed: exit code: 1181

note: LINK : fatal error LNK1181: cannot open input file 'Packet.lib'

error: could not compile dispatch-proxy due to previous error error: failed to compile dispatch-proxy v0.1.0, intermediate artifacts can be found at C:\Users\SPELLM~1\AppData\Local\Temp\cargo-installsvnr8I

Thanks so much for your powerful tool! Currently I can only start dispatch with IP address. Is there any plan to support interface name?

For example, I want to start dispatch with dispatch start en0 en1. This is because the local IP address used in our company keeps changing every time I connect. Since I have no permission to set the static IP address, I have to check the current IP address before starting dispatch. I know I can obtain the address manually or with extra script but it would be much better (also more natural) to integrate this feature into your program.

I get this error trying to install it... any ideas?

nd..DataLinkReceiverImpl$u20$as$u20$pnet_datalink..DataLinkReceiver$GT$4next17h3a83025691b25060E
          libpnet_datalink-0a34f7a21e78bc2e.rlib(pnet_datalink-0a34f7a21e78bc2e.pnet_datalink.89658d71-cgu.7.rcgu.o) : error LNK2019: unresolved external symbol __imp_PacketGetAdapterNames referenced in function _ZN13pnet_datalink7backend10interfaces17h6779642a4cf78618E
          C:\Users\eendi\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\x86_64-pc-windows-msvc\lib\Packet.lib : warning LNK4272: library machine type 'x86' conflicts with target machine type 'x64'
          C:\Users\eendi\AppData\Local\Temp\cargo-installpwR1se\release\deps\dispatch-536b16db55652398.exe : fatal error LNK1120: 4 unresolved externals

After changing the proxy settings, whether it's enabling, disabling, or changing the address/port, it does not automatically applies to the whole system.

This PowerShell script from stackoverflow helps it a lot. https://stackoverflow.com/a/39079005/6458107https://stackoverflow.com/questions/21568502/ie-enable-disable-proxy-settings-via-registry

function Refresh-System
{
  $signature = @'
[DllImport("wininet.dll", SetLastError = true, CharSet=CharSet.Auto)]
public static extern bool InternetSetOption(IntPtr hInternet, int dwOption, IntPtr lpBuffer, int dwBufferLength);
'@

$INTERNET_OPTION_SETTINGS_CHANGED   = 39
$INTERNET_OPTION_REFRESH            = 37
$type = Add-Type -MemberDefinition $signature -Name wininet -Namespace pinvoke -PassThru
$a = $type::InternetSetOption(0, $INTERNET_OPTION_SETTINGS_CHANGED, 0, 0)
$b = $type::InternetSetOption(0, $INTERNET_OPTION_REFRESH, 0, 0)
return $a -and $b
}
Refresh-System

Save that script into something like RefreshPROXY.ps1 and run it whenever you need to.

powershell -command "$signature = '[DllImport("^""wininet.dll"^"", SetLastError = true, CharSet=CharSet.Auto)] public static extern bool InternetSetOption(IntPtr hInternet, int dwOption, IntPtr lpBuffer, int dwBufferLength);'; $type = Add-Type -MemberDefinition $signature -Name wininet -Namespace pinvoke -PassThru; $type::InternetSetOption(0,39,0,0); $type::InternetSetOption(0,37,0,0);" > nul

This could be a feature and be run as dispatch proxy-refresh if it were implemented. With it's own Rust code, of course, good luck devs... 👍

Congrats for the release with Rust as known broadly by it's safe memory handling. As a long time user, I just realized that there's a new release.

There's a few topic from the past repo:

1. One and only self-hosted Speedify alternative as channel bonding and not the typical ubiquitous load balancing? #82 #89
2. Automatically restart the dispatch start after fatal crash? #93 #95 #100
3. Automatically bypass the proxy server for local (intranet) addresses #92
4. Why drop the support for HTTP? And even further of encrypted proxy? Such as HTTPS Proxy or the new HTTP/3 which is QUIC-based? #94

Were part of those at least already implemented? Any milestone plan?