Closed GoogleCodeExporter closed 9 years ago
Upd: start up new httpd on port 8008, create virtual server for incoming port
8008 and forwarded it to 192.168.1.1 (router ip) on port 8008. But I can not
access my http server on 8008 port from WAN. From LAN it works perfectly well.
Original comment by myandr...@gmail.com
on 13 Oct 2011 at 10:27
it's obviously wrong setup.
set "Port of Web Access from WAN" to 8008 and everything will be fine without
any need for manual starting, vserver rules adding etc.
Original comment by themiron.ru
on 13 Oct 2011 at 11:10
As I wrote originally I set up "Port of Web Access from WAN" to 8081, but admin
page was unavailable.
Additional information with httpd and forwarded port is only another example
that port forwarding doesn't work.
Original comment by myandr...@gmail.com
on 13 Oct 2011 at 11:32
Despite issue is invalid could you suggest what can I do to make port
forwarding work? I changed WAN Access port back to 8080 through Admin page
yesterday from home. But now I can not connect to admin page from work
(although I managed to do this previously).
Original comment by myandr...@gmail.com
on 13 Oct 2011 at 12:11
please provide iptables -nvL, iptables -t nat -nvL output
p.s you can hide last octets of wan ip address in ip4.ip4.xxx.xxx form
Original comment by themiron.ru
on 13 Oct 2011 at 12:12
Original comment by themiron.ru
on 13 Oct 2011 at 12:12
Attached files with output
Original comment by myandr...@gmail.com
on 13 Oct 2011 at 12:30
Attachments:
find "tcp dpt:8080 to:192.168.1.1:80" in your iptables -t -nvL output.
it means you've set access port to 8080, just tried to open your wan
address:8080 and it worked.
so, it's really invalid issue. please confirm
Original comment by themiron.ru
on 13 Oct 2011 at 1:38
I'm able to open admin page now.
but address:8008 still is not working although "tcp dpt:8008
to:192.168.1.1:8008" presents in iptables -t nat -nvL (it was configured using
admin page > Virtual Server).
ok, this seems to be misconfiguration of virtual server. Close the issue
Original comment by myandr...@gmail.com
on 13 Oct 2011 at 2:13
[deleted comment]
> address:8008 still is not working although "tcp dpt:8008 to:192.168.1.1:8008"
yes, it will not, but to:192.168.1.1:80 will.
as I said before, it's obviously wrong setup.
Original comment by themiron.ru
on 13 Oct 2011 at 2:35
Original issue reported on code.google.com by
myandr...@gmail.com
on 10 Oct 2011 at 10:00