Closed GoogleCodeExporter closed 8 years ago
Update:
If you go into WAN settings and set SOFTWARE NAT to DEFAULT NAT instead of FAST
NAT the issue seems to go away even in most current version. Leave it FAST NAT
and no inbound port 80. What's weird is all other inbound ports work fine just
port 80 affected.
Original comment by ispg...@gmail.com
on 26 Mar 2012 at 12:46
Hello,
Where do you forward traffic from this port? (to router itself or another local
host?)
What do you mean by 'not forwarding properly'?
Original comment by d...@soulblader.com
on 26 Mar 2012 at 8:17
To another local host... in this case 192.168.1.223. It with the settings as I
described above inbound port 80 traffic (from the WAN) is not being passed to
the local IP. If you downrev several versions it works just fine or if you
turn off Fast Software NAT it works fine.
Original comment by ispg...@gmail.com
on 26 Mar 2012 at 4:55
Do not confirm this! Right now, I've forwarded traffic to my desktop on port
80.
I can see my phpinfo() )) via http://kproxy.com/
Both hardware nat and software nat (Fast NAT) are switched on.
What type of traffic are you trying to forward (ordinary webpage content, maybe
some media streaming, or smth. else?)
Original comment by d...@soulblader.com
on 26 Mar 2012 at 5:34
It's just accessing a webserver. If I access it by http://192.168.1.223 on the
internal net works fine. If I leave SOFTWARE FAST NAT turned OFF it works fine
if I turn it on it stops works working. Previous versions of the firmware not
only didn't have this option but did not exhibit the symptoms. I have been
using this router for some time now with this exact configuration no
problems...only started with the latest firmware.
Original comment by ispg...@gmail.com
on 26 Mar 2012 at 5:56
What is your connection type to the internet?
Original comment by d...@soulblader.com
on 26 Mar 2012 at 6:19
I tried this (I have a web server too) and I confirm the issue: I set Hardware
NAT to Very Fast and Software NAT to Fast NAT - the web server cannot be
reached anymore. It works if I set Software NAT to Default NAT. I have Static
IP and port 80 forwarded: WAN:80->MyWebServer:80. Right now I cannot downgrade
the firmware to check if this is present on the previous version(s).
Original comment by bluesurv...@gmail.com
on 26 Mar 2012 at 7:07
Forgot to add one more thing, my web server is winServer2008 with IIS7 and the
pages are ASPX (ordinary webpage content some with Flash).
Original comment by bluesurv...@gmail.com
on 26 Mar 2012 at 7:16
[deleted comment]
2 ispgeek: Is your server running on Windows too?.. =)
Original comment by d...@soulblader.com
on 26 Mar 2012 at 7:28
Nope my server is linux based but I am glad you can confirm :)
Original comment by ispg...@gmail.com
on 26 Mar 2012 at 10:06
And what is the connection type? I'm on DHCP, that's why I think I don't have
such problem...
First, please check:
# cat /proc/sys/net/ipv4/ip_forward
if traffic can be forwarded. It should be '1'.
Then, check iptables rules (iptables -vnL) to see it is really forwarded.
If the first two are fine and you can see in netstat -tpln that is listening.
Could you please try to start the server on other port. Let's say on 8080 and
forward traffic from port 80 on router to local machine on 8080. Will there be
such problem?
Original comment by d...@soulblader.com
on 27 Mar 2012 at 1:39
Anyway there is no sense to fix it now. It hope this issue will be fixed in new
builds with another kernel version. (see the first page)
Original comment by d...@soulblader.com
on 27 Mar 2012 at 1:48
It has not been fixed in the latest versions of firmware :(
Original comment by ispg...@gmail.com
on 27 Apr 2012 at 3:29
[deleted comment]
I can confirm the port 80 problem with this router ( latest firmware ).
Here is what I do :
1. Use port 80 for my webserver. Try to access the server from the internet.
Check the webserver log and see that the request reaches the webserver, but the
ip address of the requesting system has been changed ! As a result, the request
will time-out.
2. Use port 8080 ( or any other port ) and all is fine.
3. Change the router and the problem disappears.
Original comment by wolfgang...@gmail.com
on 3 Aug 2012 at 8:26
Just to add :
In case 1 above the router changes the IP address of the requesting system
always to : 80.239.106.206.
No idea where these numbers are taken from.
Original comment by wolfgang...@gmail.com
on 3 Aug 2012 at 8:35
[deleted comment]
Also confirm this issue ( latest firmware ~ 1.1.2.3-009)
It affects only port 80, if i use any other port - i can access my virtual
server from Internet.
also, in my case - WAN admin access won't work.
Original comment by just.0...@gmail.com
on 26 Aug 2012 at 9:23
Original comment by andy.pad...@gmail.com
on 10 Dec 2012 at 1:10
Original issue reported on code.google.com by
ispg...@gmail.com
on 26 Mar 2012 at 12:29