Setting up a Web Server with BSNL AONT 100C Modem & TP Link Router

  • Thread starter Thread starter newbie2902
  • Start date Start date
  • Replies Replies 49
  • Views Views 18,250
Messages
28
Location
NA
ISP
BSNL
Good Morning everybody; this forum seems to be having a lot of information on networking in India. Great place for knowledge sharing and thank you members for making this forum such a wonderful & useful place.

We have an FTTH connection from BSNL and they have placed an Alphion AONT-100C modem. Since this modem doesn't have wifi feature, we have added a TP-Link router and connected many computers through wifi. Everything was fine until now when we want to use one of the computer in the network as a web server which has to be made accessible from public. Looked out for many tutorials online and tried our best with no success. So, please help with our situation.

EXISTING SETUP:
Modem: Alphion AONT-100C
LAN IP: 192.168.1.251
WAN IP: Dynamic
Connection Type: PPPoE
DHCP: Enabled

Router: TP-Link
LAN IP: 192.168.0.1
WAN IP: 192.168.1.127 (Dynamic)
Connection type: Wireless router
Connection in: LAN cable through WAN port from AONT modem
Connection out: Wifi and LAN ports

Web server machine: HP Workstation
LAN IP: 192.168.0.105
Listening to port: 80
Allow access: all

We tried two methods:
METHOD-1
Enabled DMZ (firewall settings) in BSNL modem with host 192.168.0.1 (TP-Link router) and port forwarded to 192.168.0.105 in the TP-Link router. Incoming public traffic is routed to BSNL modem admin page.

METHOD-2
Made the TP-Link router as an Access Point with IP 192.168.1.1 and assigned web server machine with IP 192.168.1.105, both having gateway as 192.168.1.251 which is the BSNL modem. Enabled port forwarding in BSNL modem to point to 192.168.1.105 (80 port). Incoming traffic is still routed to BSNL modem admin page.

We also tried with some different ports instead of 80, which didn't work either. Please help.
 
With your existing double nat config, you need to port forward on Alphion to 192.168.1.127 not 192.168.0.1 Or set up 192.168.1.127 as DMZ on Alphion, better to use static ip on the TP-Link wan side for this. Then port forward on tplink to 192.168.0.105.
We updated LAN IP of TP-Link router to static at 192.168.1.127 and activated DMZ on Alphion modem with host 192.168.1.127. Enabled port forwarding in the TP-Link router pointing to 192.168.0.105 which is the HP Workstation. Rebooted both devices and tried to access through WAN IP of the Alphion. It doesn't forward to the local server. Is it right that we are trying to access the WAN IP of the Alphion from the web or is there some other way to do this? Please suggest.
 
Upvote 0
If everything works as intended, then you should be able to hit the WAN IP address and reach your HP Workstation.

Right now, when you hit the WAN IP address from a different network (say mobile internet) what do you get? Also which all ports are being forwarded from the TP-Link to the HP Workstation?
 
Upvote 0
This is off topic, but what kind of web application do you plan to run on this web server? Is it resource hungry? Is it something that can be hosted on a cloud VM for example? Any particular reason as to why this needs to run from your home/office?
 
Upvote 0
When we try to access the WAN IP of Alphion from other ISP, it fails with the following message:
This site can't be reached

[IP ADDRESS} took too long to respond.

Try:
Checking the connection

ERR_CONNECTION_TIMED_OUT

Have forwarded port 8080 from TP-Link router to HP Workstation. We can access the Workstation using the WAN & LAN IP of TP-Link with port 8080. We also can access directly with the Workstation LAN IP. However, unable to reach through Alphion WAN IP.

Out of curiosity, used some online tool and checked which ports are open for the WAN IP of Alphion and the result said none of the ports are open.

Regarding the application we intend to run, it is just a staging server to clone database from the live server. The live server is on cloud and we intend to dump only a part of the cloud database to our local machine.
 
Upvote 0
Regarding the application we intend to run, it is just a staging server to clone database from the live server. The live server is on cloud and we intend to dump only a part of the cloud database to our local machine.

Is it then something that needs to be accessible from the public internet? I mean if you just need to remotely connect to the live server and dump a database, the client server ie your HP Workstation doesn't need to be publicly accessible right?

Also, if only certain users need to access this HP Workstation from the internet, you could look at deploying something like ZeroTier, it is absolutely zero config and just works. You'd either need the ZeroTier client on all devices or at least on the gateway device for a network.

 
Upvote 0
^ Yes you get something like a xPON ONU on a stick which comes as a SFP module. But its basically just a xPON ONT in that form factor. Anyway that doesn't seem related to this issue though. ;)
 
Upvote 0
Is it then something that needs to be accessible from the public internet? I mean if you just need to remotely connect to the live server and dump a database, the client server ie your HP Workstation doesn't need to be publicly accessible right?
Actually it is the other way round. We don't connect to the cloud server. Instead, a scheduler will be accessing our local machine and dump data. Access to the local machine should be given to two external IPs; one which dumps the data and the other which pulls the data.

We do have other FTTH connections with static IP from BSNL. Those WAN IPs are also not accessible from internet.
 
Upvote 0
Back