NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Port Forwarding - communication outside of the rules
Can someone explain to me - the external communication (no asked) outside the rules of redirection to LAN network - the firewall does not work ? Port forwarding rules: 1 DMS B ...
Hang on, you have two port forwarding rules allowing ports 80 and 443 through.
5 Topfield 8080 8080 80 80 192.168.2.111
7 https 443 443 443 443 192.168.2.110And that's exactly what your latest logs show.
where exactly do I find these settings? Search UPnP settings in help is not successful ...
Sorry I am stupid ... yes UPnP is allowed - I ban it and refer result
Hi, UpnP is denied ani in records - a little better - also are at odds with routing rule.
Target port is ready but source port is bad. It are ping ? - answer for ping is denied ...
LAN access from remote] from 46.174.37.238:1795 to 192.168.2.110:443, Sunday, Jun 12,2016 19:57:54
[LAN access from remote] from 220.254.153.173:51422 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:48
[LAN access from remote] from 220.254.153.173:52885 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:48
[LAN access from remote] from 84.55.49.180:28947 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:37
[LAN access from remote] from 84.55.49.180:56721 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:37
[LAN access from remote] from 180.97.106.161:37269 to 192.168.2.110:21, Sunday, Jun 12,2016 19:53:53
[LAN access from remote] from 24.71.26.5:58073 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:28
[LAN access from remote] from 24.71.26.5:53881 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:28
[LAN access from remote] from 83.7.78.215:49586 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:16
[LAN access from remote] from 83.7.78.215:5061 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:16I overlooked your question about the source port. You are misunderstanding the way port forwarding works. Port forwarding never touches the source port for incoming traffic. A port forwarding rule has two behaviors:
- It opens an external port
- It, optionally, rewrites the destination port to a new value on the packet before forwarding it to the internal IP address.
Your port forwarding rules are not performing #2.
buchtik wrote:Hi, UpnP is denied ani in records - a little better - also are at odds with routing rule.
Target port is ready but source port is bad. It are ping ? - answer for ping is denied ...
LAN access from remote] from 46.174.37.238:1795 to 192.168.2.110:443, Sunday, Jun 12,2016 19:57:54
[LAN access from remote] from 220.254.153.173:51422 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:48
[LAN access from remote] from 220.254.153.173:52885 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:48
[LAN access from remote] from 84.55.49.180:28947 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:37
[LAN access from remote] from 84.55.49.180:56721 to 192.168.2.110:443, Sunday, Jun 12,2016 19:55:37
[LAN access from remote] from 180.97.106.161:37269 to 192.168.2.110:21, Sunday, Jun 12,2016 19:53:53
[LAN access from remote] from 24.71.26.5:58073 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:28
[LAN access from remote] from 24.71.26.5:53881 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:28
[LAN access from remote] from 83.7.78.215:49586 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:16
[LAN access from remote] from 83.7.78.215:5061 to 192.168.2.110:443, Sunday, Jun 12,2016 19:53:16