IPTables and Port Forwarding on an OpenVPNAS Server





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I have a new OpenVPNas server running on CentOS 7 (Not married to CentOS 7). That I working on replacing an expensive Commercial VPN that has a Public Static IP. Being that the OpenVPNas server is what amounts to my private VPN Server I just need to forward a couple of ports to a static internal VPN address to replace the Commercial Server.



I have the VPN Client setup and I can ping from the Server to the Client's static IP and from the Static IP to the server's Public IP and beyond.



I want the following ports on the server's IP forwarded/NAT'd/Masqueraded to the internal VPN.




Public TCP 80 ie Server Public's:80 -> 172.28.28.28:80
Public UDP Ports 2074-2093
Public TCP Ports 15425-15427
Public UDP Ports 5198-5200
Public TCP Ports 5198-5200


I have tried different route / iptables commands, but I have yet to figure out the magic bullet. I believe it's a simple process but the solution is eluding me. Via SSH the server can connect to the VPN port 80 and I get the client's via the VPN's web interface. So the basic routing is working as expected.



I can't figure out the magic routing a packet destined for port 80 in the server's page to Forwarding




[root@vpn ~]# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1

[root@vpn ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 209.182.218.1 0.0.0.0 UG 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
172.27.224.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t0
172.27.228.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t1
172.27.232.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t2
172.27.236.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t3
172.28.28.28 0.0.0.0 255.255.255.255 UH 0 0 0 as0t0
209.182.218.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

[root@vpn ~]# ip route list
default via 209.182.218.1 dev eth0
169.254.0.0/16 dev eth0 scope link metric 1002
172.27.224.0/22 dev as0t0 proto kernel scope link src 172.27.224.1
172.27.228.0/22 dev as0t1 proto kernel scope link src 172.27.228.1
172.27.232.0/22 dev as0t2 proto kernel scope link src 172.27.232.1
172.27.236.0/22 dev as0t3 proto kernel scope link src 172.27.236.1
172.28.28.28 dev as0t0 proto static
209.182.218.0/24 dev eth0 proto kernel scope link src 209.182.218.187

[root@vpn ~]# ifconfig
as0t0: flags=4305 mtu 1500
inet 172.27.224.1 netmask 255.255.252.0 destination 172.27.224.1
inet6 fe80::4da2:53e9:7fba:8f11 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
RX packets 219 bytes 13438 (13.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 250 bytes 202093 (197.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

as0t1: flags=4305 mtu 1500
inet 172.27.228.1 netmask 255.255.252.0 destination 172.27.228.1
inet6 fe80::d557:1adc:c34c:4954 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 144 (144.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

as0t2: flags=4305 mtu 1500
inet 172.27.232.1 netmask 255.255.252.0 destination 172.27.232.1
inet6 fe80::be1a:bfd3:3c25:20f9 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 144 (144.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

as0t3: flags=4305 mtu 1500
inet 172.27.236.1 netmask 255.255.252.0 destination 172.27.236.1
inet6 fe80::bfed:3f81:6938:bbc7 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 144 (144.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163 mtu 1500
inet 209.182.218.187 netmask 255.255.255.0 broadcast 209.182.218.255
inet6 fe80::216:3eff:fecc:ddf3 prefixlen 64 scopeid 0x20
ether 00:16:3e:cc:dd:f3 txqueuelen 1000 (Ethernet)
RX packets 11673 bytes 1350674 (1.2 MiB)
RX errors 0 dropped 14 overruns 0 frame 0
TX packets 5295 bytes 1099520 (1.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 9 bytes 748 (748.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9 bytes 748 (748.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0









share|improve this question









New contributor




MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



























    0















    I have a new OpenVPNas server running on CentOS 7 (Not married to CentOS 7). That I working on replacing an expensive Commercial VPN that has a Public Static IP. Being that the OpenVPNas server is what amounts to my private VPN Server I just need to forward a couple of ports to a static internal VPN address to replace the Commercial Server.



    I have the VPN Client setup and I can ping from the Server to the Client's static IP and from the Static IP to the server's Public IP and beyond.



    I want the following ports on the server's IP forwarded/NAT'd/Masqueraded to the internal VPN.




    Public TCP 80 ie Server Public's:80 -> 172.28.28.28:80
    Public UDP Ports 2074-2093
    Public TCP Ports 15425-15427
    Public UDP Ports 5198-5200
    Public TCP Ports 5198-5200


    I have tried different route / iptables commands, but I have yet to figure out the magic bullet. I believe it's a simple process but the solution is eluding me. Via SSH the server can connect to the VPN port 80 and I get the client's via the VPN's web interface. So the basic routing is working as expected.



    I can't figure out the magic routing a packet destined for port 80 in the server's page to Forwarding




    [root@vpn ~]# sysctl net.ipv4.ip_forward
    net.ipv4.ip_forward = 1

    [root@vpn ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 209.182.218.1 0.0.0.0 UG 0 0 0 eth0
    169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
    172.27.224.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t0
    172.27.228.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t1
    172.27.232.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t2
    172.27.236.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t3
    172.28.28.28 0.0.0.0 255.255.255.255 UH 0 0 0 as0t0
    209.182.218.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

    [root@vpn ~]# ip route list
    default via 209.182.218.1 dev eth0
    169.254.0.0/16 dev eth0 scope link metric 1002
    172.27.224.0/22 dev as0t0 proto kernel scope link src 172.27.224.1
    172.27.228.0/22 dev as0t1 proto kernel scope link src 172.27.228.1
    172.27.232.0/22 dev as0t2 proto kernel scope link src 172.27.232.1
    172.27.236.0/22 dev as0t3 proto kernel scope link src 172.27.236.1
    172.28.28.28 dev as0t0 proto static
    209.182.218.0/24 dev eth0 proto kernel scope link src 209.182.218.187

    [root@vpn ~]# ifconfig
    as0t0: flags=4305 mtu 1500
    inet 172.27.224.1 netmask 255.255.252.0 destination 172.27.224.1
    inet6 fe80::4da2:53e9:7fba:8f11 prefixlen 64 scopeid 0x20
    unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
    RX packets 219 bytes 13438 (13.1 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 250 bytes 202093 (197.3 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    as0t1: flags=4305 mtu 1500
    inet 172.27.228.1 netmask 255.255.252.0 destination 172.27.228.1
    inet6 fe80::d557:1adc:c34c:4954 prefixlen 64 scopeid 0x20
    unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 3 bytes 144 (144.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    as0t2: flags=4305 mtu 1500
    inet 172.27.232.1 netmask 255.255.252.0 destination 172.27.232.1
    inet6 fe80::be1a:bfd3:3c25:20f9 prefixlen 64 scopeid 0x20
    unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 3 bytes 144 (144.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    as0t3: flags=4305 mtu 1500
    inet 172.27.236.1 netmask 255.255.252.0 destination 172.27.236.1
    inet6 fe80::bfed:3f81:6938:bbc7 prefixlen 64 scopeid 0x20
    unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 3 bytes 144 (144.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    eth0: flags=4163 mtu 1500
    inet 209.182.218.187 netmask 255.255.255.0 broadcast 209.182.218.255
    inet6 fe80::216:3eff:fecc:ddf3 prefixlen 64 scopeid 0x20
    ether 00:16:3e:cc:dd:f3 txqueuelen 1000 (Ethernet)
    RX packets 11673 bytes 1350674 (1.2 MiB)
    RX errors 0 dropped 14 overruns 0 frame 0
    TX packets 5295 bytes 1099520 (1.0 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73 mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10
    loop txqueuelen 1000 (Local Loopback)
    RX packets 9 bytes 748 (748.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 9 bytes 748 (748.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0









    share|improve this question









    New contributor




    MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I have a new OpenVPNas server running on CentOS 7 (Not married to CentOS 7). That I working on replacing an expensive Commercial VPN that has a Public Static IP. Being that the OpenVPNas server is what amounts to my private VPN Server I just need to forward a couple of ports to a static internal VPN address to replace the Commercial Server.



      I have the VPN Client setup and I can ping from the Server to the Client's static IP and from the Static IP to the server's Public IP and beyond.



      I want the following ports on the server's IP forwarded/NAT'd/Masqueraded to the internal VPN.




      Public TCP 80 ie Server Public's:80 -> 172.28.28.28:80
      Public UDP Ports 2074-2093
      Public TCP Ports 15425-15427
      Public UDP Ports 5198-5200
      Public TCP Ports 5198-5200


      I have tried different route / iptables commands, but I have yet to figure out the magic bullet. I believe it's a simple process but the solution is eluding me. Via SSH the server can connect to the VPN port 80 and I get the client's via the VPN's web interface. So the basic routing is working as expected.



      I can't figure out the magic routing a packet destined for port 80 in the server's page to Forwarding




      [root@vpn ~]# sysctl net.ipv4.ip_forward
      net.ipv4.ip_forward = 1

      [root@vpn ~]# route -n
      Kernel IP routing table
      Destination Gateway Genmask Flags Metric Ref Use Iface
      0.0.0.0 209.182.218.1 0.0.0.0 UG 0 0 0 eth0
      169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
      172.27.224.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t0
      172.27.228.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t1
      172.27.232.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t2
      172.27.236.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t3
      172.28.28.28 0.0.0.0 255.255.255.255 UH 0 0 0 as0t0
      209.182.218.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

      [root@vpn ~]# ip route list
      default via 209.182.218.1 dev eth0
      169.254.0.0/16 dev eth0 scope link metric 1002
      172.27.224.0/22 dev as0t0 proto kernel scope link src 172.27.224.1
      172.27.228.0/22 dev as0t1 proto kernel scope link src 172.27.228.1
      172.27.232.0/22 dev as0t2 proto kernel scope link src 172.27.232.1
      172.27.236.0/22 dev as0t3 proto kernel scope link src 172.27.236.1
      172.28.28.28 dev as0t0 proto static
      209.182.218.0/24 dev eth0 proto kernel scope link src 209.182.218.187

      [root@vpn ~]# ifconfig
      as0t0: flags=4305 mtu 1500
      inet 172.27.224.1 netmask 255.255.252.0 destination 172.27.224.1
      inet6 fe80::4da2:53e9:7fba:8f11 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 219 bytes 13438 (13.1 KiB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 250 bytes 202093 (197.3 KiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      as0t1: flags=4305 mtu 1500
      inet 172.27.228.1 netmask 255.255.252.0 destination 172.27.228.1
      inet6 fe80::d557:1adc:c34c:4954 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 3 bytes 144 (144.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      as0t2: flags=4305 mtu 1500
      inet 172.27.232.1 netmask 255.255.252.0 destination 172.27.232.1
      inet6 fe80::be1a:bfd3:3c25:20f9 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 3 bytes 144 (144.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      as0t3: flags=4305 mtu 1500
      inet 172.27.236.1 netmask 255.255.252.0 destination 172.27.236.1
      inet6 fe80::bfed:3f81:6938:bbc7 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 3 bytes 144 (144.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      eth0: flags=4163 mtu 1500
      inet 209.182.218.187 netmask 255.255.255.0 broadcast 209.182.218.255
      inet6 fe80::216:3eff:fecc:ddf3 prefixlen 64 scopeid 0x20
      ether 00:16:3e:cc:dd:f3 txqueuelen 1000 (Ethernet)
      RX packets 11673 bytes 1350674 (1.2 MiB)
      RX errors 0 dropped 14 overruns 0 frame 0
      TX packets 5295 bytes 1099520 (1.0 MiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      lo: flags=73 mtu 65536
      inet 127.0.0.1 netmask 255.0.0.0
      inet6 ::1 prefixlen 128 scopeid 0x10
      loop txqueuelen 1000 (Local Loopback)
      RX packets 9 bytes 748 (748.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 9 bytes 748 (748.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0









      share|improve this question









      New contributor




      MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I have a new OpenVPNas server running on CentOS 7 (Not married to CentOS 7). That I working on replacing an expensive Commercial VPN that has a Public Static IP. Being that the OpenVPNas server is what amounts to my private VPN Server I just need to forward a couple of ports to a static internal VPN address to replace the Commercial Server.



      I have the VPN Client setup and I can ping from the Server to the Client's static IP and from the Static IP to the server's Public IP and beyond.



      I want the following ports on the server's IP forwarded/NAT'd/Masqueraded to the internal VPN.




      Public TCP 80 ie Server Public's:80 -> 172.28.28.28:80
      Public UDP Ports 2074-2093
      Public TCP Ports 15425-15427
      Public UDP Ports 5198-5200
      Public TCP Ports 5198-5200


      I have tried different route / iptables commands, but I have yet to figure out the magic bullet. I believe it's a simple process but the solution is eluding me. Via SSH the server can connect to the VPN port 80 and I get the client's via the VPN's web interface. So the basic routing is working as expected.



      I can't figure out the magic routing a packet destined for port 80 in the server's page to Forwarding




      [root@vpn ~]# sysctl net.ipv4.ip_forward
      net.ipv4.ip_forward = 1

      [root@vpn ~]# route -n
      Kernel IP routing table
      Destination Gateway Genmask Flags Metric Ref Use Iface
      0.0.0.0 209.182.218.1 0.0.0.0 UG 0 0 0 eth0
      169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
      172.27.224.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t0
      172.27.228.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t1
      172.27.232.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t2
      172.27.236.0 0.0.0.0 255.255.252.0 U 0 0 0 as0t3
      172.28.28.28 0.0.0.0 255.255.255.255 UH 0 0 0 as0t0
      209.182.218.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

      [root@vpn ~]# ip route list
      default via 209.182.218.1 dev eth0
      169.254.0.0/16 dev eth0 scope link metric 1002
      172.27.224.0/22 dev as0t0 proto kernel scope link src 172.27.224.1
      172.27.228.0/22 dev as0t1 proto kernel scope link src 172.27.228.1
      172.27.232.0/22 dev as0t2 proto kernel scope link src 172.27.232.1
      172.27.236.0/22 dev as0t3 proto kernel scope link src 172.27.236.1
      172.28.28.28 dev as0t0 proto static
      209.182.218.0/24 dev eth0 proto kernel scope link src 209.182.218.187

      [root@vpn ~]# ifconfig
      as0t0: flags=4305 mtu 1500
      inet 172.27.224.1 netmask 255.255.252.0 destination 172.27.224.1
      inet6 fe80::4da2:53e9:7fba:8f11 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 219 bytes 13438 (13.1 KiB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 250 bytes 202093 (197.3 KiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      as0t1: flags=4305 mtu 1500
      inet 172.27.228.1 netmask 255.255.252.0 destination 172.27.228.1
      inet6 fe80::d557:1adc:c34c:4954 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 3 bytes 144 (144.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      as0t2: flags=4305 mtu 1500
      inet 172.27.232.1 netmask 255.255.252.0 destination 172.27.232.1
      inet6 fe80::be1a:bfd3:3c25:20f9 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 3 bytes 144 (144.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      as0t3: flags=4305 mtu 1500
      inet 172.27.236.1 netmask 255.255.252.0 destination 172.27.236.1
      inet6 fe80::bfed:3f81:6938:bbc7 prefixlen 64 scopeid 0x20
      unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 3 bytes 144 (144.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      eth0: flags=4163 mtu 1500
      inet 209.182.218.187 netmask 255.255.255.0 broadcast 209.182.218.255
      inet6 fe80::216:3eff:fecc:ddf3 prefixlen 64 scopeid 0x20
      ether 00:16:3e:cc:dd:f3 txqueuelen 1000 (Ethernet)
      RX packets 11673 bytes 1350674 (1.2 MiB)
      RX errors 0 dropped 14 overruns 0 frame 0
      TX packets 5295 bytes 1099520 (1.0 MiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      lo: flags=73 mtu 65536
      inet 127.0.0.1 netmask 255.0.0.0
      inet6 ::1 prefixlen 128 scopeid 0x10
      loop txqueuelen 1000 (Local Loopback)
      RX packets 9 bytes 748 (748.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 9 bytes 748 (748.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0






      iptables routing port-forwarding iptables-redirect






      share|improve this question









      New contributor




      MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 2 hours ago









      G-Man

      13.6k93770




      13.6k93770






      New contributor




      MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 4 hours ago









      MrLimoMrLimo

      1




      1




      New contributor




      MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      MrLimo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          MrLimo is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510834%2fiptables-and-port-forwarding-on-an-openvpnas-server%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          MrLimo is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          MrLimo is a new contributor. Be nice, and check out our Code of Conduct.













          MrLimo is a new contributor. Be nice, and check out our Code of Conduct.












          MrLimo is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510834%2fiptables-and-port-forwarding-on-an-openvpnas-server%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          CARDNET

          Boot-repair Failure: Unable to locate package grub-common:i386

          濃尾地震