V4.32 NAT port 80 and 443 not allowed
This discussion was created from comments split from: V4.32 NAT port 80 and 443 not allowed
Description: For NAT port mapping setting, add a check box override or even a check how the GUI is being accessed (a smarter check) to know the user can still log in after the rule
Comments
-
Is this issue going to be addressed in a future firmware? I realize that I can change the Zywall web interface port but this is not desired since I do not care or want to access the Zywall web interface over the WAN interface.
0 -
This is pure stupidity. What you are saying here is that your customer running a WEB server cannot use your product without modifying the internal port of the Zywall GUI ????
And secondly basic security tells you that you NEVER EVER open any firewall services to the WAN! Why would Zywall then "consume" that port?
Fix it!
0 -
What I don't get is you can NAT port 22 without conflict! if you have SSH enabled! so why ports 443 and 80 but not 22? the user with one WAN IP should already understand that if you NAT ports 443 and 80 the Zywall GUI can only be accessed on the LAN side unless changed.
0 -
Same problem with ATP700 running 4.55.
Edit: Found a workaround. Create a Service-Group and add http and/or https. Select the service group instead of the the service when you create a nat rule. The GUI doesn't check for port conflicts within service-groups.1
Categories
- All Categories
- 347 Beta Program
- 2.1K Nebula
- 114 Nebula Ideas
- 77 Nebula Status and Incidents
- 5K Security
- 44 USG FLEX H Series
- 246 Security Ideas
- 1.2K Switch
- 65 Switch Ideas
- 901 WirelessLAN
- 33 WLAN Ideas
- 5.8K Consumer Product
- 204 Service & License
- 326 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 1.8K FAQ
- 831 Nebula FAQ
- 401 Security FAQ
- 219 Switch FAQ
- 190 WirelessLAN FAQ
- 45 Consumer Product FAQ
- 136 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 71 About Community
- 61 Security Highlight