draytek 2860, help configuring a home hosted site...

Associate
Joined
22 Jun 2009
Posts
813
Location
Norwich
Hi, would much appreciate any pointers with a little issue I have configuring my router.
I suspect it's easy to solve but I'm being a bit thick at the moment...

Summary of the problem:
I need to correctly configure my DrayTek VigorLTE 2860Ln to allow hosting a webpage. I think the problem is the firewall is not allowing external traffic through.

Background:
I have a few useful little applications running on an ancient RPi (MK1) which is a LAMP server.
The Pi has a fixed IP address within my LAN.
I'd like to get Alexa to communicate with this server - and if I could get Alexa to directly send CURL data, eg POST or GET then I'd be happy.

As it stands I can only achieve this if I use Alexa -> IFTTT -> Webhooks. The problem is Webhooks needs a publically accessible URL.

Please flame me if there is simpler way to do this, but I decided host my RPi LAMP server on the open web. Since I have a Draytek router I can use a free, mini DNS service called DrayDDNS.

Current situation:
I have activated this mini DNS service, and got given a URL I can use, which then points all traffic to my home router. Of course being a DDNS service, it will automatically update my IP as it changes.
If I connect to this URL on a browser from within my LAN, no problems.

You can guess where this is going, this URL is inaccessible from outside my LAN (tried using 4G data connection, and a VPN service). Which makes me think the Draytek's firewall is simply blocking outside traffic -- alas, my attempts to create a fliter, or open a port have failed miserably :( :mad: :o

Here's a few screenshots of what I have done thus far:

Here I set up my freebie DDNS service.
So by clicking on http://164*********.drayddns.com/test.php it should direct traffic to my home IP address, and as this IP changes in the future DrayDDNS will auto-update.

4bVGfYL.jpg

A bit of tinkering is needed, simply specifying which LAN IP address to send traffic to:
(in this case, the blurred IP is my RPi, LAMP server).

SHdFxtl.jpg

These two simple steps are enough to get my RPi LAMP server on the www.
So if I connect to the URL using a browser, all checks out fine:

FsAoI8g.jpg

Of course, you cannot connect if you're outside my LAN.

The first thing I tried was port redirection. You can see below I specified a public port of 8888. It wouldn't let me use port 80. I don't mind having inbound traffic arrive on 8888, if this makes it slightly more secure.

V2tz5o2.jpg

However if I try:
http://164*********.drayddns.com/test.php
http://164*********.drayddns.com/test.php:8888

none of these work from outside the LAN.

I tried opening the ports:

bix977R.jpg

Again, no access from outside.

And finally, I changed the firewall filter (default data filter) to specifically allow incoming traffic to pass immediately. Also, no luck.

noDFjWq.jpg



Any ideas?
thanks
 
It won't be letting you use port 80 because it'll already be using it for something else (probably for the SSL VPN). There's nothing to stop you making it available if you want to.

What's with 'http://164*********.drayddns.com/test.php' having an IP address in it? I'd have expected http://somedomainname.drayddns.com.

To open the port either the 'Port Redirection' or 'OpenPorts' options should work, I don't think you need to use both. There shouldn't be any need to mess with much else such as the 'LAN DNS / DNS Forwarding' and 'Filters'.

Test using your WAN IP first. Once that's working worry about the DDNS.
 
Back
Top Bottom