Ensure Gateway IP Resides in the Same Subnet as Node's IP

[Mahmoud-Emad]

Description

The gateway must reside within the same IP range (subnet) as the node's IP address to facilitate proper routing. This ensures that the node can effectively communicate and route its traffic through the designated gateway.

Changes

• A new validation rule has been added to ensure that the gateway IP address is within the same subnet as the node's IP address. This validation is applied based on the IP version (IPv4 or IPv6).
• A new validation rule has been added to verify whether the provided IPv4 address is public or private.
• A new validation rule has been added to verify whether the provided IPv6 address is public or private.

Related Issues

• 🐞 [Bug]: Node public config validation isn't consistent with the tfchain validation  #2637

Screenshots

• 
• 
• 
• 
• 

Checklist

• Tests included
• Build pass
• Documentation
• Code format and docstrings
• Screenshots/Video attached (needed for UI changes)

[zaelgohary]

I tried adding invalid data and the validation didn't work.

[Mahmoud-Emad]

I tried adding invalid data and the validation didn't work.

There is a validation on the chain that may validate the prefix length. The value '0' you sent is not valid. This scenario is covered.

Also, the error message has been updated to be user-readable, and I have logged the actual error from the chain in the console/logger for developer investigations.

[zaelgohary]

Also, the error message has been updated to be user-readable, and I have logged the actual error from the chain in the console/logger for developer investigations.

Do we really need to show the error to the user twice? I think the toast is enough. If the user wants to copy it, he can get it from the logs.

[Mahmoud-Emad]

Also, the error message has been updated to be user-readable, and I have logged the actual error from the chain in the console/logger for developer investigations.

Do we really need to show the error to the user twice? I think the toast is enough. If the user wants to copy it, he can get it from the logs.

The toast message stays on the screen for about 5 seconds before disappearing. I included the alert so that users have enough time to read any error messages without feeling rushed.

Consider this scenario: you press "save," and then glance at your phone for a minute. When you look back, you notice that the public configuration wasn't added, and no errors had disappeared. This is the reason for the alert. Either way, I'll remove it now.