Show Posts
1
16.7 Legacy Series / Re: TLS Web interface access.
« on: January 03, 2017, 10:05:30 am »
Perfect Thank you! We totally missed that config section, sorry!
Ok, got it working under https, but then again we got confused about what you said: how comes the anti-lockout is enough? As far as we can see (it's in the attacment of my first post) it opens just port 80, is it also taking care of port 443 under the hood?
However, next step was to NAT a port for remote access to the web GUI (password is strong, connection is encrypted and IPs are controlled, so no worries) but we got dns rebind attack protection alert. We know what it is and we don't need this protection, how can we get rid of the alert to access with domain name from wan?
Or is there a better way than NATting the access?
Nevermind, I found out:
I just filled the input "Alternate hostnames" under System -> Settings -> Administration with the domain name(s) we'll be using to access this firewall.
Still I'd like to know why the anti-lockout rule which is specified for port 80 works also for port 443...
Ok, got it working under https, but then again we got confused about what you said: how comes the anti-lockout is enough? As far as we can see (it's in the attacment of my first post) it opens just port 80, is it also taking care of port 443 under the hood?
However, next step was to NAT a port for remote access to the web GUI (password is strong, connection is encrypted and IPs are controlled, so no worries) but we got dns rebind attack protection alert. We know what it is and we don't need this protection, how can we get rid of the alert to access with domain name from wan?
Or is there a better way than NATting the access?
Nevermind, I found out:
I just filled the input "Alternate hostnames" under System -> Settings -> Administration with the domain name(s) we'll be using to access this firewall.
Still I'd like to know why the anti-lockout rule which is specified for port 80 works also for port 443...