Proposal: Adding setorder Keyword for Ordered IP Configuration

Gadi denny Agussy Krupa Raju gkruparaju at msystechnologies.com
Tue Jun 4 11:25:44 UTC 2024


Feature URL <https://github.com/FRRouting/frr/issues/15464>

Hi everyone,
We'd like to propose the addition of a new keyword, "setorder", to the IP
address configuration command. This keyword would allow users to specify
the order in which IP addresses are applied to an interface, ensuring
consistent behavior regardless of the order they are entered.

*Motivation*
Currently, the order in which IP addresses are configured on an interface
can potentially impact functionality in some scenarios. With setorder,
users can define a clear and predictable order for IP usage, eliminating
this potential source of inconsistency.

*Proposed Solution*
The setorder keyword would be added as an optional parameter to the IP
address configuration command. It would accept an integer value
representing the desired order for that specific IP address. Lower values
indicate a higher priority.

*Example Configuration*
R1# interface eth3
R1# ip address 89.A.B.2/32 setorder 5
R1# ip address 10.100.2.1/32 setorder 6
R1# ip address 16.16.2.1/32 setorder 3
R1# ip address 83.83.2.6/32
R1# ip address 63.63.2.6/32

In this example, the IP addresses would be applied in the following order
(ascending setorder value):
16.16.2.1/32 (setorder 3)
89.A.B.2/32 (setorder 5)
10.100.2.1/32 (setorder 6)
The remaining two IP addresses (without setorder) would retain their
current behavior.

*Expected Output (After FRR Reload)*
interface eth3
ip address 16.16.2.1/32 setorder 3
ip address 89.A.B.2/32 setorder 5
ip address 10.100.2.1/32 setorder 6
ip address 83.83.2.6/32
ip address 63.63.2.6/32

Is the proposed setorder solution acceptable for achieving predictable IP
address order on interfaces? If not, please provide details on any concerns
or alternative approaches you may have.

Thanks
Denny Agussy

-- 


****** DISCLAIMER - MSysTechnologies LLC ******

 

This email message, 
contents and its attachments may contain confidential, proprietary or 
legally privileged information and is intended solely for the use of the 
individual or entity to whom it is actually intended. If you have 
erroneously received this message, please permanently delete it immediately 
and notify the sender. If you are not the intended recipient of the email 
message,you are notified strictly not to disseminate,distribute or copy 
this e-mail.E-mail transmission cannot be guaranteed to be secure or 
error-free as Information could be intercepted, corrupted, lost, destroyed, 
incomplete or contain viruses and MSysTechnologies LLC accepts no liability 
for the contents and integrity of this mail or for any damage caused by the 
limitations of the e-mail transmission.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20240604/6937331c/attachment.htm>


More information about the dev mailing list