Some questions about wireproxy HOT 4 CLOSED

Thanks for your reply, it's really a great REPO.
I have a one click script that installs WARP. And I have integrated the functionality of wireproxy.
Before, I installed warp in alpine docker and used 'gost' to create a socks5 proxy to the host.
Or use iptables + dnsmasq + ipset to divert some websites to warp.

Here is my REPO: https://github.com/fscarmen/warp

from wireproxy.

1. I haven't tested it with IPv6, but in theory it should work. A sample config snippet would probably look like this:

SelfEndpoint = fe80::1
PeerEndpoint = [fc80::1]:53

2. No, it merely takes a path to a config file and that's it. No pass paramteres.
3. So in #3 @MuratovAS mentioned that they have tested wireproxy in a ARM64 settings, so I'd imagine it would work. I'm gonna test it on termux in my phone and see if it works or not.

Edit: I've tested it on my phone on termux and it works on ARM64.

from wireproxy.

Just realized I missed question 4. Those are essentially static TCP tunnels. TCPClientTunnel allows you to host a TCP server on your localhost, and any traffic received will be forwarded to the specified endpoint over wireguard. TCPServerTunnel is the opposite, hosting a TCP server in the wireguard network and forwarding any received traffic on a localhost.

This can be useful when you have an application that doesn't support socks5, but the destination endpoint is already known beforehand. Or receiving incoming TCP traffic over wireguard, without configuring firewalls at kernel space.

from wireproxy.

1. I haven't tested it with IPv6, but in theory it should work. A sample config snippet would probably look like this:

SelfEndpoint = fe80::1
PeerEndpoint = [fc80::1]:53

2. No, it merely takes a path to a config file and that's it. No pass paramteres.
3. So in Docker container implementation #3 @MuratovAS mentioned that they have tested wireproxy in a ARM64 settings, so I'd imagine it would work. I'm gonna test it on termux in my phone and see if it works or not.

Edit: I've tested it on my phone on termux and it works on ARM64.

So apparently IPv6 wasn't working and I figured out why. In the newest commit I've added support for IPv6 and I have tested it on ipv6.google.com and test-ipv6.com with cloudflare warp. Here's my config:

[Interface]
PrivateKey = censored
Address = 172.16.0.2/32
Address = fd01:5ca1:ab1e:8d86:bd6:e0d3:8ad9:1c81/128
MTU = 1280
DNS = 1.1.1.1

[Peer]
PublicKey = censored
AllowedIPs = 0.0.0.0/0
AllowedIPs = ::/0
Endpoint = engage.cloudflareclient.com:2408

[Socks5]
BindAddress = 127.0.0.1:25344

[TCPClientTunnel]
BindAddress = 127.0.0.1:25565
Target = play.cubecraft.net:25565

from wireproxy.