From 36d0358b568a0dde740ade770408bef2d8c3fa65 Mon Sep 17 00:00:00 2001 From: Scott Ullrich Date: Sun, 16 Dec 2007 20:43:26 +0000 Subject: Add product_copyright re-branding support Add product_copyright_years re-branding support Add product_website re-branding support Add product_email re-branding support Work sponsored-by: Centipede Networks --- usr/local/www/services_captiveportal.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'usr/local/www/services_captiveportal.php') diff --git a/usr/local/www/services_captiveportal.php b/usr/local/www/services_captiveportal.php index 30c9ed0..7dd78b2 100755 --- a/usr/local/www/services_captiveportal.php +++ b/usr/local/www/services_captiveportal.php @@ -346,7 +346,7 @@ to access after they've authenticated. > Disable MAC filtering
If this option is set, no attempts will be made to ensure that the MAC address of clients stays the same while they're logged in. - This is required when the MAC address of the client cannot be determined (usually because there are routers between pfSense and the clients). + This is required when the MAC address of the client cannot be determined (usually because there are routers between {$g['product_name']} and the clients). If this is enabled, RADIUS MAC authentication cannot be used. "> } ?>
If RADIUS type is set to Cisco, in Access-Requests the value of Calling-Station-Id will be set to the client's IP address and - the Called-Station-Id to the client's MAC address. Default behaviour is Calling-Station-Id = client's MAC address and Called-Station-Id = pfSense's WAN IP address. + the Called-Station-Id to the client's MAC address. Default behaviour is Calling-Station-Id = client's MAC address and Called-Station-Id = {$g['product_name']}'s WAN IP address. @@ -528,7 +528,7 @@ value=""> HTTPS server name
- This name will be used in the form action for the HTTPS POST and should match the Common Name (CN) in your certificate (otherwise, the client browser will most likely display a security warning). Make sure captive portal clients can resolve this name in DNS and verify on the client that the IP resolves to the correct interface IP on pfSense.. + This name will be used in the form action for the HTTPS POST and should match the Common Name (CN) in your certificate (otherwise, the client browser will most likely display a security warning). Make sure captive portal clients can resolve this name in DNS and verify on the client that the IP resolves to the correct interface IP on {$g['product_name']}.. HTTPS certificate -- cgit v1.1