Quick Heal IP to be accessed through internet
-
If you were doing PAT with my example above you would also choose another port, like 4011, to expose that service as.
-
Most firewalls make you "Label" or "Name" a port before using it. This is a little silly but has its purpose, I guess. So in the case of my example, you might call port 22 "SSH". Many firewalls already label common ports so that you don't have to know what they are.
-
My guess is that ISPs are IP poor in India, so they put all of the clients on private IPs. I know of at least one US ISP that does this as well. So for all intents and purposes in @Lakshmana's case these are "public IPs".
-
@Kelly said:
My guess is that ISPs are IP poor in India, so they put all of the clients on private IPs. I know of at least one US ISP that does this as well. So for all intents and purposes in @Lakshmana's case these are "public IPs".
Well public vs. private are very basic networking concepts. We need those terms to be used correctly or none of this is going to make sense. If those addresses are private, then NATing won't help either. The service simply is not available.
This is a case where hiding the IP addresses is just going to make this impossible to answer if we feel he doesn't know the networking to have the discussion.
-
@Lakshmana, instead of asking us how to setup NAT, can you explain to us what you're trying to accomplish via NAT? Most people who ask how to do a given task often are asking how to do something that will not solve their problem. @scottalanmiller has answered many networking questions.
Are you trying to connect this AV console between two sites? If that's the case, and you were accessing it via a public IP before, just change the IP in your URL or whatever you're accessing it from and the rest will stay the same and just work. I don't understand where your confusion is.
Is the issue that your public IP changed and you've lost access to the system? How were you accessing this device before? Can you give us some specifics or exacts to help us understand what you're talking about? You can't give us too much info. Figure out the question and we'll help you with the solution.
-
What are you trying to do?
And is your WAN IP a public or private (RFC 1918) address? You might need to pay for a static IP if you currently have a private IP for your WAN.
-
@Kelly said:
My guess is that ISPs are IP poor in India, so they put all of the clients on private IPs. I know of at least one US ISP that does this as well. So for all intents and purposes in @Lakshmana's case these are "public IPs".
Many WISPs are double natting.
-
@thecreativeone91 said:
What are you trying to do?
And is your WAN IP a public or private (RFC 1918) address? You might need to pay for a static IP if you currently have a private IP for your WAN.
I fear that what you just said will only confuse him.
If you address starts with any of these, it's private:
10.0.0.0
172.16.0.0-172.31.0.0
192.168.0.0If it starts with anything else, it's a public IP. Can you tell us first off what your IP address is, or at least if it's actually public or private?
-
-
@mlnews said:
@handsofqwerty said:
If it starts with anything else, it's a public IP.
We hope
Ok, yes, we hope. I shouldn't speak in such absolutes, but it's a pretty safe bet...
