![]() ![]() IPSec has become the defacto standard protocol for secure Internet communications, providing confidentiality, authentication and integrity. IKEv2 (Internet key exchange version 2) is part of the IPSec protocol suite. The PPTP specification does not actually describe encryption or authentication features and relies on the PPP protocol being tunneled to implement security functionality. ![]() A PREROUTING -i ens3 -p udp -m multiport -dports 80,25,995,110,443,465,993,143 -j DNAT -to-destination 10.0.0.A very basic VPN protocol based on PPP. A PREROUTING -i ens3 -p tcp -m multiport -dports 1000:51820 -j DNAT -to-destination 10.0.0.2 ![]() A PREROUTING -i ens3 -p tcp -m multiport -dports 51822:65534 -j DNAT -to-destination 10.0.0.2 A PREROUTING -i ens3 -p udp -m multiport -dports 51822:65534 -j DNAT -to-destination 10.0.0.2 ![]() A PREROUTING -i ens3 -p udp -m multiport -dports 1000:51820 -j DNAT -to-destination 10.0.0.2 This is my WG Server IPTables configuration to forward the ports to the EdgeRouter through WG0: # Generated by iptables-save v1.8.7 on Sun Jan 9 11:04:33 2022 The issue is that when a user connects let's say to 22.22.22.22:80 he is displayed succesfully the web page, but his IP to the server results to be 10.0.0.1 and not the user public IP. I am forwarding all the ports from OVH's VPS (1-65535) with IPTables to my EdgeRouter through the wg0 tunnel and then to my homeserver and that works. The graph for my connection is like this: OVH VPS Wireguard Server WG0 Tunnel (LOCAL Tunnel 10.0.0.1) (LOCAL Tunnel 10.0.0.2) EdgeRouter XĮdgeRouter-X (LOCAL 192.168.1.1) (LOCAL 192.168.1.10) HOME-SERVER This is because I want to host an home server using OVH's IP and Anti-DDoS instead of my own public ip which is unprotected. I have set up my EdgeRouter-X as a WireGuard client (using IPv6) so that my public IP is shown to be the WireGuard server's public IP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |