bottleneck
Choose style:

Author Topic: Forwarding port 80  (Read 6521 times)

0 Members and 1 Guest are viewing this topic.

Offline the_unlord

  • Backer
  • *
  • Posts: 6
  • Thanks: 0
  • Registered : 29/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Forwarding port 80
« on: December 01, 2014, 08:34:25 am »
I'm running a VPN server on my NAS that I'd like to access from the internet on port 80 (I'm frequently on extremely paranoid networks that block all outgoing traffic except ports 80 and 443).
However, the web interface of the Almond+ is also running on port 80, and as soon as I try to forward it, I can no longer access the internet from the LAN (maybe HTTPS and all other ports still work, haven't checked that).

Maybe this is because the router web interface is listening on port 80 on all interfaces (I have disabled accessing the web interface from the WAN side, so listening on LAN interfaces would be enough), and the firewall blocks it from WAN side if in my case, or maybe there is a rule specifying that all port 80 traffic for any router IP is not the be forwarded, but sent to the router itself.

How should I go about fixing this? Is is easy to just run the web interface on another port (88 for instance)? I haven't worked with iptables and openWRT before...

Offline Fire69

  • Backer
  • *
  • Posts: 344
  • Thanks: 0
  • Registered : 03/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Forwarding port 80
« Reply #1 on: December 01, 2014, 05:50:14 pm »

Offline the_unlord

  • Backer
  • *
  • Posts: 6
  • Thanks: 0
  • Registered : 29/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Forwarding port 80
« Reply #2 on: December 04, 2014, 08:10:57 am »
Thanks!

server.bind="192.168.1.1"
in the lighttpd config file did it!

I still needed to reboot once I added the forwarding rule, as routing was broken (see my other thread), but after a reboot it all seems to work now!

 

Page created in 0.036 seconds with 18 queries.

bottleneck