}
}</screen>
</para>
-
+
<para>
An example command updating IPv6 lease looks as follows:
<screen>{
{
"command": "subnet4-get",
"arguments": {
- "subnet-id": 10
+ "id": 10
}
}</screen>
<screen>
{
"result": 0,
- "text": "Info about IPv4 subnet 10.0.0.0/8 (subnet-id 10) returned",
+ "text": "Info about IPv4 subnet 10.0.0.0/8 (id 10) returned",
"arguments": {
"subnets": [
{
{
"command": "subnet6-get",
"arguments": {
- "subnet-id": 11
+ "id": 11
}
}
</screen>
<screen>
{
"result": 0,
- "text": "Info about IPv6 subnet 2001:db8:1::/64 (subnet-id 11) returned",
+ "text": "Info about IPv6 subnet 2001:db8:1::/64 (id 11) returned",
"arguments": {
"subnets": [
{
used). You can mix those two approaches only if you
understand how the internal automatic subnet-id generation works.
</para>
-
+
</section>
<section>
{
"command": "subnet4-del",
"arguments": {
- "subnet-id": 123
+ "id": 123
}
}
</screen>
<screen>
{
"result": 0,
- "text": "IPv4 subnet 192.0.2.0/24 (subnet-id 123) deleted",
+ "text": "IPv4 subnet 192.0.2.0/24 (id 123) deleted",
"arguments": {
"subnets": [
{
{
"command": "subnet6-del",
"arguments": {
- "subnet-id": 234
+ "id": 234
}
}
</screen>
<screen>
{
"result": 0,
- "text": "IPv6 subnet 2001:db8:1::/64 (subnet-id 234) deleted",
+ "text": "IPv6 subnet 2001:db8:1::/64 (id 234) deleted",
"subnets": [
{
"id": 234,
</section>
-
+
</chapter> <!-- hooks-libraries -->