TW-EAV510 modem exposes admin interface publically - router

I have a ADSL/VDSL modem, model TW-EAV510 ADSL2+/VDSL2 WLAN Router. The firmware version I am running is 5.00.59g-1.
I noticed that the modem is exposing the admin web interface on port 80 via my public IP address. This wasn't a major problem, because I have a pretty strong password, but I'd like to disable this so that the admin interface is only accessible within my local network.
I'm now hosting a website, so I forwarded port 80 to my server. When I set up the port forwarding, the modem automatically mapped the public admin interface to port 8080 (and informed me in an alert box). I have a domain name pointing to my IP, so the admin interface can be accessed through mydomain.com:8080
I've read all the manuals and docs, and combed through every setting in the web interface, but couldn't find any option to disable public accessibility.
Anyone else run into this problem, or know how to fix it?

I spoke with a very informative tech support rep from the manufacturer of the modem, and he informed me that I have nothing to worry about. I was accessing my admin interface with my public IP address while I was within my network, so there was an internal loopback which took me to there. If I had tried to access the admin interface from outside the network with my public IP, it would not have show me anything, because there loopback would not happen.

Related

Is it possible to run web server on private IP?

I'm trying to implement a web server on my pc, connected to router.
Since my PC is connected to router, It identifies private IP address, starting with
192.168...
However,it could not accept any clients that is not connected to the same router, even I specified tried with public IP address.
Is it possible to implement Web server that can be accept clients from anywhere with my PC connected to local router?
Or should I connect my web server directly to public IP directly without router?
It'll be pleasure to learn from your answers.
The problem may be, that your web server routing may not be configured correctly to your external IP, or your web server ports may be blocked, or another possibility is that your firewall is blocking your service connections outside the local network.
So, a solution to misconfiguration would be, to forward your port to your internal IP of the web server from your router menu.
And, for the case of firewall blocking, you may give special access to your web server through the firewall by setting inbound and outbound rules.
And if all that is correct then most probably your ISP(Internet Service Provider) is not allowing ports to be opened to you, maybe due to dynamic IP or service restrictions.
For the similar problem, you may refer to my answer to another post Here
What router do you have? go into the router using a web browser, mine is 192.168.0.1 with username and password as admin. or username admin, password blank.
Then set a dmz route or for port forwarding 80 to you own internal IP address.

How to access REST APIs hosted locally on Alexa

I am developing a custom Alexa Skill and have a requirement where I want Alexa to access REST APIs that are hosted locally on http://localhost:8080? Any idea how to do this?
Thanks!
If you really want to do this, and I’m assuming you are hosting the skill on AWS Lambda, it would involve quite a bit of work.
Your local endpoints need to be accessible from outside of your network, which requires port forwarding in your router to your machine where the endpoints are hosted. This needs to be configured in your router.
An easier way is to deploy your project containing the API to something like Heroku, which can be done easily. They give you a domain and make the endpoints accessible to Lambda. This should be possible within their free tier.
Here' a link to a pretty good article about how IP addresses work.
Allowing a device sitting on your local network (eg. a laptop computer or Raspberry Pi connected to your wifi) to be accessed from outside your local network (eg. from a service running on AWS) will involve mapping 2 separate IP addresses:
The IP address assigned to your router (your public IP)
The private IP addresses assigned by your router to your devices (laptop, iPhone, RPi, etc).
You have a couple options for allowing your router's IP (#1) to be accessible from outside your local network:
a. Pay your internet provider to provide you with a static IP address
b. Use a dynamic DNS service such as DuckDNS or No-IP.
Once you have a fixed public IP that can be used to access your router, you will then need to map a port on your router (#1) to the device IP on your local network (#2). This is usually referred to as "port forwarding". Most routers will support configuring this. In effect, your tell your router "when you get a message to : pass it to my laptop :"
Your local private IP address will typically have an IP value like 192.168.0.23 (where the 23 can be anything from 1 to 254).
An outside IP will start with something other than 192. Refer to the first link above regarding IP ranges.
You can google "port forwarding" and "public IP" for more info on how IP addresses and port forwarding work, but hopefully this will help get you started. It may seem a bit complicated at first, but if I can understand it, then anyone can :-)

D-link Modem & Linksys Router Wrtg54

I have recently brought a static ip address from my isp and i have a old computer to which i want to make my website live on internet i have read couple of forums and done research from it and nowhere i am to follow that.
I have a D-link modem and linksys router wrtg54 my isp have set up the static ip on d-link modem now i am confused what to do with the static ip as per my research many static ip are written on networks ip address,subnet,gateway and dns. I dont know how to set this up.
I had setup a static ip on my server computer which is 192.168.192.103 now i dont know what to do.Just for your refrence my Linksys router is configured on DHCP network.
I would really appreciate if someone can guide me or help me with a name who can setup this network thing so i can find the help for this problem.
Just to clarify, having a static IP does not resolve all the points for setting up a website, open to the public.
Consider the following points:
Do you have a webserver running on your computer?
(see www[.]apachefriends.org/de/index.html for windows or help[.]ubuntu.com/lts/serverguide/httpd.html for Ubuntu)
Does your ISP allow access on port 80?
(this would change to 443 if you use https)
Set the port forwarding on your router to the local machine
(http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/HTTP.htm for more info)
Get a domain (www.example.com) for your website
(If you registered already a domain, you have to change the target IP to your fixed IP which you received from your ISP)
Try to work this through and don't stop asking!

Letting remote desktops access localhost's web service

I can access my computer's (localhost) web service using eclipse mars and jax-ws. However, I'm just curious, how can I make it so that other remote computers that is not connected by LAN?
Any advice, direction, or what I should research is welcomed.
Your computer is invisible to internet. It will connect to internet
via a router (ADLS modern for en example).
Your router is visible on Internet and with a public IP Address, you
can try some website to see what its address is (for example
http://whatismyipaddress.com/)
You need to config your router to make it forward the request from internet
to you computer LAN address and your web-service port, the way to
config port forwarding is depend on your router.

Turning PC Into A Server

Sorry if I have this in the wrong community but I'm hoping one of you can help me out anyway.
I have a web hosting account with a UK company who I'm happy with, but I'd like to set up a little hosting account from my laptop, just to see if it's possible and easy enough to do really.
Trouble is I've been doing a lot of research online but coming up empty whenit comes to more of a "complete guide". Do any of you know of a good resource for setting up a home server for publishing "Live" websites with custom TLD domain names? I have a localhost server running and files hosted on there but I'm really looking for help with the IP and DNS parts for the custom domains.
For reference, I have a machine running Win7, Appserv 2.5.10, UK broadband and a .co.uk domain name registered with 123-reg.
Any help would be hugely appreciated.
You'll need to:
Point your domain to your laptop.
If you get static public IP address from your ISP, then you can just point the A record to this IP address.
Where do I set this A record? Almost all domain registrars give you a nameserver for free. You point your domain to their nameservers (generally ns1.somedomain.com and ns2.samedomain.com etc.). In the nameserver config, create a A (stands for authoritative) record and put in your static IP address.
What if my ISP doesn't give me an static IP address? This is where services like dyndns come into picture. They give you an agent that you'll install on your laptop, it detects the change in IP address and automatically updates the Nameservers accordingly. There are some free variants of dyndns as well if you don't want to spend money on this.
But my laptops IP address is something like 192.168.x.x and my site runs on localhost (127.0.0.1)? Your laptop is most likely NATed. Think about your public IP address to be that of your router. You will need to forward any connection coming to your router on port 80 or 443 to your laptop's (192.168.x.x) corresponding ports. This is called Port-Forwarding and all routers support this. Port-Forwarding is done by logging on to the admin interface of your router (Many times its at http://192.168.0.1 or http://192.168.1.1).
But again my application is accessible at localhost? You need to make sure your apache/nginx listens on 0.0.0.0 or atleast 192.168.x.x interface. This is how computers outside your laptop will be able to make connection to your laptop on port 80/443.