(20250212) Started a new class (util) that handles MikroTik config. in async mode, and started implementing that in the PPPoE-1000 controller. I can now configure and roll back the first three steps. Long way to go :')

readme/MikroTik-PPPoE-1000.md

@@ -69,6 +69,9 @@ configuration, simply delete your record.
 You will receive the Private IP range in either CIDR notation or as a hyphen-separated string. You need to cut up this
 larger IP pool into subnets that you will eventually assign to each VLAN (by way of creating PPPoE servers).
 
+**WARNING:** It is possible to have IP pools in a MikroTik device with overlapping IP addresses. It is not recommended,  
+though, because it may lead to conflicts that could be hard to trace back.
+
 Use `PUT` or `PATCH` method on the path `/ip/pool`. Consider to the following example JSON:
 ```json
 {
@@ -80,8 +83,8 @@ Use `PUT` or `PATCH` method on the path `/ip/pool`. Consider to the following ex
 
 **NOTE:** Looping needed.
 
-**ROLL-BACK:** Save the original configuration as a JSON string in the `comment` field. If there was no original 
-configuration, simply delete your record.
+**ROLL-BACK:** Identify your entry from the `name` field (contains 'easyfi') or from the contents of the `comment` field
+and remove it.
 
 ### 4. Create PPPoE Profiles
 
@@ -115,7 +118,7 @@ up servers that use one VLAN and one private IP sub-pool to actually handle the
 Use `PUT` or `PATCH` method on the path `/interface/pppoe-server/server`. Consider to the following example JSON:
 ```json
 {
-    "interface": "vlan10",  // ..................... The VLAN interface you had created earlier.
+    "interface": "easyfi-vlan-2001",  // ........... The VLAN interface you had created earlier.
     "profile": "easyfi-pppoe-prf-2001",  // ........ The PPPoE profile you created earlier.
     "service-name": "easyfi-pppoe-srv-2001",  // ... Use the VLAN id in the name.
     "comment": "{...}"  // ......................... The JSON string to indicate automated config.