Quick Heal IP to be accessed through internet
-
What is the IP address of your Quick Heal device?
(just give us part of it). -
@Lakshmana said:
@scottalanmiller PLease see this link
I'm extremely aware of what NAT is and how it works. I've been doing NAT since it was actually cool (and not just generic and everyone had it.) I've built NAT systems in the mid-1990s when you couldn't just buy them. I know exactly what it is.
Now that you've provided a Wikipedia link why do you think that there is any reason for us to be discussing NAT?
-
@dafyre said:
What is the IP address of your Quick Heal device?
(just give us part of it).Like the first two octets.
-
@scottalanmiller Ok Forget.Everything discused eariler.Please give me the information to do Port NAting.How to do?
-
@Lakshmana said:
@scottalanmiller Ok Forget.Everything discused eariler.Please give me the information to do Port NAting.How to do?
Ports are not NATed. There is PATing.
Do you want to implement PATing (Port Address Translation) or do you want to do Port Forwarding?
-
To port forward, you just select the Private IP address and the Port that exist inside the NAT and expose them via the public IP of your NAT Firewall. The exact interface for this will vary but the process is always the same and extremely basic. You only need to know which IP address inside your network is for the server you want to host to the world and which port number you want exposed.
That's Port Forwarding on a NAT.
If you want to do PAT as well, you can tell your firewall to use a different port on the outside than the one used on the inside. This is less common, but not uncommon.
-
Example:
LAN (192.168.1.0) <--> NAT Firewall <--> Public WAN / Internet (208.45.31.8)
Internal SSH Server: 192.168.1.18
SSH Port: 22On the NAT Firewall: Selection IP of 192.168.1.18 and a Port of 22 to expose to the world.
-
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...
