There are no routes through the tunnel. You can add one with "ip route"
(see ip-route(8)) but there is probably an option in the VPN
configuration to automatically add it whenever the VPN is connected.
On 12/20/18 11:16, Josiah Chinedu wrote:
default via 142.9x.x.x dev eth0 proto static
10.16.x.x/16 dev eth0 proto kernel scope link src 10.16.x.x
142.9x.x.x/20 dev eth0 proto kernel scope link src 142.9x.x.x (public IP)
On Thu, Dec 20, 2018 at 4:37 PM zrm <zrm@xxxxxxxxxxxxxxx> wrote:
What does the output of "ip route" have to say for itself?
On 12/20/18 08:47, Josiah Chinedu wrote:
Yes am trying to pass traffic through the tunnel.
On Thu, Dec 20, 2018 at 12:54 PM Josiah Chinedu
<josiahaccounts@xxxxxxxxx> wrote:
Hello, i am having issues passing traffic through a tunnel that was
created using StrongSwan.
Since the tunnel is up, i am having difficulties connecting to through
the tunnel to the partner's server.
The idea is to route incoming traffic through the tunnel to the
partners server ip.
I have tried lots of solution but none seems to work.
Here is my iptables current configuration:
x.x.x.x = external IP
y.y.y.y = VPN public IP
z.z.z.z = Partner Server Private IP
port = partner open port
iptables -t nat -A PREROUTING -s x.x.x.x -d y.y.y.y -p udp -j DNAT
--to-dest z.z.z.z:port
iptables -t nat -A POSTROUTING -d z.z.z.z -p udp --dport port -j SNAT
--to-source y.y.y.y:4500
