ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2024-01-26T15:38:09Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/3123Synced leases with HA standby cause RADIUS accounting packets2024-01-26T15:38:09ZDarren AnkneySynced leases with HA standby cause RADIUS accounting packetsIf the Kea HA peers (`libdhcp_ha.so`) are configured to send RADIUS accounting packets using the `libdhcp_radius.so` hook, then the standby peer also sends accounting packets on lease sync. This can create a few problems such as:
- The ...If the Kea HA peers (`libdhcp_ha.so`) are configured to send RADIUS accounting packets using the `libdhcp_radius.so` hook, then the standby peer also sends accounting packets on lease sync. This can create a few problems such as:
- The "acct-session-id" will not match between the accounting packets sent from the primary and standby Kea peers.
- The timestamp of the event may not match between the packets sent from the primary and standby Kea peers.
- If there were attributes gathered via the RADIUS authentication process, this will not have occurred on the standy peer. Therefore, there may be missing data in the accounting packet.
Propose that some type of flag to disable sending these accounting updates from the standby server be added.
[SF1403](https://isc.lightning.force.com/lightning/r/Case/5007V00002ZRLi2QAH/view)kea2.5.5Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/kea/-/issues/3119Coverity scan issues2024-02-06T12:55:09ZPiotrek ZadrogaCoverity scan issuesI triaged new issues detected by Coverity scan and below ones could be checked more carefully:
- High: `time_t` casting to `uint_32` - assuming we are doing `static_cast`, we should be ok until year 2106. One cases misses the `static_ca...I triaged new issues detected by Coverity scan and below ones could be checked more carefully:
- High: `time_t` casting to `uint_32` - assuming we are doing `static_cast`, we should be ok until year 2106. One cases misses the `static_cast`.
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250303669&defectInstanceId=53277773&mergedDefectId=1533185
- Medium: dereferencing invalid iterator - in most cases it seems to be false positive, but there is one place where it could be checked - this could have separate ticket
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250303968&defectInstanceId=53270168&mergedDefectId=1533337
- Low: used `auto` causing copy - this is low priority, but could be fixed anyway, just `const auto&` could be used.
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250303713&defectInstanceId=53363199&mergedDefectId=1539484
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250303704&defectInstanceId=53363142&mergedDefectId=1539483
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250303706&defectInstanceId=53363182&mergedDefectId=1539482
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250304018&defectInstanceId=53270328&mergedDefectId=1532980 and all others in `src/hooks/dhcp/lease_cmds/lease_cmds.cc`
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250304037&defectInstanceId=53270311&mergedDefectId=1532961 and all others in `src/hooks/dhcp/mysql_cb/mysql_cb_dhcp*.cc`
- https://scan5.scan.coverity.com/reports.htm#v60426/p10289/fileInstanceId=250304057&defectInstanceId=53270884&mergedDefectId=1532978 and all others in `src/hooks/dhcp/pgsql_cb/pgsql_cb_dhcp*.cc`kea2.5.5Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/3112the io_service run/run_once/poll should be called in a try-catch_all block in...2023-12-14T20:22:27ZRazvan Becheriuthe io_service run/run_once/poll should be called in a try-catch_all block in thread function in thread poolsthe io_service->run should be guarded by a try catch(...) and exceptions should be logged (if possible):
```
void
IoServiceThreadPool::threadWork() {
bool done = false;
while (!done) {
switch (getState()) {
case ...the io_service->run should be guarded by a try catch(...) and exceptions should be logged (if possible):
```
void
IoServiceThreadPool::threadWork() {
bool done = false;
while (!done) {
switch (getState()) {
case State::RUNNING: {
{
std::unique_lock<std::mutex> lck(mutex_);
running_++;
// If We're all running notify main thread.
if (running_ == pool_size_) {
main_cv_.notify_all();
}
}
// try { <<<---
// Run the IOService.
io_service_->run();
// } catch(exception& ex) { <<<---
// LOG the exception error here <<<---
// } catch (...) { <<<---
// LOG general error here <<<---
// } <<<---
```kea2.5.5Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/3110ping-check-hook update HA peer(s) with lease declinations2023-12-01T16:56:45ZThomas Markwalderping-check-hook update HA peer(s) with lease declinationsThe design overlooked how HA update peers will be updated when leases are declined. The initial release may simply state the hook is experimental and doesn't work with HA.
Proposed solution:
Leases are marked decline via a function a...The design overlooked how HA update peers will be updated when leases are declined. The initial release may simply state the hook is experimental and doesn't work with HA.
Proposed solution:
Leases are marked decline via a function added to support
ping-checking, Dhcpv4Srv::serverDecline(). This function gets
invoked by the unpark callback if ping-check concluded the address
is unavailable (i.e. in use).
In order to propagate the declination to HA peers, a new hook point
will be added within this function, "lease4-server-decline". This
affords any hook library with an opportunity to take an action when
the server declines a lease. There is already a "lease4-decline" hook
point but this is for leases that are declined by clients via DHCPDECLINEs.
HA will need to implement a callout handler for this hook point which
propagates the update to the appropriate peer(s). Unlike updates done
via leases4_committed, there is no outbound response pending and
thus no need to park the query. Nor is there any need to wait for
the updates to be acknowledged.kea2.5.5Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/3108ALLOC_ENGINE_V4_ALLOC_ERROR message update2023-12-18T19:11:47ZPeter DaviesALLOC_ENGINE_V4_ALLOC_ERROR message updateALLOC_ENGINE_V4_ALLOC_ERROR:
A suggestion from a Kea user to update the ALLOC_ENGINE_V4_ALLOC_ERROR messages
"with multiple records were found in the database where only one was expected ..."
It may be helpful for new users...ALLOC_ENGINE_V4_ALLOC_ERROR:
A suggestion from a Kea user to update the ALLOC_ENGINE_V4_ALLOC_ERROR messages
"with multiple records were found in the database where only one was expected ..."
It may be helpful for new users to mention the "ip-reservations-unique" setting.
[kea-users](https://lists.isc.org/pipermail/kea-users/2023-October/004332.html)kea2.5.5Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/3107ping-check-hook implement ST mode in PingCheckMgr2023-12-13T15:44:38ZThomas Markwalderping-check-hook implement ST mode in PingCheckMgrExtend PingCheckMgr, created in #3083, to support ST mode. The basic steps are:
1. PingCheckMgr::start()
- Skip creating the thread-pool
- Create an WatchSocket and pass it into PingChannel::open(). PingChannel::asyncSend() would ...Extend PingCheckMgr, created in #3083, to support ST mode. The basic steps are:
1. PingCheckMgr::start()
- Skip creating the thread-pool
- Create an WatchSocket and pass it into PingChannel::open(). PingChannel::asyncSend() would invoke WatchSocket::markReady() and socketWriteCallback() would invoke WatchSocket::clearReady()
- After the PingChannel is created, manager would crate an external socket, via IfaceMgr::addExternalSocket(), for the channel's socket.
2. PingCheckMgr::stop() would need to remove the sockets added abovekea2.5.5Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/3074Support for option 121 (classless-static-routes) is needed2024-01-18T08:34:12ZPhilip PrindevilleSupport for option 121 (classless-static-routes) is needed---
name: Feature request
about: Support classless-static-routes (option 121)
---
**Some initial questions**
- While routes can be hand-mangled into the correct order and then expressed as a string of hex bytes, this is onerous for DHC...---
name: Feature request
about: Support classless-static-routes (option 121)
---
**Some initial questions**
- While routes can be hand-mangled into the correct order and then expressed as a string of hex bytes, this is onerous for DHCP administrations and error-prone. A plugin could be done to support this option.
**Is your feature request related to a problem? Please describe.**
In a complex enterprise mesh VPN with redundant IPsec connectivity, the DHCP server might need to provide hints as to that topology. This feature would make it easier to provide CIDR routes to the various islands in the mesh.
**Describe the solution you'd like**
A simpler notation expressing [subnet, next-hop]* where the plugin figures out the appropriate encoding of the prefix, the significant octets of the subnet, and the 4 octets of next-hop router.
**Describe alternatives you've considered**
In cases where a front-end (such as a Netconf/YANG proxy) synthesizes a Kea configuration, it could do the encoding previously described, but developers would probably appreciate being able to inspect and easily validate the intermediate Kea config that the front-end generated.
**Additional context**
An example of having to encode this is currently done for ISC-DHCP in OpenWRT when converting UCI to ISC-DHCP config.
**Funding its development**
If given examples of another plugin that might serve as a suitable homologue, I'd be willing to try to write such a plugin myself.
**Participating in development**
Yes, I'm willing to participate in all phases.
**Contacting you**
philipp@redfish-solutions.com or philipp64 on oftc.net or libera.chat.kea2.5.5Piotrek ZadrogaPiotrek Zadrogahttps://gitlab.isc.org/isc-projects/kea/-/issues/3019Add retries and delay for initial lease db connection on Kea start2024-01-16T16:38:12ZMarcin GodzinaAdd retries and delay for initial lease db connection on Kea startWhen Kea starts and can not connect to lease db, it makes 4 tries in total in rapid succession. (under 5 seconds)
If we have a slowly starting db engine, Kea may exit prematurely.
Existing parameters like `"max-reconnect-tries"`, `"conn...When Kea starts and can not connect to lease db, it makes 4 tries in total in rapid succession. (under 5 seconds)
If we have a slowly starting db engine, Kea may exit prematurely.
Existing parameters like `"max-reconnect-tries"`, `"connect-timeout"`, and `"reconnect-wait-time"` work only when the db connection is **LOST** after the initial startup and connection check.kea2.5.5Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/2788Kea might not use getopt correctly on alpine2024-01-26T18:01:50ZAndrei Pavelandrei@isc.orgKea might not use getopt correctly on alpineOn all the alpine systems in jenkins, we have this failure:
```
netconf_controller_unittests.cc:134
Expected equality of these values:
std::string(ex.what())
Which is: "unsupported option: [x] d2-test-config.json"
"unsupported o...On all the alpine systems in jenkins, we have this failure:
```
netconf_controller_unittests.cc:134
Expected equality of these values:
std::string(ex.what())
Which is: "unsupported option: [x] d2-test-config.json"
"unsupported option: [x] "
```
It's not related only to NETCONF. The tests there are just more thorough and check for the error message and that's why it appears only there. The tested code is common to all binaries.
The tested argument is just `-x`. It could be that on alpine systems, the way Kea uses getopt in `DControllerBase::parseArgs()` doesn't clear an argument previously used in the same unit test, which would be why `d2-test-config.json` appears in the error message.
You can see the failures here: https://jenkins.aws.isc.org/job/kea-dev/job/ut-extended/1017/.kea2.5.5Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/kea/-/issues/1790[ISC-support #18162] Configuration Backend and map parameters2024-01-26T13:50:32ZBertrand Buclin[ISC-support #18162] Configuration Backend and map parameters---
name: Feature request
about: Configuration backend and map parameters
---
**Some initial questions**
- Are you sure your feature is not already implemented in the latest Kea version? yes
- Are you sure what you would like to do is ...---
name: Feature request
about: Configuration backend and map parameters
---
**Some initial questions**
- Are you sure your feature is not already implemented in the latest Kea version? yes
- Are you sure what you would like to do is not possible using some other mechanisms? yes
- Have you discussed your idea on kea-users or kea-dev mailing lists? yes
**Is your feature request related to a problem? Please describe.**
The configuration backend hook allows to put server parameters to the configuration database, but does not allow to put complex parameters/maps. For example, it would be great to be able to put the expired-leases-processing map in the database, particularly as its “semantics” apply to all the servers that share the same configuration items like subnets and shared networks. Enhancing the “global-parameter[46]-set” API parameters to allow maps would be a great addition.
**Describe the solution you'd like**
Enhance the remote-parameter[46]-set API parameter set to allow including maps so that, for example, the following API call would be a legitimate one:
```
{"command": "remote-global-parameter6-set"
"arguments": {
"parameters": {
"t1-percent": 0.85,
"renew-timer": 43200,
"expired-leases-processing": {
"reclaim-timer-wait-time": 600,
"flush-reclaimed-timer-wait-time": 4320,
"hold-reclaimed-time": 17280,
"max-reclaim-leases": 100,
"max-reclaim-time": 9999,
"unwarned-reclaim-cycles": 5
}
},
"remote": {"type": "mysql"}, "server-tags": [ "all" ]
}
}
```
**Describe alternatives you've considered**
Leave the parameters in the individual server config files, but that makes it painful to update the parameters across all servers.
**Additional context**
Other parameter maps could be considered, such as the dhcp-ddns one.
**Funding its development**
Kea is run by ISC, which is a small non-profit organization without any government funding or any permanent sponsorship organizations. Are you able and willing to participate financially in the development costs? This is a fairly minor development, I'd imagine... we are indirectly contributing by being paying subscriber :)
**Participating in development**
Are you willing to participate in the feature development? ISC team always tries to make a feature as generic as possible, so it can be used in wide variety of situations. That means the proposed solution may be a bit different that you initially thought. Are you willing to take part in the design discussions? Are you willing to test an unreleased engineering code? Sure.
**Contacting you**
How can ISC reach you to discuss this matter further? If you do not specify any means such as e-mail, jabber id or a telephone, we may send you a message on github with questions when we have them.
You can reach me too on bbuclin@att.comkea2.5.5Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/1149Extend Kea HA to permit a single backup server for multiple primary/active se...2024-01-26T14:35:10ZVicky Riskvicky@isc.orgExtend Kea HA to permit a single backup server for multiple primary/active serversAs an administrator with many offices, each with a local Kea server, I would prefer to have a single backup server, centrally located, that can serve as backup for many remote Kea servers.
I realize that one option is to run multiple Ke...As an administrator with many offices, each with a local Kea server, I would prefer to have a single backup server, centrally located, that can serve as backup for many remote Kea servers.
I realize that one option is to run multiple Kea servers on the single machine at HQ, but monitoring and managing that single Kea server would also present scaling issues. This request is to be able to have a single Kea server that has multiple failover relationships.
* The scale would be dozens of remote active nodes to a single passive node.
* In this scenario, the active Kea servers are not likely to be heavily loaded or extremely active.
* It is ok if the central server is limited in the number of relationships in which it can become the primary simultaneously.kea2.5.5https://gitlab.isc.org/isc-projects/stork/-/issues/1296Sanity checks for Stork 1.15.0 rc12024-02-07T12:54:23ZAndrei Pavelandrei@isc.orgSanity checks for Stork 1.15.0 rc1We are now at step SANITY CHECKS of Stork 1.15.0 rc1.
Please do sanity checks according to the steps below:
1. Get the tarball and check it, run tests with `rake unittest:backend` or `rake unittest:backend_db`.
2. Get the apk, deb & rp...We are now at step SANITY CHECKS of Stork 1.15.0 rc1.
Please do sanity checks according to the steps below:
1. Get the tarball and check it, run tests with `rake unittest:backend` or `rake unittest:backend_db`.
2. Get the apk, deb & rpm packages, place them in the tarball location, run tests with `rake system_tests` and `rake system_tests_ui`.
3. Start demo locally with `rake demo:up` and follow the steps from the demo wiki: https://gitlab.isc.org/isc-projects/stork/-/wikis/Demo
4. Install server and agent locally e.g. in VMs from apk, deb & rpm packages
Before starting, please state what you are checking in a thread/discussion (not as comment).
When you finish a check, state in the same thread/discussion what the result is.
This way we know what is covered upfront and we can avoid repeating ourselves.
* tarball: https://gitlab.isc.org/isc-projects/stork/-/jobs/3998886/artifacts/browse
* apk, deb & rpm packages: https://gitlab.isc.org/isc-projects/stork/-/jobs/3998884/artifacts/browse
Hooks:
* tarball: https://gitlab.isc.org/isc-projects/stork/-/jobs/3998897/artifacts/browse
* apk, deb & rpm packages: https://gitlab.isc.org/isc-projects/stork/-/jobs/3998904/artifacts/browse
Release notes: https://gitlab.isc.org/isc-projects/stork/-/wikis/Releases/Release-notes-1.15.01.152024-02-07https://gitlab.isc.org/isc-projects/stork/-/issues/1295Changes for Stork 1.15.0
release2024-02-05T21:51:45ZAndrei Pavelandrei@isc.orgChanges for Stork 1.15.0
release
- [x] announce the release in the changelog
- [x] bump up Stork versions
- [x] merge changelog entries
- [x] announce the release in the changelog
- [x] bump up Stork versions
- [x] merge changelog entries1.15Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.org2024-02-07https://gitlab.isc.org/isc-projects/stork/-/issues/1286Make tarball task optional2024-02-01T22:58:52ZSlawek FigielMake tarball task optionalThe `tarball` CI task tries to download some artifacts from other tasks, although they are not needed. It sometimes fails.
[Source](https://gitlab.isc.org/isc-projects/stork/-/jobs/3965088)
```
Preparing the "docker+machine" executor
0...The `tarball` CI task tries to download some artifacts from other tasks, although they are not needed. It sometimes fails.
[Source](https://gitlab.isc.org/isc-projects/stork/-/jobs/3965088)
```
Preparing the "docker+machine" executor
00:24
Using Docker executor with image registry.gitlab.isc.org/isc-projects/stork/ci-base:3 ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image registry.gitlab.isc.org/isc-projects/stork/ci-base:3 ...
Using docker image sha256:4579cce3c0c8b1f05031a797d08e081c184777f80ef4a11f0ea325ba533e2c99 for registry.gitlab.isc.org/isc-projects/stork/ci-base:3 with digest registry.gitlab.isc.org/isc-projects/stork/ci-base@sha256:373b00e8c068bd4798d8340a20ee31d2aea1fb21a7ec6409217a1a7c75b82f2a ...
Preparing environment
00:23
Running on runner-4ylmhpa7-project-87-concurrent-0 via runner-4ylmhpa7-gitlab-docker-runner-1706108027-e915d800...
Getting source from Git repository
00:04
Fetching changes...
Initialized empty Git repository in /builds/isc-projects/stork/.git/
Created fresh repository.
Checking out e5b5702b as detached HEAD (ref is refs/merge-requests/699/head)...
Skipping Git submodules setup
Downloading artifacts
02:43
Downloading artifacts for build_ui (3965074)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965074 responseStatus=200 OK token=64_3MZNy
Downloading artifacts for build_doc (3965075)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965075 responseStatus=200 OK token=64_3MZNy
Downloading artifacts for build_backend (3965076)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965076 responseStatus=200 OK token=64_3MZNy
WARNING: tools/python/bin/python: chmod tools/python/bin/python: no such file or directory (suppressing repeats)
Downloading artifacts for build_backend_legacy (3965077)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965077 responseStatus=200 OK token=64_3MZNy
Downloading artifacts for build_debs_amd64 (3965080)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965080 responseStatus=200 OK token=64_3MZNy
Downloading artifacts for build_debs_arm64 (3965081)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965081 responseStatus=200 OK token=64_3MZNy
Downloading artifacts for build_rpms_amd64 (3965082)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965082 responseStatus=200 OK token=64_3MZNy
Downloading artifacts for build_rpms_arm64 (3965083)...
Downloading artifacts from coordinator... ok host=gitlab.isc.org id=3965083 responseStatus=200 OK token=64_3MZNy
Downloading artifacts for build_apks_amd64 (3965084)...
ERROR: Downloading artifacts from coordinator... not found host=gitlab.isc.org id=3965084 responseStatus=404 Not Found token=64_3MZNy
FATAL: file does not exist
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1
```1.15Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1285Update project dependencies2024-02-05T18:03:23ZSlawek FigielUpdate project dependenciesWe should update Go, JavaScript, Python, and so on dependencies to fix bugs and security vulnerabilities.We should update Go, JavaScript, Python, and so on dependencies to fix bugs and security vulnerabilities.1.15Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1284Delete a subnet from the subnet view2024-01-30T13:32:02ZMarcin SiodelskiDelete a subnet from the subnet viewWe need a button in the subnet view to delete selected subnet from the Kea servers and from the database. The user should confirm deletion of the subnet. This is analogous to deletion of the host reservation.We need a button in the subnet view to delete selected subnet from the Kea servers and from the database. The user should confirm deletion of the subnet. This is analogous to deletion of the host reservation.1.15Piotrek ZadrogaPiotrek Zadrogahttps://gitlab.isc.org/isc-projects/stork/-/issues/1277Create new subnets using the subnet form2024-01-26T15:05:09ZMarcin SiodelskiCreate new subnets using the subnet formStork UI has a form allowing for updating an existing subnet. We need to create new API calls in the backend to support creating new subnets in the Kea servers. The existing form should be used for specifying the new subnet's configurati...Stork UI has a form allowing for updating an existing subnet. We need to create new API calls in the backend to support creating new subnets in the Kea servers. The existing form should be used for specifying the new subnet's configuration data.1.15Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/1272Build hooks fails due to missing space2024-01-24T11:53:56ZSlawek FigielBuild hooks fails due to missing spaceIt started occurring after merge #1254.
```
Reverting remap operation...
/builds/isc-projects/stork/tools/ruby/bin_bundle/fpm -s dir -C /builds/isc-projects/stork/hooks -n isc-stork-server-hook-ldap -t apk -a amd64 -v 1.14.0.24010815450...It started occurring after merge #1254.
```
Reverting remap operation...
/builds/isc-projects/stork/tools/ruby/bin_bundle/fpm -s dir -C /builds/isc-projects/stork/hooks -n isc-stork-server-hook-ldap -t apk -a amd64 -v 1.14.0.240108154502 --license MPL 2.0 --url https://gitlab.isc.org/isc-projects/stork/ --vendor Internet Systems Consortium, Inc. stork-server-ldap.so=/var/lib/stork-server/hooks/stork-server-ldap.so --rpm-digest sha256
{:timestamp=>"2024-01-08T15:45:20.075263+0000", :message=>"All flags should be before the first argument (stray flags found: [\"--rpm-digest\"]", :level=>:warn}
{:timestamp=>"2024-01-08T15:45:20.089074+0000", :message=>"Invalid package configuration: Cannot package the path '/builds/isc-projects/stork/hooks/--rpm-digest', does it exist?", :level=>:error}
```1.15Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1271Switching a subnet between shared networks2024-01-18T11:01:11ZMarcin SiodelskiSwitching a subnet between shared networksThis ticket should extend the subnet form with the ability to inlude a subnet in the shared network or exclude the subnet from the shared network resulting in moving the subnet to a global scope. Use the `network4-add` and `network4-del`...This ticket should extend the subnet form with the ability to inlude a subnet in the shared network or exclude the subnet from the shared network resulting in moving the subnet to a global scope. Use the `network4-add` and `network4-del` commands.1.15Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/1270Feature request - bulk authorize machines2024-01-17T17:58:42ZPiotrek ZadrogaFeature request - bulk authorize machinesFeature proposal - bulk authorize more than one machine.
- Easy way - `Authorize all machines`
- More complicated way - `select machines and then bulk authorize selected`Feature proposal - bulk authorize more than one machine.
- Easy way - `Authorize all machines`
- More complicated way - `select machines and then bulk authorize selected`1.15Piotrek ZadrogaPiotrek Zadroga