[DOCs/operators]: 2024.4 nutella release changelog & mixnode ipv6 cla…

…rification (#4581)

* edit IPv6 mixnode info

* add mixnode ipv6 info and nuttela changelog

* syntax edit

documentation/operators/src/changelog.md

@@ -2,6 +2,18 @@
 
 This page displays a full list of all the changes during our release cycle from [`v2024.3-eclipse`](https://github.com/nymtech/nym/blob/nym-binaries-v2024.3-eclipse/CHANGELOG.md) onwards. Operators can find here the newest updates together with links to relevant documentation. The list is sorted so that the newest changes appear first.
 
+## `v2024.4-nutella`
+
+- [Merged PRs](https://github.com/nymtech/nym/milestone/59?closed=1)
+- [`nym-node`](nodes/nym-node.md) version `1.1.1`
+- This release also contains: `nym-gateway` and `nym-network-requester` binaries
+- core improvements on nym-node configuration
+- Nym wallet changes:
+    - Adding `nym-node` command to bonding screens
+    - Fixed the delegation issues with fixing RPC
+- [Network configuration](nodes/configuration.md#connectivity-test-and-configuration) section updates, in particular for `--mode mixnode` operators
+- [VPS IPv6 troubleshooting](troubleshooting/vps-isp.md#ipv6-troubleshooting) updates
+
 ## `v2024.3-eclipse`
 
 - Release [Changelog.md](https://github.com/nymtech/nym/blob/nym-binaries-v2024.3-eclipse/CHANGELOG.md)

documentation/operators/src/nodes/configuration.md

@@ -163,14 +163,18 @@ This lets your operating system know it's ok to reload the service configuration
 
 During our ongoing testing events [Fast and Furious](https://nymtech.net/events/fast-and-furious) we found out, that after introducing IP Packet Router (IPR) and [Nym exit policy](https://nymtech.net/.wellknown/network-requester/exit-policy.txt) on embedded Network Requester (NR) by default,  only a fragment of Gateways routes correctly through IPv4 and IPv6. We built a useful monitor to check out your Gateway (`nym-node --mode exit-gateway`) at [harbourmaster.nymtech.net](https://harbourmaster.nymtech.net/).
 
-IPv6 routing is not only a case for Exit Gateways. Imagine that you run a `mixnode` without IPv6 enabled and packets are going through the Mixnet through such route:
+IPv6 routing is not only a case for gateways. Imagine a rare occassion when you run a `mixnode` without IPv6 enabled and a client will sent IPv6 packets through the Mixnet through such route:
 ```ascii
-user -> [entry-gateway] -> [mixnode layer 1] -> [your mixnode] -> [IPv6 mixnode layer3] -> [exit-gateway]
+[client] -> [entry-gateway] -> [mixnode layer 1] -> [your mixnode] -> [IPv6 mixnode layer3] -> [exit-gateway]
 ```
-In this case your `mixnode` will not be able to route the packets. The node will drop the packets and its performance would go down.
+In this (unusual) case your `mixnode` will not be able to route the packets. The node will drop the packets and its performance would go down. For that reason it's befetial to have IPv6 enabled when running a `mixnode` functionality.
 
 ### Quick IPv6 Check
 
+```admonish caution
+Make sure to keep your IPv4 address enabled while setting up IPv6, as the majority of routing goes through that one!
+```
+
 You can always check IPv6 address and connectivity by using some of these methods:
 
 ```sh
@@ -330,6 +334,10 @@ Make sure that you get the validation of IPv4 and IPv6 connectivity. If there ar
 
 #### Mode: `mixnode`
 
+```admonish caution title=""
+Most of the time the packets sent through the Mixnet are IPv4 based. The IPv6 packets are still pretty rare and therefore it's not mandatory from operational point of view. If you preparing to run a `nym-node` with all modes enabled once this option is implemented, then the IPv6 setup on your VPS is required.
+```
+
 1. Download `network_tunnel_manager.sh`, make executable and run:
 
 ```sh

documentation/operators/src/troubleshooting/nodes.md

@@ -194,18 +194,12 @@ If you are still unable to see your node on the dashboard, or your node is decla
 - You did not configure your router firewall while running the node from your local machine behind NAT, or you are lacking IPv6 support
 - Your Mix Node is not running at all, it has either exited / panicked or you closed the session without making the node persistent. Check out the [instructions](../nodes/configuration.md#automating-your-node-with-tmux-and-systemd).
 
-```admonish caution
+```admonish caution title=""
 Your Nym Node **must speak both IPv4 and IPv6** in order to cooperate with other nodes and route traffic. This is a common reason behind many errors we are seeing among node operators, so check with your provider that your VPS is able to do this!
 ```
 
 #### Check IPv6 Connectivity
 
-IPv6 routing is not only a case for Exit Gateways. Imagine that you run a `mixnode` without IPv6 enabled and packets are going through the Mixnet through such route:
-```ascii
-user -> [entry-gateway] -> [mixnode layer 1] -> [your mixnode] -> [IPv6 mixnode layer3] -> [exit-gateway]
-```
-In this case your `mixnode` will not be able to route the packets. The node will drop the packets and its performance would go down.
-
 You can always check IPv6 address and connectivity by using some of these methods:
 
 ```sh
@@ -241,33 +235,6 @@ On certain cloud providers such as AWS and Google Cloud, you need to do some add
 
 If the difference between the two is unclear, contact the help desk of your VPS provider.
 
-#### No IPv6 connectivity
-
-Make sure that your VPS has IPv6 connectivity available with whatever provider you are using.
-
-To get all ip addresses of your host, try following commands:
-
-```
-hostname -i
-```
-
-Will return your **local ip** address.
-
-```
-hostname -I
-```
-
-Will return all of the ip addresses of your host. This output should look something like this:
-
-```
-bob@nym:~$ hostname -I
-88.36.11.23 172.18.0.1 2a01:28:ca:102::1:641
-```
-
-- The first **ipv4** is the public ip you need to use for the `--announce-host` flag.
-- The second **ipv4** is the local ip you need to use for the `--host` flag.
-- The 3rd output should confirm if your machine has ipv6 available.
-
 ### Running on a local machine behind NAT with no fixed IP address
 
 Your ISP has to be IPv6 ready if you want to run a Nym Node on your local machine. Sadly, in 2020, most of them are not and you won't get an IPv6 address by default from your ISP. Usually it is an extra paid service or they simply don't offer it.
@@ -304,7 +271,7 @@ thread 'tokio-runtime-worker' panicked at 'Failed to create TCP listener: Os { c
 ```
 
 Then you need to `--announce-host <PUBLIC_IP>` and `--host <LOCAL_IP>` on startup. This issue is addressed [above](#missing-`announce-host`-flag)
-
+<!-- NEEDS TO BE REWORKED AND ADD WARNING TO NOT CHANGE OTHER PORTS FOR API
 ### Can I use a port other than 1789?
 
 Yes! Here is what you will need to do:
@@ -331,7 +298,7 @@ nano ~/.nym/nym-nodes/alice-node/config/config.toml
 You will need to edit two parts of the file. `announce_address` and `listening_address` in the `config.toml` file. Simply replace `:1789` (the default port) with `:1337` (your new port) after your IP address.
 
 Finally, restart your node. You should see if the Mix Node is using the port you have changed in the config.toml file right after you run the node.
-
+-->
 ### What is `verloc` and do I have to configure my Nym Node to implement it?
 
 `verloc` is short for _verifiable location_. Mix Nodes and Gateways now measure speed-of-light distances to each other, in an attempt to verify how far apart they are. In later releases, this will allow us to algorithmically verify node locations in a non-fake-able and trustworthy manner.