ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 172.31.17.203 netmask 255.255.240.0 broadcast 172.31.31.255
inet6 fe80::4a7:e4ff:fe0b:d001 prefixlen 64 scopeid 0x20<link>
ether 06:a7:e4:0b:d0:01 txqueuelen 1000 (Ethernet)
RX packets 290357 bytes 388903715 (370.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 122943 bytes 17110046 (16.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 1495 bytes 509516 (497.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1495 bytes 509516 (497.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
IP 172.31.17.203 ==> IP NAT
ip public di map 'otomatis' oleh AWS ke 52.XX.XX.63
setau saya ini istilahnya NAT 1:1, 1 IP NAT di map ke 1 IP public
panel berbayar sudah banyak yg mendukung fitur ini, sedangkan panel opensource, cwp sudah mendukung tapi masih 'mentok' hanya mengenali IP NAT 192.168.xxx.xxx
tapi saya coba, ternyata tetap bisa dipakai walaupun prefix nat saya 172.xxx.xxx.xxx