diff options
author | Scott Ullrich <sullrich@pfsense.org> | 2006-06-08 20:04:07 +0000 |
---|---|---|
committer | Scott Ullrich <sullrich@pfsense.org> | 2006-06-08 20:04:07 +0000 |
commit | 5480497a3598c49ffcc2e3e4c57079fe922d79da (patch) | |
tree | 1fd707aaded12f5be7a75cd09d5e2e51b7a0df22 /etc/inc/captiveportal.inc | |
parent | f9c955dacf6ca16bbde6d8395086a76b355b5024 (diff) | |
download | pfsense-5480497a3598c49ffcc2e3e4c57079fe922d79da.zip pfsense-5480497a3598c49ffcc2e3e4c57079fe922d79da.tar.gz |
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.
Diffstat (limited to 'etc/inc/captiveportal.inc')
-rw-r--r-- | etc/inc/captiveportal.inc | 16 |
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 +?> |