Netgate Store

Author Topic: Portal cautivo redirecciona solo en HTTP y no en HTTPS ayuda por favor  (Read 462 times)

0 Members and 1 Guest are viewing this topic.

Offline AdrianCuba

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
El Portal cautivo redirecciona en  HTTP o sea yo pongo una pagina en HTTP y redirecciona al portal cautivo sin problemas el problema es que cuando pongo una HTTPS no redirecciona no se que pasa saludos. 
« Last Edit: April 15, 2017, 03:01:56 pm by AdrianCuba »


Offline jose1

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Portal cautivo redirecciona solo en HTTP y no en HTTPS ayuda por favor
« Reply #2 on: January 22, 2018, 11:30:26 am »
El Portal cautivo redirecciona en  HTTP o sea yo pongo una pagina en HTTP y redirecciona al portal cautivo sin problemas el problema es que cuando pongo una HTTPS no redirecciona no se que pasa saludos.


ya encontraste alguna solucion, tengo ese problema pero no encuentro solucion

Offline arnoldo0945

  • Jr. Member
  • **
  • Posts: 54
  • Karma: +5/-0
    • View Profile
Re: Portal cautivo redirecciona solo en HTTP y no en HTTPS ayuda por favor
« Reply #3 on: January 22, 2018, 05:02:25 pm »
???  Leiste el Link, a la Documentacion Oficial, que dejaron en el post anterior al tuyo ?

Quote

Captive portal not redirecting


If clients are not being redirected to the portal page when attempting to browse on an interface with captive portal enabled, it's most always one of the following causes.


1. DNS resolution not functioning - the clients on the captive portal interface must either be using the DNS forwarder on pfSense, on the IP of the interface where the client resides (which is the default configuration), or if using some other IP for DNS, it must be an allowed IP entry. If DNS fails, the browser never issues the HTTP request, hence it cannot be intercepted and redirected.


2. Firewall rules on the captive portal interface do not allow the initial HTTP request - if the user is trying to browse to google.com, but HTTP connections are not allowed to google.com, the HTTP request will be blocked and hence cannot be redirected. Under Firewall > Rules, on the interface where captive portal is enabled, the traffic to be redirected must be allowed to pass. This is most commonly HTTP to any destination.


3. The client has an HTTPS home page - The request must be to an HTTP site in order for the portal to redirect the client