pfsense - Raptor Engineering's fork of the main repository for pfSense

	Commit message (Collapse)	Author	Age	Files	Lines
*	Code spacing	Phil Davis	2015-06-15	1	-2/+2
\| \| \| \| \| \| \|	and other random stuff I noticed. I think this finishes messing with code style. The codebase should match the developer style guide closely enough that 99.9% of changes will not feel the need to also massage the formatting.
*	Code style Firewall NAT	Phil Davis	2015-05-11	1	-59/+94
\|
*	Ticket #4445 do not write config and remove its cache when applying settings ↵	Ermal LUÇI	2015-02-23	1	-2/+0
\| \| \| \|	its just behaviour from dinosaur era and should have been cleanded long time ago.
*	Fix lineup of copyright lines	Phil Davis	2015-01-01	1	-1/+1
\| \| \| \| \|	and module names and other bits of formatting and typos in header comment sections.
*	Welcome 2015	Renato Botelho	2014-12-31	1	-1/+1
\|
*	outbound NAT can apply to any type of interface, make WAN-type specific ↵	Chris Buechler	2014-11-13	1	-1/+1
\| \| \| \|	reference generic
*	modify copyright statement to reflect reality	Jim Thompson	2014-11-10	1	-0/+1
\|
*	Make sure button 'move to the end' highlight last line	Renato Botelho	2014-09-04	1	-2/+2
\|
*	Add (self) for an outbound NAT source as well	jim-p	2014-05-23	1	-0/+1
\|
*	Unset these globals after use	Ermal	2014-04-14	1	-0/+5
\|
*	Include static routes in automatic NAT rules display	Phil Davis	2014-04-14	1	-0/+2
\| \| \| \| \|	If I have an internal gateway to other private subnets behind LAN, and add a static route to those private subnets through the internal gateway, then pfSense very nicely generates NAT rules on WAN-style interfaces to NAT those internal subnets on the way out of WAN. That is very good and convenient. This outbound NAT is actually correctly in the ruleset. However, the new Outbound NAT GUI page shows the Automatic Outbound NAT rules that are in effect (a great new feature in 2.2). But it did not show the rules for the static routes. This fixes it. (But the code for all of this is a bit ugly, because it all depends on having a global variable $GatewaysList in view - I am not going to attempt to re-engineer that)
*	removed duplicate type=text/javascript	ayvis	2014-03-25	1	-1/+1
\| \| \|	added type for <script>
*	replaced uppercase html tags with lowercase	ayvis	2014-03-19	1	-1/+1
\| \| \| \|	js files saved as UTF-8 / LF language="JavaScript" deprecated, replaced with type="text/javascript"
*	xhtml Compliance	ayvis	2014-03-14	1	-11/+11
\| \| \|	replaced <br>, <br/> and </br> with <br />
*	Show aliases popup on Outbound NAT list	Renato Botelho	2013-12-02	1	-4/+22
\|
*	Fix typos	Renato Botelho	2013-12-02	1	-1/+1
\|
*	Make it more visible when an item is disabled	Renato Botelho	2013-11-25	1	-17/+29
\|
*	We do not need 2 variables to do the same thing, simplify it a bit	Renato Botelho	2013-11-20	1	-19/+16
\|
*	Improve text on outbound NAT page to reflect last changes, it should fix #2416	Renato Botelho	2013-11-19	1	-6/+6
\|
*	Fix a wrong } left on my last commit	Renato Botelho	2013-11-19	1	-1/+0
\|
*	Try to detect already automatically created outbound NAT rules and avoid ↵	Renato Botelho	2013-11-19	1	-2/+18
\| \| \| \|	duplicating them. Also automatically create rules when switching from hybrid to manual. Ticket #2416
*	Use the same code to automatically create outbound NAT rules when mode ↵	Renato Botelho	2013-11-18	1	-122/+13
\| \| \| \|	change to manual, ticket #2416
*	Move automatic rules to a separate table, ticket #2416	Renato Botelho	2013-11-14	1	-43/+62
\|
*	Show advanced outbound rules and inform user what are being used and what ↵	Renato Botelho	2013-11-14	1	-9/+110
\| \| \| \|	are being ignored. It should fix #2416
*	Add hybrid and disabled outbound NAT, fixes #2416:	Renato Botelho	2013-11-13	1	-134/+143
\| \| \| \| \| \| \| \| \| \| \| \| \|	- Add 2 new outbound NAT modes, hybrid and disabled, manual and advanced keep working the same way - Hybrid mode applies manual rules first, automatic after - Disabled do no create any outbound NAT rules - Remove ipsecpassthru config field and rename advancedoutbound to outbound - Save mode on $config['nat']['outbound']['mode'] to simplify the logic - Modify config.default to reflect changes - Add code to upgrade config, and change latest_version to 10.3 - Use html to align modes and remove some hacks to align using
*	Fix indent, whitespaces and a close a couple of unbalanced tags	Renato Botelho	2013-11-12	1	-268/+336
\|
*	outboundnat, disable checkbox	PiBa-NL	2013-09-16	1	-1/+24
\|
*	touch up text, s/nat/NAT/	Chris Buechler	2013-09-03	1	-1/+1
\|
*	Tidy up "firewall_nat_out.php" XHTML	Colin Fleming	2013-05-01	1	-37/+36
\| \| \| \| \| \| \| \| \|	Close BR, INPUT and IMG tags and ALT to IMG tags Update HTML Boolean operators Move NOWRAP to class statement Move CENTER tag to ALIGN statement in TD tag Add missing closing SPAN tag Add missing closing P tag
*	Rearrange this manual outbound NAT rule generation loop -- fixes unnecessary ↵	jim-p	2013-03-20	1	-93/+93
\| \| \| \|	duplication of Localhost and VPN rules.
*	Add the user/time tracking to Port forwards and outbound NAT also.	jim-p	2013-03-20	1	-0/+7
\|
*	Insert new NAT rules on the top of the list when top plus icon is used. ↵	Renato Botelho	2013-02-21	1	-1/+1
\| \| \| \|	Fixes #1118
*	Do not skip displaying outbound NAT rules with no interface or an invalid ↵	Erik Fonnesbeck	2013-01-05	1	-8/+0
\| \| \| \|	interface; it interferes with editing/deleting the skipped rule itself or rules after it.
*	Revert "Use get_Cofnigured_interface_with_descr() here since that's the purpose"	Erik Fonnesbeck	2013-01-05	1	-6/+9
\| \| \| \|	This reverts commit 0c8e9f0c26b29f57faa2ccef9a559774103fee79.
*	Use get_Cofnigured_interface_with_descr() here since that's the purpose	Ermal	2013-01-05	1	-9/+6
\|
*	Fix outbound NAT rules when interface is deleted:	Renato Botelho	2013-01-05	1	-6/+9
\| \| \| \| \| \| \| \| \| \|	- When delete interface, do not touch outbound NAT rules - Skip outbound NAT rules when interface doesn't exist - Bump latest_config to 9.2 - Since rules with no interface were considered as wan, convert old rules adding interface 'wan' to avoid breaking old configs It should fix #2338
*	add " address" behind the interface nat name	PiBa-NL	2012-11-20	1	-1/+1
\|
*	show difference between outbound NAT and outbound NONAT.	PiBa-NL	2012-11-18	1	-6/+8
\|
*	Refine saving/applying on more pages - don't show apply or take an action ↵	jim-p	2012-10-09	1	-8/+8
\| \| \| \|	unless the user is allowed to do that.
*	Protect against a potential infinite loop here.	jim-p	2012-08-01	1	-1/+2
\|
*	Add per-rule delete ("X") button to Outbound NAT rules	Darren Embry	2012-03-21	1	-1/+12
\| \| \| \|	http://redmine.pfsense.org/issues/1062
*	fix firewall_nat_out to not auto-generate outbound NAT rules with one too ↵	Chris Buechler	2011-09-09	1	-1/+2
\| \| \| \|	many IPs
*	Clarify notes so people don't think they need to disable pf to disable NAT.	jim-p	2011-08-30	1	-1/+4
\|
*	Merge remote branch 'upstream/master'	jim-p	2011-06-01	1	-8/+15
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Conflicts: conf.default/config.xml etc/inc/filter.inc etc/inc/globals.inc etc/inc/pfsense-utils.inc etc/inc/upgrade_config.inc usr/local/www/interfaces.php
\| *	Bug#1528. Automatically create outbound NAT rules on WAN for localhost when ↵	Evgeny Yurchenko	2011-05-30	1	-0/+11
\| \| \| \| \| \| \| \|	switching to manual.
\| *	Fix automatic and manual outbound NAT for PPTP. Fixes #954	jim-p	2011-05-24	1	-8/+4
\| \|
* \|	Merge remote branch 'upstream/master'	Seth Mos	2011-03-15	1	-8/+12
\|\ \ \| \|/
\| *	Fix typo	jim-p	2011-03-10	1	-2/+2
\| \|
\| *	Clarify text on outbound NAT page.	jim-p	2011-03-10	1	-8/+12
\| \|
* \|	Merge remote branch 'upstream/master'	Seth Mos	2011-02-11	1	-16/+18
\|\ \ \| \|/