Project

General

Profile

Actions

Todo #5177

closed

Bugs with available PR fixes that needed review and merge before 2.2.5

Added by Kill Bill over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
09/20/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

There are multiple trivial fixes available for blatant bugs, just rotting in GitHub and getting periodic conflicts from the bootstrap madness. I cannot see bootstrap anywhere usable until mid of next year, to put it mildly. After redoing/backporting all those conflicting ones, putting this here so that the works gets finally done and bugs get fixed in code that people actually use in production, instead of code that they'll eventually be able to use a year later.

https://github.com/pfsense/pfsense/pull/1909 - DH groups 22-24 do not function (Bug #4918)
https://github.com/pfsense/pfsense/pull/1911 - Add L2TP server's interface to mpd.conf (Bug #4830)
https://github.com/pfsense/pfsense/pull/1907 - pkg_edit.php - fix issue where default value was not being populated for newly added fields
https://github.com/pfsense/pfsense/pull/1790 - pkg install error handling and connect timeout RELENG_2_2 (loads of complaints on forums about broken, half-installed packages because the code happily goes on after fetch failure as if nothing happened)

Actions #1

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1913 - pkg-utils.inc typo fix, typo causing useless junk leftovers in syslog configuration for packages which use separate syslog facility (arpwatch, spamd, tinc...)

Actions #2

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1836 - Ignore DHCP pools that are out of range (if the user changes the subnet of an interface then applies without adjusting the DHCP pool range/s to be in the new subnet, then an invalid dhcpd.conf is generated)

Actions #3

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1839 - DynDNS should allow "@" at hostname (Bug #3900); make no-ip.com round robin DNS work (Bug #5051)

Actions #4

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1916 - Fix Cloudflare support for Dynamic DNS Updates (Todo #4737)

Actions #5

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1918 - GratisDNS support for hosts without subdomains

Actions #6

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1921 - Show openvpn interfaces while reassigning the interfaces for a restored config backup

Actions #7

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1922 - Move "Enable MSS clamping on VPN traffic" to System - Advanced - Firewall / NAT (Bug #4864)

Actions #8

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1781 - Preserve MLPPP settings when saving interface settings (Bug #4568)

Actions #9

Updated by Phillip Davis over 8 years ago

https://github.com/pfsense/pfsense/pull/1923 - Redmine #5162 do not allow alias rename to an existing name - RELENG_2_2

Actions #10

Updated by Kill Bill over 8 years ago

https://github.com/pfsense/pfsense/pull/1926 - fix interface assignment menus running off VGA screen

Actions #11

Updated by Kill Bill over 8 years ago

Vast majority of the PRs I mentioned above and wasted about two days of my time with picking up on GitHub, redoing and resubmitting due to conflicts arising from bootstrap was closed due to authorship "issue". Reference: https://github.com/pfsense/pfsense/pull/1917#issuecomment-142041673

Feel free to close this bug as well. Not only you have repeatedly wasted the time of the original commiters, you've wasted mine in addition because apparently the former wasn't enough. Worse yet, as final results, the bugs are still sitting there in the code.

Can only time certain amount of bullshit. ATM, the limit is completely exhausted.

Actions #12

Updated by Renato Botelho over 8 years ago

  • Status changed from New to Resolved

Almost everything was committed, other cases like missing CLA will be handled on github

Actions

Also available in: Atom PDF