walt node config <virtual-node> netsetup=[LAN|NAT] not applied #118
Labels
Comments
eduble
added a commit
that referenced
this issue
Sep 20, 2024
Changing `netsetup` configuration of a virtual node for allowing or disabling internet access was not applied. The user had to reboot the server or restart the main service as root, i.e., `systemctl restart walt-server` for this change to be applied. Actually the NAT rules were properly updated but the virtual node manager was not notified of the new "gateway" setting. This commit adds this notification. Fix #118.
eduble
added a commit
that referenced
this issue
Sep 20, 2024
Changing `netsetup` configuration of a virtual node for allowing or disabling internet access was not applied. The user had to reboot the server or restart the main service as root, i.e., `systemctl restart walt-server` for this change to be applied. Actually the NAT rules were properly updated but the virtual node manager was not notified of the new "gateway" setting. This commit adds this notification. Fix #118.
eduble
added a commit
that referenced
this issue
Sep 24, 2024
Changing `netsetup` configuration of a virtual node for allowing or disabling internet access was not applied. The user had to reboot the server or restart the main service as root, i.e., `systemctl restart walt-server` for this change to be applied. Actually the NAT rules were properly updated but the virtual node manager was not notified of the new "gateway" setting. This commit adds this notification. Fix #118.
eduble
added a commit
that referenced
this issue
Oct 3, 2024
Changing `netsetup` configuration of a virtual node for allowing or disabling internet access was not applied. The user had to reboot the server or restart the main service as root, i.e., `systemctl restart walt-server` for this change to be applied. Actually the NAT rules were properly updated but the virtual node manager was not notified of the new "gateway" setting. This commit adds this notification. Fix #118.
eduble
added a commit
that referenced
this issue
Nov 19, 2024
Changing `netsetup` configuration of a virtual node for allowing or disabling internet access was not applied. The user had to reboot the server or restart the main service as root, i.e., `systemctl restart walt-server` for this change to be applied. Actually the NAT rules were properly updated but the virtual node manager was not notified of the new "gateway" setting. This commit adds this notification. Fix #118.
eduble
added a commit
that referenced
this issue
Mar 4, 2025
Changing `netsetup` configuration of a virtual node for allowing or disabling internet access was not applied. The user had to reboot the server or restart the main service as root, i.e., `systemctl restart walt-server` for this change to be applied. Actually the NAT rules were properly updated but the virtual node manager was not notified of the new "gateway" setting. This commit adds this notification. Fix #118.
eduble
added a commit
that referenced
this issue
Mar 6, 2025
Changing `netsetup` configuration of a virtual node for allowing or disabling internet access was not applied. The user had to reboot the server or restart the main service as root, i.e., `systemctl restart walt-server` for this change to be applied. Actually the NAT rules were properly updated but the virtual node manager was not notified of the new "gateway" setting. This commit adds this notification. Fix #118.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Changing
netsetupconfiguration of a virtual node for allowing or removing internet access is not applied unless rebooting the server or callingsystemctl restart walt-server.Thanks to @sandikkaya for reporting.
The text was updated successfully, but these errors were encountered: