Skip to main content

Creating own Hosting Space

Requirement: A Computer connected to DSL  modem and access rights to DSL Modem's admin interface.
In this setup, if I connect to a website, the request reaches the Modem. All systems behind modem will have private ips(say 192.168.x.x). The modem performs a NAT and sends the request to the ISP's upstream router. The modem will have a different ip on ISP's upstream subnet. So it puts its IP and some port translation so that it can map to same computer.
A very very rough sketch at http://drawit.eskratch.com/fetch?q=464041803 where A and B are clients who send requests to web servers on port number 8140 and 8141. Modem m receives them and translates req to m:80 and m:81 respectively and sends to the ISP modem.The ISP modem associates a public IP pub to the modem m and sends the request to webserver. On return the packet reaches ISP who based on IPmapping sends the data to modem m. The modem m based on port mapping, send the data to corresponding computer.
Now my requirement is I will place a web server in any one of the computers and it should be reachable globally.
Steps:

  1. Open the modem's Admin interface(this is possible only in a home setup). Admin interface is in standard ip for each manufacturer. 
  2. Select Port Forwardng
  3. Enter your ip(ifconfig) and port number(say 8080) where webserver is hosted
  4. Start web server
  5. Do a crawl ifconfig.me or visit http://ifconfig.me , this will give your pub ip of ISP
  6. Now type pubip:port (port mentioned in port forwarding) in the address bar of any browser. This should lead to your site.
How it works?
when somebody enters pub:port, the request reaches the ISP who maps to modem using IP, the modem forward the data on port to required system as we have configured to do so.

But the mapping between the modem and ISP is dynamic, they may assign a diff public IP from their pool at different point of time. There are third party like http://www.no-ip.com/ who solves this issue
No-ip allows us to select a domain name(dn.no-ip.org). It periodically checks our system's public ip and maps it to dn.no-ip.org. 

My local apache webserver is accessible in public (provided my lap is on and Iam in my home network) at http://apache4.no-ip.org:8080/

Comments

Post a Comment

Popular posts from this blog

How we have systematically improved the roads our packets travel to help data imports and exports flourish

This blog post is an account of how we have toiled over the years to improve the throughput of our interDC tunnels. I joined this company around 2012. We were scaling aggressively then. We quickly expanded to 4 DCs with a mixture of AWS and colocation. Our primary DC is connected to all these new DCs via IPSEC tunnels established from SRX. The SRX model we had, had an IPSEC throughput of 350Mbps. Around December 2015 we saturated the SRX. Buying SRX was an option on the table. Buying one with 2Gbps throughput would have cut the story short. The tech team didn't see it happening. I don't have an answer to the question, "Is it worth spending time in solving a problem if a solution is already available out of box?" This project helped us in improving our critical thinking and in experiencing the theoretical network fundamentals on live traffic, but also caused us quite a bit of fatigue due to management overhead. Cutting short the philosophy, lets jump to the story.
8 comments
Read more

LXC and Host Crashes

 We had set up a bunch of lxc containers on two servers each with 16 core CPUs and 64 GB RAM(for reliability and loadbalancing). Both the servers are on same vlan. The servers need to have atleast one of their network interface in promiscuous mode so that it forwards all packets on vlan to the bridge( http://blogs.eskratch.com/2012/10/create-your-own-vms-i.html ) which takes care of the routing to containers. If the packets are not addressed to the containers, the bridge drops the packet. Having this setup, we moved all our platform maintenance services to these containers. They are fault tolerant as we used two host machines where each host machine has a replica of the containers on the other. The probability to crash for both the servers at the same time due to some hardware/software failure is less. But to my surprise both the servers are crashing exactly the same time with a mean life time 20 days. We had to wake up late nights(early mornings) to fix stuffs that gone down The
Post a Comment
Read more

The FB outage

 This outage has caused considerable noise everywhere. It was quite discomforting for me because during the whole conversation nobody bothered to understand the gravity of the issue. I don't expect end users to understand the issue. But this is going to be a blogpost for all of those in the tech field, Such an event can happen how much ever chaos engineering, best of the tech jargon we implement in the stack To all my Site Reliability Engineer friends, Site Up is our first priority. I myself said many a times outage is news and SREs should prevent outage. But I'm afraid this is leading to a cult in the industry who despises outages and takes no learnings from it. I don't know what has happened in Facebook. I can explain a scenario which may or may not be right but that can definitely show the gravity of the issue. Let's draw a probable Facebook architecture Disclaimer I don't work at Facebook. So this might not be how facebook routes traffic. This is based on my exp
2 comments
Read more