| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| | |
marjohn56/RTSOLD-lock-creation,-dhcp6c-launch-&-kill-changes-#3
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added lock file creation and check to RTSOLD script creation. This is to
prevent mutliple launches of dhcp6c, this appears to happen when
multiple RA's are received in rapid succession at the start of a
session. Once created dhcp6c cannot be launched again until the lock
file is deleted, this is done within the kill_dhcp6_client process
locking the two together.
The kill vlaue used to kill the dhcp6c client is now variable. The
value -9 causes the process to exit without sending a release if
required, and if the timing is just rignt can cause the pid file to be
left behind; -15 allows for a graceful exit and if the release flag is
not set then it sends and waits for the release confirnation, the value
now switches between those depending on the configuration option 'No
Release'. If no release is true then -9 is used as the type. Any left
behind pid is removed automatically. This change will make it possible
to stop the use of the -n flag, thus allowing the dcp6c to send a
release manually, if so required.
The launch of dhcp6c when in dhcp6withoutRA is moved to its own
function, as uch as anything this makes the code tidy around the bottom
of nterface_dhcpv6_configure().
A completely new method of implimenting dhcp6wihtoutRA is used. In
default mode RTSOLD launches dhcp6c. In dhcp6wihtoutRA mode dhcp6
aunches RTSOLD.
New scripts are created and old ones modified to handle this mode, the
dhcp6 conf file changes depending on the mode calling a different script
for each mode. In simple terms its dcp6->rtsold- lan_configure. Whenever
dhcp6 gets a response that launches its script then it will run rtsold,
the RA in turn will cause the wan6 configure script to run. This method
also means the script only ever runs once and no modified dhcp6c is
required.
The scripts are dynamic and change depending on the mode. Creation takes
into account that the domain-name-server variables created by dhcp6 and
passed to the script it calls are passed on. In default mode this is
simple as it calls the dhcp6c_*_script which calls the rc.newwanipv6
script directly, in dhcp6withoutRA its RTSOLD that calls the
dhcp6c_*_script, so in order to make this change work the variables are
echoed to the tmp folder and retreived by the dhcp6withoutRA version of
dhcp6c_*_script when that calls rc.newwanip.
|
| |\ \ |
|
| |/ / |
|
| |\ \ |
|
| | | | |
|
| |\ \ \ |
|
| | |/ / |
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | | |
When creating a new Captive Portal Zone the user can fail to select any of the Authorization Method radio buttons. No default radio button is selected - that is probably good, as the user has to think and click to decide which authorization method they will use.
But the form validation should check that some valid value is POSTed when the CP is enabled.
|
| |\ \ \ |
|
| | |/ /
| | |
| | | |
Add full stop and spacing between sentences.
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Corrects malformed NMEA sentences by calculating and appending the checksum and adding missing special characters "$" and "*"
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| |/ / / |
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Note: is_intrange() only tells us that the range is good and might be delimited by a "-" or a ":", so if we want to take apart the 2 parts of the range (like is done here) we have to also test the string to decide which separator to use.
I decided it is fine to accept ranges with a ":" separator. Even though it is not explicitly mention on the UI, a user who accidentally does it will be pleasantly happy that it works.
|
| | | | |
| | | |
| | | |
| | | | |
Tags must be in the range 1 to 4094
Flag the various input errors and only report them once each.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
1) Make the row delete button actually work
2) Do not allow ranges that go backwards like 25-20 or just "-" or 1-sided ranges "-42" "42-"
3) Remember the POSTed stuff to redisplay to the user if there were input errors
4) Ranges or numbers entered could overlap - just save a list of the unique members. e.g. If the user enters 5-15 and 10-20
|
| |\ \ \ \ |
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
NOYB/System_Update_Settings_-_GitSync_Options_master
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add GitSync options selectors to post update GitSync.
Minimal, Diff, Show Files, Show Command, Dry Run
The GitSync options have utility for post update sync also.
Dependency: Will merge cleanly but for the options to be functional, https://github.com/pfsense/FreeBSD-ports/pull/263 is required.
|
| |\ \ \ \ \ |
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / / |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | |/ / / / |
|
| |\ \ \ \ \ |
|
| | |\ \ \ \ \ |
|
| | |\ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Copy-paste error from code that used $_REQUEST. This is more correct to use $_POST.
|
| | | |_|/ / / /
| |/| | | | |
| | | | | | |
| | | | | | | |
I was blanking out stuff to see what input error messages came about fields that are required. I was surprised that the Interface Description would save empty. The system did not immediately explode (I was playing with a bonus interface I had created in a VM) but I don't think it is desirable to have interfaces with no description.
The change here also only does the other checks on the description if it has actualy been entered - no point checking a whole lot of other dependent stuff if the description is not even entered.
|
| |\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | | |
|
| | |\ \ \ \ \ \
| | | |_|/ / /
| | |/| | | | |
|
