Differences

This shows you the differences between two versions of the page.

--- pfsense:about_pfsense [2020/11/27 14:29] – [IPsec] peter
+++ pfsense:about_pfsense [2020/11/27 19:34] (current) – peter
@@ Line 39: / Line 39: @@
   * NAT Reflection – in some configurations, NAT reflection is possible so services can be accessed by public IP from internal networks
-----
-===== NAT Limitation =====
+<WRAP info>
+**NAT Limitation**
 PPTP / GRE Limitation – The state tracking code in pf for the GRE protocol can only track a single session per public IP per external server.
-This means if you use PPTP VPN connections, only one internal machine can connect simultaneously to a PPTP server on the Internet.
+This means if you use [[http://en.wikipedia.org/wiki/Pptp|PPTP]] VPN connections, only one internal machine can connect simultaneously to a PPTP server on the Internet.
 A thousand machines can connect simultaneously to a thousand different PPTP servers, but only one simultaneously to a single server.
@@ Line 54: / Line 54: @@
 A solution for this is currently under development.
+</WRAP>
 ----
@@ Line 108: / Line 110: @@
 ==== OpenVPN ====
-OpenVPN is a flexible, powerful SSL VPN solution supporting a wide range of client operating systems.  See the OpenVPN website for details on its abilities.
+OpenVPN is a flexible, powerful SSL VPN solution supporting a wide range of client operating systems.
+See the [[http://openvpn.net/|OpenVPN]] website for details on its abilities.
 ==== PPTP Server ====
-PPTP is a popular VPN option because nearly every OS has a built in PPTP client, including every Windows release since Windows 95 OSR2. See this [[http://en.wikipedia.org/wiki/Point-to-point_tunneling_protocol|article]] for more information on the PPTP protocol.
+PPTP is a popular VPN option because nearly every OS has a built in PPTP client, including every Windows release since Windows 95 OSR2.
+See this [[http://en.wikipedia.org/wiki/Point-to-point_tunneling_protocol|article]] for more information on the PPTP protocol.
 ----
@@ Line 119: / Line 125: @@
 ===== PPPoE Server =====
-pfSense offers a PPPoE server.
+pfSense offers a [[http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet|PPPoE]] server.
-For more information on the PPPoE protocol, see this [[http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet|entry]].  A local user database can be used for authentication, and RADIUS authentication with optional accounting is also supported.
+A local user database can be used for authentication, and RADIUS authentication with optional accounting is also supported.
 ----
@@ Line 141: / Line 147: @@
 ===== Real Time Information =====
-Historical information is important, but sometimes it’s more important to see real time information.  SVG graphs are available that show real time throughput for each interface.  For traffic shaper users, the **Status -> Queues** screen provides a real time display of queue usage using AJAX updated gauges.  The front page includes AJAX gauges for display of real time CPU, memory, swap and disk usage, and state table size.
+Historical information is important, but sometimes it’s more important to see real time information.
+SVG graphs are available that show real time throughput for each interface.
+For traffic shaper users, the **Status -> Queues** screen provides a real time display of queue usage using AJAX updated gauges.
+The front page includes AJAX gauges for display of real time CPU, memory, swap and disk usage, and state table size.
 ----
@@ Line 167: / Line 179: @@
 ===== Captive Portal =====
-Captive portal allows you to force authentication, or redirection to a click through page for network access.  This is commonly used on hot spot networks, but is also widely used in corporate networks for an additional layer of security on wireless or Internet access.  For more information on captive portal technology in general, see the Wikipedia article on the topic.  The following is a list of features in the pfSense Captive Portal.
+[[https://en.wikipedia.org/wiki/Captive_portal|Captive portal]] allows you to force authentication, or redirection to a click through page for network access.
+This is commonly used on hot spot networks, but is also widely used in corporate networks for an additional layer of security on wireless or Internet access.
+The following is a list of features in the pfSense Captive Portal:
   * Maximum concurrent connections – Limit the number of connections to the portal itself per client IP. This feature prevents a denial of service from client PCs sending network traffic repeatedly without authenticating or clicking through the splash page.
@@ Line 174: / Line 190: @@
   * Logon pop up window – Option to pop up a window with a log off button.
   * URL Redirection – after authenticating or clicking through the captive portal, users can be forcefully redirected to the defined URL.
-  * MAC filtering – by default, pfSense® CE filters using MAC addresses. If you have a subnet behind a router on a captive portal enabled interface, every machine behind the router will be authorized after one user is authorized. MAC filtering can be disabled for these scenarios.
+  * MAC filtering – by default, pfSense filters using MAC addresses. If you have a subnet behind a router on a captive portal enabled interface, every machine behind the router will be authorized after one user is authorized. MAC filtering can be disabled for these scenarios.
   * Authentication options – There are three authentication options available
     * No authentication – This means the user just clicks through your portal page without entering credentials
@@ Line 194: / Line 210: @@
 pfSense includes both DHCP Server and Relay functionality.
+----
+===== References =====
+https://www.netgate.com/solutions/pfsense/features.html