NAT 1:1

[rl82]

is interesting that i can ping only .101 (port forward virual ip) and not .102 (1:1 NAT virtual ip).
ssh no success

[bartjsmit]

ssh no success

Can you make sure the SSH server is installed and running?

sudo apt-get install openssh-server
systemctl status sshd

Bart...

[rl82]

ssh no success

Can you make sure the SSH server is installed and running?

sudo apt-get install openssh-server
systemctl status sshd

Bart...

thanks Bart for your help.
You mean to install  it in webterm?

[bartjsmit]

ubuntu1 - the server that sits behind your 1:1 NAT

[rl82]

sorry Bart, i am not sure i understood.
Might you be please so kind to explain me better?
Do you need some screenshot regarding the configuration?

Thanks

[Patrick M. Hausen]

You are trying to SSH to a server behind 1:1 NAT. Bart asked you to check and make sure that SSH is running on that server. Might be simply not active ...

[rl82]

thanks
here are the output

[bartjsmit]

Can you confirm it works now from your local LAN and from the WAN side of your 1:1 NAT?

There may be a host firewall on ubuntu1 that limits access (UFW in that case). If it doesn't work from your LAN, ensure SSH is allowed from everywhere (at least temporarily for testing)

Bart...

[rl82]

Hallo Bart,

i am sorry but i have difficulties to understand the goal:

my problem is that i am able to reach the webserver on ubuntu with his private address (192.168.56.3:81) although i set the NAT Port  Forwarding and the NAT 1:1. I see that if i disable the NAT port forwarding the problem still persists while if i disable the NAT 1:1 the problem is solved, so i assume there is some misconfiguration on the NAT 1:1.

[bartjsmit]

To me the goal of 1:1 NAT is for traffic parity on the WAN side. The destination address for traffic to your server from outside  is the same as the source address of the return traffic. This solves a lot of issues with NAT (but not all).

Once that bit works, you can worry about other issues.

[rl82]

Hello Bart,

thank you for your answer. What you mean with "traffic parity" please?
can be that this options has enabled this bug?
"block private network disabled"

[rl82]

I can do ssh from internal browser webterm-1
no ssh from external browser webterm-2

[rl82]

so i am not able to solve it 
i will hit my head in this hours and i will find it out.
If i find the solution, i will post it and share for the community
thanks everybody

[rl82]

so no success.
The problem persists: the private ip address of the webserver (192.168.56.3) is REACHABLE from WAN (external network) when i add the NAT 1:1 Rule.