Quick Heal IP to be accessed through internet
-
@scottalanmiller OK Forget NAT now.
-
Don't keep saying that you "need to do this or that." Instead, tell us WHY you think the NAT is involved. Changing IP addresses does not affect NAT. Give us why you think NAT is related to this discussion. Either you've not told us what is happening or you don't understand what NAT is. One way or another, you are saying one thing and then saying you need to do something that is completely unrelated and we have no means of connecting the two.
-
@Lakshmana said:
@scottalanmiller OK Forget NAT now.
Very good.
Now, what do you need to accomplish?
-
@Lakshmana Please see this scenario
1)The system in one company with the IP 192.168.1.155
2)The other system from other company 192.168.2.200
3)I need this two system to communicate with the Quick Heal Antivirus.(New Public IP)Whether NATing is needed to be done for this process
-
@Lakshmana said:
1)The system in one company with the IP 192.168.1.155
2)The other system from other company 192.168.2.200These are not public IPs. Are these servers or clients.
-
@Lakshmana said:
Whether NATing is needed to be done for this process
Of course not. You just said that you were going to forget NATing. But here we go again.
NATing is for accessing things that you host, not for accessing things that other people host. Public IP addresses have no configuration in NAT.
Do you configure a NAT rule for every website that people use?
-
@Lakshmana said:
3)I need this two system to communicate with the Quick Heal Antivirus.(New Public IP)
So what's the issue? They should "just work". Have you tested them yet?
-
@scottalanmiller said:
So what's the issue? They should "just work". Have you tested them yet?
OK.I need to do Port restricted Cone NAT.
-
@Lakshmana said:
@scottalanmiller said:
So what's the issue? They should "just work". Have you tested them yet?
OK.I need to do Port restricted Cone NAT.
What does this mean?
-
@scottalanmiller PLease see this link
-
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".
