Patch from Nick Buraglio

Is there any reason, other than maybe the ssl certificate error that it would cause, that https isn't redirected to the portal by default?  I just noticed that this isn't default behavior.  It's a feature that I thought would be somewhat handy and I think only would take a simple ipfw change.

1 files changed, 13 insertions, 3 deletions

diff --git a/etc/inc/captiveportal.inc b/etc/inc/captiveportal.inc
index 17b123b..d8f44a5 100644
--- a/etc/inc/captiveportal.inc
+++ b/etc/inc/captiveportal.inc
@@ -362,10 +362,20 @@ EOD;
 
 # redirect non-authenticated clients to captive portal
 add 19900 set 1 fwd 127.0.0.1,8000 tcp from any to any 80 in
+
+# --- for redir ssl
+# redirect non-authenticated clients to captive portal on ssl
+add 19901 set 1 fwd 127.0.0.1,8001 tcp from any to any 443 in
+
+# let the responses from the captive portal web server back out
+add 19902 set 1 pass tcp from any 443 to any out
+
+# --- End redir ssl
+
 # let the responses from the captive portal web server back out
-add 19901 set 1 pass tcp from any 80 to any out
+add 19903 set 1 pass tcp from any 80 to any out
 # block everything else
-add 19902 set 1 deny all from any to any
+add 19904 set 1 deny all from any to any
 
 # ... 20000-29899: layer2 block rules per authenticated client go here...
 
@@ -922,4 +932,4 @@ function captiveportal_write_elements() {
 	return 0;
 }
 
-?>
\ No newline at end of file
+?>