Today the sequence starts at 1 and use 1 as spacing.
This becomes somewhat tricky to insert new rules in a filter.
Suggestion to alter default to start at 10 and use 10 as spacing example:
Before:
```
set firewall ipv4 forward filter default-action 'accept'
set firewall ipv4 forward filter rule 1 action 'drop'
set firewall ipv4 forward filter rule 1 state invalid 'enable'
set firewall ipv4 forward filter rule 2 action 'accept'
set firewall ipv4 forward filter rule 2 state established 'enable'
set firewall ipv4 forward filter rule 3 action 'accept'
set firewall ipv4 forward filter rule 3 state related 'enable'
```
After:
```
set firewall ipv4 forward filter default-action 'accept'
set firewall ipv4 forward filter rule 10 action 'drop'
set firewall ipv4 forward filter rule 10 state invalid 'enable'
set firewall ipv4 forward filter rule 20 action 'accept'
set firewall ipv4 forward filter rule 20 state established 'enable'
set firewall ipv4 forward filter rule 30 action 'accept'
set firewall ipv4 forward filter rule 30 state related 'enable'
```
This could be achieved by adding this command (where "10 10" would be default):
```
set firewall ipv4 input filter resequence 10 10
```
* start_num Sequence number assigned to the first rule. Default is 10.
* inc_num Numeric interval between consecutive rules. Default is 10.
Where if I use:
```
set firewall ipv4 input filter resequence 100 20
```
the result would become:
```
set firewall ipv4 forward filter default-action 'accept'
set firewall ipv4 forward filter rule 100 action 'drop'
set firewall ipv4 forward filter rule 100 state invalid 'enable'
set firewall ipv4 forward filter rule 120 action 'accept'
set firewall ipv4 forward filter rule 120 state established 'enable'
set firewall ipv4 forward filter rule 140 action 'accept'
set firewall ipv4 forward filter rule 140 state related 'enable'
```
This would match "how others do it" such as Arista.
Ref:
https://www.arista.com/en/um-eos/eos-acls-and-route-maps#xx1151287