I'm from Chennai and using static IP allocation from ACT - but it's a bizarre setup, so allow me to explain:
For some reason, they're NATing the private IP allocation given to you, with a public IP address. For instance, that 10.x.x.x IP address given to you is attached to a particular public IP address. The only difference here, is the allocation does not 'end' at your router level like it should. Instead, your router is setup with the static private IP address (10.x.x.x) whereas it translates to the public IP in the backend of ACT.
In my case, I wanted them to give me an actual public IP, not this NAT crap - nevertheless, it still works as expected, just not explained properly by them in the first place.
In your case, I assume your apache server is behind a router, so you should be binding the local IP address that's allocated from your router to the apache box - not the static that's supposed to be setup in your router, nor the actual public IP that's displayed on whatever site you check.
So the setup should look like this :
Router (with a static WAN on 10.x.x.x) --> Port Forward (assume you want port 80) --> Apache server (bind to local IP given by the router, ex 192.x.x.x)
If you visit the public IP address (ex to check from whatismyip.com) directly from another connection, your apache server should respond. Likewise, pings will respond, as long as your router is setup to reply back and not just block. Some routers won't reply ICMP pings unless specifically configured to do so.
Static IP from ACT means getting a static 10.x.x.x IP address, which will translate to a public IP address - this does not change, so technically it is still static except it's setup this way.
They implement Double NAT-ing to solve the problem. They make the required changes at their end and walk you through the changes to be made in your router. With that you pretty much get a static WAN IP.
Client router end changes:
PPPoE settings will be changed to static ip. No portal login required.
They provide you their DNS settings that you can discard, if you want to use Google or other 3rd party DNS.
You may not require DDNS going forward. But if you still need it, you can directly assign your public IP to the DDNS. If you still want the router to register, then your router should be capable of registering 'NATed Public IP' with your DDNS provider.
As expected, ping slows down considerably.
Okay time to share my experience. I'm in Bangalore for reference.
Firstly this will only solve the double NAT issue that comes along with giving people private IP addresses instead of public ones. I apologise if this is not what you're looking for but I believe it is better than using a VPN because I've never gotten above 20MBps with one.
To Fix Port Forwarding:
- Call CC and tell them you would like to speak to an engineer. Wait for the callback.
- Tell the engineer that you need open ports because you use game servers so you would like a static private IP (not public IP).
- He should disable PPPoE on your account and tell you to setup your router WAN for a static IP like the following: https://puu.sh/jZG00/4aa9360697.png
- If he bullshits around just tell him to look at the configuration for account # 10455273
- There, you should now be able to port forward.
Now you might notice that most public trackers will not give you a proper peer response after doing this. This is largely because ACT is now intercepting tracker responses over ports 80 and 81 to make you use more local peers (P4P), whether this happens outside Bangalore or not I will still post the fix.
To Fix Tracker Responses:
Done, you should be able to torrent just fine now.
- Get a SOCKS5 proxy subscription (or whatever). I use PIA.
- In uTorrent or basically any other torrenting client enable the proxy only for hostname lookups/tracker lookups. What this means is that the client will only use the proxy to query trackers. All other connections will be done over your normal connection (full speed) and that's the IP that will be reported to the seeds/peers.
- It looks like this in uTorrent 2.2.1: http://puu.sh/jZGBz/9aabfdb248.png
I am experiencing the same thing. However, that's only on first load. Refresh the page as soon as it loads and the video will stream at expected speeds. I believe ACT is using some inefficient version of caching.
I am ACT customer from Bangalore, and interested to know the drawbacks of the ACT's double NAT setup for Static IP & Port Forwarding. My primary tasks on internet are:
- Gaming (Dota 2)
- WebDev / Networks
- Does Bangalore have the same Double-NAT setup for Static IPs & Port Forwarding?
- IF yes, how much latency does that add to the current system? Also, how much harm does it cause to the general downloading and stuff?
- Should I rather use my remote server (DigitalOcean/Vultr) as VPN and connect to my system via it, when I want access to the local system, and disconnect the VPN when I don't? (Neglecting the price aspect)