Services (http, ssh) Not Accessible Using Public IP

Issues related to configuring your network
Post Reply
05Cent
Posts: 1
Joined: 2018/12/03 18:41:25

Services (http, ssh) Not Accessible Using Public IP

Post by 05Cent » 2018/12/03 19:19:39

Good day to all,

I need help with accessing services using WAN IP. Access to services from public remote IP (123.123.123.1) to public IP (134.134.134.1) of my Centos VM instance does not work (ping works). Internally (192.168.1.0/24) those services are working and are accessible. Tested this on a fresh minimal install and other instances, results are the same. On the same network we have another CentOS VM instance with those services accessible externally (134.134.134.2). Tested on multiple routers, router port forwarding is working and ping works externally. Am I missing some configuration on the CentOS installation? tried disabling firewalld, still not working. Any help is appreciated.

Thanks.
B

aks
Posts: 3073
Joined: 2014/09/20 11:22:14

Re: Services (http, ssh) Not Accessible Using Public IP

Post by aks » 2018/12/07 21:29:47

Okay the big jump out here is NAT. How are you implementing NAT? How fdoes the external address "map" to the internal address?

Look into your NAT.

User avatar
jlehtone
Posts: 4523
Joined: 2007/12/11 08:17:33
Location: Finland

Re: Services (http, ssh) Not Accessible Using Public IP

Post by jlehtone » 2018/12/10 11:45:57

A VM with two network interfaces, WAN (134.134.134.0/24?) and LAN (192.168.1.0/24).

Nothing is said about the VM host platform.

What could it be within the VM?
* firewall
* selinux
* service not listening an interface
* routing

What is the default route / static route to 123.123.123.1?



Wait! "router port forwarding"? What forwarding?
If the VM's genuinely have public addresses, then there is no need to "forward" or NAT anything at the router; just route between public subnets.

Post Reply