Brian wrote:
Rob;
On Mon, 2015-08-03 at 22:12 +0200, Rob Janssen wrote:
That is correct, but it does not actually route
the reply traffic to there.
Or at least, it is not received at our end of the tunnel.
Can you ping the public address?
I now have a ping running from 44.137.0.1, please observe what is happening.
n1uro@n1uro:~$ fping 213.222.29.194
213.222.29.194 is alive
n1uro@n1uro:~$ fping 44.137.0.1
44.137.0.1 is alive
n1uro@n1uro:~$
Now it suddenly starts to work!
--- 44.88.0.9 ping statistics ---
1117 packets transmitted, 106 received, 90% packet loss, time 1122044ms
rtt min/avg/max/mdev = 116.516/119.247/130.393/2.411 ms
Is there some stateful firewall e.g. in a router that you have set to "forward a
protocol" or "dmz"?
I have seen before that such forwardings sometimes are not transparent and only work when
the
first traffic is from inside.
Rob