Skip to content

add All-Inkl.com to DynDns servicesStable/18.1#691

Closed
ghost wants to merge 117 commits intomasterfrom
stable/18.1
Closed

add All-Inkl.com to DynDns servicesStable/18.1#691
ghost wants to merge 117 commits intomasterfrom
stable/18.1

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented May 27, 2018

All-Inkl is one of the biggest european providers and offers a DynDns service. The code was tested extensively and checks the result for its correctness. The code is a fork from pfsense/pfsense#3223

fichtner and others added 30 commits January 4, 2018 17:02
Error: Attribute "type" not allowed on element <i> at this point.
(cherry picked from commit 9960e5a)
(cherry picked from commit db06a4d)
(cherry picked from commit a2091db)
(cherry picked from commit 76a866f)
(cherry picked from commit 0dfdb00)
(cherry picked from commit 129acfd)
(cherry picked from commit 23035f1)
(cherry picked from commit 7bc1c20)
(cherry picked from commit 24caebf)
(cherry picked from commit 9d7a5ff)
(cherry picked from commit a091aec)
This is recommended as Chrome gave us CRSF issues with this "feature"
for no apparent reason.  We don't have minified stylesheets...
fichtner and others added 26 commits April 26, 2018 11:11
The plugin will move to core in 18.7, but for now we can adapt
the changes that have been implemented there.
(cherry picked from commit b6b677f)
(cherry picked from commit ac2f2d4)
(cherry picked from commit e97d13b)
(cherry picked from commit e910c4c)
PR: opnsense/core#2400
(cherry picked from commit 95e79a6)
The help message on the Freeradius User form is off for the enabled, username and password fields.
Username and Password have regex mask validation patterns, but the help message was placed on the wrong field.
Fixed this by moving the 'Allowed characters' text to the correct help field.

(cherry picked from commit 2aecb80)
(cherry picked from commit 0bc2c00)
Leave out tokenzier drop for now.
@fraenki
Copy link
Copy Markdown
Member

fraenki commented May 27, 2018

@tamara2k Thanks for your contribution. Your PR is screwed. Please rebase against master branch.

@fichtner
Copy link
Copy Markdown
Member

yup, I think we need to close this and start with a cleaner PR :)

@fichtner
Copy link
Copy Markdown
Member

Ah, there's #693 and #692, we'll do stable/18.1 when it's ready internally.

@fichtner fichtner closed this May 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

8 participants