Messages

1

17.7 Legacy Series / HTTPS no redirection to the captive portal

« on: December 22, 2017, 03:31:53 pm »

Hello !

My problem is simple to understand but difficult to handle. I set up a captive portal and choose HTTPS to get its traffic on my portal but it only works with HTTP.

I have rode several posts about it but some are old so my question is : Can I make the captive portal redirect correctly?

When I type http, or IP it redirects to the captive portal (test with 8.8.8.8 among others). But when it's https, I'm okay if it doesn't allow the certificate, etc. but is it possible to get at least the certificate error ?
And the user could go on.

2

Web Proxy Filtering and Caching / Re: GUI : Transparent proxies (both http/https) make GIU unreachable

« on: December 22, 2017, 01:25:39 pm »

To make the connection with dev reply on Github :

easiest steps to reconfigure your box, with a factory reset is to flush all firewall related configurations, go to the gui and then reapply settings when done.

Code: [Select]

ipfw flush
pfctl -d
Then configure your firewall, next your captive portal....

3

Web Proxy Filtering and Caching / GUI : Transparent proxies (both http/https) make GIU unreachable

« on: December 22, 2017, 11:29:37 am »

Hello everyone

In my training project, I need to set up a captive portal connected to a wireless access point. The last one distributes DHCP on the LAN interface. I have two network cards not three as suggested in documentation tutorial ; it's not possible so I tried on two cards configuration.

I have an issue on the captive portal, more precisely on the web GUI. Actually I tried to add http and https transparent proxies on it which is on the LAN network card.
However when I did this, it was on the LAN interface (web GUI and guestnetwork are on this interface) and now I can't get access on the GUI. It makes sense, this is what the transparent proxies should do.

Of course I'm stuck now.. I tried to undo the LAN interface on my server but it appears the configuration is still the same.
N.B. The captive portal still work on the LAN interface

LAN is : 10.100.70.0
WAN is : 10.100.71.0
and the Web GUI is on 10.100.70.254

EDIT: I tried this on account of HTTPS certificate issue when clients need to log on but the browser shows certificate error.