11/1/2023 0 Comments Amimullvad![]() UPD wg-quick output: / # wg-quick up vpn1 I also found that some WireGuard clients have this feature out of the box:īut with the docker setup, I'm kinda stuck now and would appreciate any help. PostDown = iptables -D FORWARD -i %i -j ACCEPT iptables -D FORWARD -o %i -j ACCEPT iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE PostUp = iptables -A FORWARD -i %i -j ACCEPT iptables -A FORWARD -o %i -j ACCEPT iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE ![]() PostDown = iptables -D FORWARD -i %i -j ACCEPT iptables -D FORWARD -o %i -j ACCEPT iptables -t nat -D POSTROUTING -o wg2 -j MASQUERADE ![]() PostUp = iptables -A FORWARD -i %i -j ACCEPT iptables -A FORWARD -o %i -j ACCEPT iptables -t nat -A POSTROUTING -o wg2 -j MASQUERADE ![]() I also tried to have 2 separate interfaces but that doesn't work as well. My first idea was to use the same interface and 2 peers (and configure routing via AllowedIPs param so that VPN_1 uses 0.0.0.0/0 and VPN_2 uses /32) but I have 2 different private keys so probably that's not going to work. I want to achieve the same goal but in a single docker container (preferably without any socks proxy). If I configure my app to use the socks5 proxy it does the job and I have APP -> VPN_1 -> VPN_2 -> destination. ![]() I need to configure 2 different wireguard VPN networks on the same client machine and nest them so that when I make a request it passes through VPN_1 then VPN_2 and then reaches the destination website.Ĭurrently, I have a working configuration when VPN_1 is configured on a host machine, VPN_2 is configured in a docker container and exposed via socks proxy. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |