I have a problem with my core layer. I have given public IP address of 142.48.2.0/30 by the internet service provider(ISP) and the private address is 172.16.0.0/24. In the core layer, I have active and standby router which have been configured using HSRP. the problem is that the public address provides only two ip addresses and I do not know to to make the Two routers share the same Public IP address.
Any ideas.
Unless that pipe going to your ISP is bigger than the link between your two routers, OR the link between your two routers is latent/slow I would not even try as the benefits would be miniscule. However, you would have to have to use MHSRP. Basically, double up on your private HSRP configuration.
http://www.cisco.com/c/en/us/support/docs/ip/hot-standby-router-protocol-hsrp/13781-7.html/index.html
"In order to utilize both paths from the host network to the server network, you can configure Multigroup HSRP (MHSRP) between R1 and R2. Essentially, R1 is configured with two HSRP groups (for example, group 1 and group 2) and R2 is also configured with the same HSRP groups. For group 1, R1 is the active router and R2 is the standby router. For group 2, R2 is the active router and R1 is the standby router. Then you configure half of the hosts' default gateways with the HSRP group 1 virtual IP address, and the other half of the hosts' default gateways with the HSRP group 2 virtual IP address."
Be careful about split-horizon, as I don't know how your ISP is set up.
http://searchnetworking.techtarget.com/definition/split-horizon
Related
I am using fiber internet service that company give me a device which assign me local ip like 192.168.0.1 ,2,3 and so on to my computer/ Laptop . but I want to change my local area ip like 172.15.15.1 etc. how to route my Ip
Thanks
Well since the ip is assigned by the service provider they are probably using DHCP server to assign you ip. So you are getting those segment ip's, these are basically private class c ip address. In order to get different range of IP's you can put your intermediate router and configure it to provide private class B IP address.You might need a cross cable to connect both the routers.
I use a static IP connection, Configured to TPLINK router.
I have a local server running which i can access from my network, but i want it to be accessed outside network.
So I did port forwarding. and its Successfully running.
Now the problem is :: The IP address of my WAN is also a private address like 10.10.X.X, so when am entering http://10.10.X.X, i can access my site, but not outside my network. Please guide me how to fix this?
If your WAN address is a private address, your ISP is using CGN. This is becoming more common since the RIRs have, or soon will, run out of public IP addresses to assign to ISPs. It sounds like your ISP has run out of public addresses and needs to use private addresses for its residential customers, reserving its remaining public addresses for its business customers which are willing to pay for public addresses.
Basically, your ISP is using NAT, too. You would need to have the ISP forward your port on its NAT router, but the odds of that are zero since it probably has a policy you agreed to to not host servers on your residential LAN (buried in the fine print of the ISP agreement). This situation will play out more and more over time.
You have to use the "Virtual Server" settings. Port triggering is used for.
Once the modem router is configured, the operation is as follows: 1. A local host makes an outgoing connection to an external host using a destination port number defined in the Trigger Port field. 2. The modem router records this connection, opens the incoming port or ports associated with this entry in the Port Triggering table, and associates them with the local host. 3. When necessary, the external host will be able to connect to the local host using one of the ports defined in the Incoming Ports field.
It is not used for incoming connections which are triggered from outside!
Of course, to have it working you have to have an application listening on that port not only having the firewall on Windows allowing the port.
After you set up the "Virtual Server" a port scanner should show you the port is open (even without having a running application listening) - it will try to port forward it. I use ShieldsUp for testing.
i have two instances in two different availability-zones which need to communicate with each other. they are inside vpc private subnets-
a) Will the traffic go through NAT when they talk to each other ?
b) And what will happen if they are in public subnet and have elastic ip attached ?
c) What if they are in ec2 classic in two different az ?
All of these scenarios can go either way, depending on how the instances address each other.
All VPC instances have a private IP address, even if they also have an Elastic (public) IP or a dynamic public IP from the pool.
As long as A connects to B using B's private IP address as the destination, the traffic will not use B's public IP, and will not traverse the NAT (when A doesn't have a public IP) and will not use A's public or elastic IP (if it has one).
If A connects to B using B's public address as the destination (if B has one) then none of the statements in the previous paragraph will hold true... So, you almost always want to use the private IP of an instance when connecting to another instance.
That also holds true in EC-Classic.
You will also pay for data transfer between instances in different availability zones, and in the same AZ if the instances are in two different VPCs (using VPC peering). As of this writing, the charge is $0.02/GB. In most cases, to be precise, one instance is charged $0.01 to send the data, and the other is charged $0.01 to receive it, but that's a net of $0.02. Conversely, when instances communicate with each other across two different regions, the sending instance pays $0.02 and the receiving instance pays $0.00... and, of course, public IPs are always involved at some layer of a multi-region setup.
You don't pay for data transfer between instances in the same AZ (and VPC, if VPC) unless you use NAT or elastic/public IP addresses, which -- aside from potential and unnecessary loss of performance -- is another reason not to do that... which, again, should only happen if one instance does not connect to the the other using private IP addresses as the destination address.
I have a LAMP server. It works great if I access using the private ip e.g. 192.168... I also did port forwarding to access to it using its public ip and it works great if I'm not in the same LAN as the server, so if I use mobile data, I can access to it, but if I'm with my laptop which is connected to the same router, I can't.
How can I access to a lamp server using the public ip and being in the same LAN? I've read about creating a DNS server but I think that's too complex for this and there must be an easier answer.
Thank you!
What you need is NAT hair-pinning on the router. Presently Cisco routers support it.
You may also create a DNS host-entry on your PC which points the public IP(or DNS name) to local IP.
If two hosts (called X1 and X2) are behind the same NAT and exchanging traffic, the NAT may allocate an address on the outside of the NAT for X2, called X2':x2'. If X1 sends traffic to X2':x2', it goes to the NAT, which must relay the traffic
from X1 to X2. This is referred to as hairpinning. Source
Was just wondering why I seem to get different values for my IP address from different sources. If I go to one of the many different 'what's my ip' sites on the net I get a completely different value from when I use ipconfig (on win7)
And no, it's not the subnet mask I'm looking at, these are the actual ipv4 addresses, why would they be resolving to different addresses? Are these 'what's my IP' sites only able to hit an exchange and not determine the IPs of my actual box itself?
If your PC is on a network and not directly connected to your ISP via a modem, there will be at least one router between your machine and the internet. That router will almost certainly be doing NAT (Network Address Translation) and possibly DHCP (Dynamic Host Configuration Protocol) too.
The router will have been assigned an address by the ISP when it established the connection. This address might be static (unchanging) or, more commonly, dynamic (changes periodically as the ISP sees fit). So your 'public' address - the one the router has been assigned and which is visible to the internet - may change from time to time.
Your PC will be connected to the router, and will either have a fixed IP address assigned to it (typically in the 192.168.x.x range) through your OS networking config, or will be given one by the router each time it connects (when you switch on or reboot) via DHCP. In this case, the address will be in whatever range the DHCP service has been told to use (again, the default is likely to be in the 192.168.x.x range).
So your PC has its' own internal address, and your router has its' public address. When you exchange internet traffic, the machine at the other end of the connection will see your public address, not your internal address - the router takes care of forwarding data to the right internal address automatically.
Depending on what IP-checker service you're using, it might display your public address (from the router, which may change if the ISP assigns dynamic addresses) or your internal address (typically when a script runs inside the browser and asks the machine directly).
The answer won't clarify anything, but I'll tell you anyway.
They're both right.
No, your machine doesn't really have two IP addresses, but the IP it shows as depends on who's looking, and from where.
•
What you're seeing is the result of what's called a NAT router. NAT stands for "Network Address Translation". The router manages the IP addresses on a LAN, or Local Area Network, and then translates to the appropriate IP address it was assigned on the external network, usually the internet.
details