So, packets are being NATed. We can ping 192.168.1.200 from network 192.168.1.0/24 and get a reply from 172.30.1.2. NAT is working.
The problem is, the server 172.30.1.2 accepts telnet connections only from it's local network, 172.30.1.0/30
Is it possible to do a "Double NAT"?
Now packets travelling from 192.168.1.0/24 with dest address of 192.168.1.200 are being NATed(dest addr translated 192.168.1.200->172.30.1.2) and are getting to the server with the source address from 192.168.1.0/24.
I need to change the source address of this packets to 172.30.1.1 so that telnet connections were accepted.
It is quite unfamiliar to do NATing because the connections are rejected by the server from another network.Check at server side and allow connections from another network.It can be a problem with the Anti virus that prevents the connections happening form another network.
You need to change the source address of packets originating from the outside interface (192.168.1.0/24 network).
This is possible with ip nat outside (translates source address of packets going from outside to inside) statement.
However ip nat outside requires a network matched via an access-list (192.168.1.0/24) to be mapped to a pool rather than an interface
access list 102 permit ip 192.168.1.0 0.0.0.255 any
ip nat pool poolout 172.30.1.3 172.30.1.254 netmask 255.255.255.0
ip nat outside source list 102 pool poolout add-route
But since you have only two inside local (172.30.1.2 and 172.30.2.2, /30 mask) address to which these outside global address must be mapped, this will not work.
Another solution is to use another router in between and map all 192.168.1.0/24 network to single address (X.X.X.X) with NAT overload keyword ofcourse.
then on your router
ip nat outside source static X.X.X.X 172.30.1.3 add-route
As you can see all the solutions of changing the source address of the 192.168.1.0/24 network requires you to have a prefix length greater than /30 for the ip nat inside interfaces to support more than 2 address for (172.30.1.0/30 subnet). If these solutions need to be implemented, you'll obviously need to make modifications on the server (changing it's subnet mask) .
The point, it's easier to make changes on server to access packets from the source address from the network 192.168.1.0/24.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...