| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Worked for me in testing, I watched a file briefly burst until and then be clamped down to the limiter's rate.
|
|
|
|
| |
leads to the 'Maximum login reached' on CP
|
|
|
|
| |
would like to have that on rmlist.
|
| |
|
| |
|
|\ |
|
|/
|
|
|
|
|
|
| |
PfSense 2.1.2
This annoyed me also, so I thought it worth finding what changes exactly broke this.
del_entry was broken on 2.1 branch by https://github.com/pfsense/pfsense/commit/fe3088b965a99772e76622d17ceae87288471edc
These 2 small changes make it work again without needing to reverse the other bits of stuff in that commit.
Note that Master does not have that commit at all. There are lots of these "XHTML Compliance" and similar commits in 2.1 branch that are not done in master. I don't understand why that is. Why don't those code cleanups also need to be applied to master?
|
| |
|
|
|
|
| |
done for openvpn to avoid loops
|
| |
|
|
|
|
| |
is why this is using config lock? Also where is filter configure called here?
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Conflicts:
etc/inc/filter_log.inc
etc/inc/system.inc
etc/rc
usr/local/www/guiconfig.inc
|
|
|
|
| |
and repsect user choices. Reported-by: Antoine Guillemot
|
|\ |
|
|/
|
|
|
|
| |
The 'listening_ip' option in miniupnpd.conf can accept an interface name
directly instead of having to translate it to an IPv4 address first. (This is
actually required if IPv6 support is enabled.)
|
|
|
|
| |
doesn't exist, just log that it doesn't exist and don't attempt to ifconfig destroy it, delete it from config
|
|\ |
|
| |
| |
| | |
fix
|
| |
| |
| |
| |
| |
| | |
RELENG_2_1
* Added missing usepublicip with dyndnsCheckIP
* Added missing CURL setops
|
| |
| |
| |
| | |
adding it when apinger was enabled
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
This version for 2.1 branch.
apinger is repeated here from the code above, but it should be dhcp.
Forum https://forum.pfsense.org/index.php?topic=73734.0
Selecting to remote syslog "Gateway Monitor events" would also switch on "DHCP service events" unintentionally.
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
If the DHCP Relay server is not on any local subnet, and not on any subnet that has an internal static route, but is somewhere that no specific route is known, then this code finds the default gateway and uses that in the DHCP relay "-i" parameter. The current code gets just the interface name (like "wan", "opt1"). But DHCP Relay command needs to be fed the actual device name "vr0", "vr1" etc.
To break this I simply enabled DHCP Relay, select "LAN" interface, and put Destination Server 1.2.3.4
Making this changed fixed it.
Forum: https://forum.pfsense.org/index.php?topic=75010.0
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Back-port of this fix done in master https://github.com/pfsense/pfsense/commit/31300a95f71b14dcb98c139388205223a36e8c8b and https://github.com/pfsense/pfsense/commit/8f56dd279432c4fd5a027310622e2650822e4651
Unfortunately this never got back-merged to 2.1 branch. A user on the forum noticed the issue again on 2.1.1 - https://forum.pfsense.org/index.php?topic=74922.0
I am submitting this so that when the next security issue happens, and there is 2.1.n+1 then this little fix will also happen automagically. I wonder what other fixes are in master that missed being back-ported to 2.1 branch.
|
|\ \ \ |
|
|/ / / |
|
| |/
|/|
| |
| | |
the call of get_interface_gatewayv6() in the creation of a GIF tunnel over IPv6 leads to a "Fatal error: Call to undefined function get_interface_gatewayv6() in /etc/inc/interfaces.inc on line 934". changeing the function call to get_interface_gateway_v6() fixed it for me on my local system.
|
| | |
|
| | |
|
|/
|
|
| |
problems of tap disappearing from bridge if its a member.
|
|
|
|
| |
generated by uniqid and is not purely numeric. Fixes #3591
|
| |
|
|
|
|
| |
for example, the PID is stale/invalid and there is still a running instance.
|
| |
|
|
|
|
| |
https://forum.pfsense.org/index.php?topic=74688.0
|
|\ |
|
|/
|
|
|
|
|
| |
On packages that uses row_helper when user clicks on add or delete button, the page scrolls to top.
It seems something with ajax
http://stackoverflow.com/questions/1061580/jquery-click-on-anchor-element-forces-scroll-to-top
A simple return false after jquery action fixes the unwanted scroll.
|
|
|
|
| |
new time, just drop unused php variables and set it on js
|
|
|
|
| |
isn't necessary in the long run. It's better handled in the installer stage and not after the fact.
|
|
|
|
|
|
| |
This commit broke schedules edit, it should fix #3555.
This reverts commit e1002cd2724869eabdfe1f9258d4522d572722e4.
|
|
|
|
| |
enable from proper setting. Reported-by: https://forum.pfsense.org/index.php?topic=74013.0
|
| |
|
| |
|