I've summited an issues case on FRR , where explain the problematic :

as stated before, in 1.4 now it's possible to specify corresponding interface.

@zoenan7 thanks for getting back to me
it looks like it is now fixed in upstream so I will close this ticket

Bug introduced in 1.3.x with upgrade of FastAPI framework in:
https://vyos.dev/T5176

Yes; it was not evident in 1.3.x until the upgrade of the FastAPI framework for
https://vyos.dev/T5176
and will be backported.

I did not report it to the upstream, but another vendor helped me to report it to the upstream and gave me the relevant CVE number. You can check the following link about netsnmp: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016139

PR in firewall refactor: https://github.com/vyos/vyos-1x/pull/2016

It seems to work fine (VyOS 1.4-rolling-202307120317).

vyos@r14# set interfaces ethernet eth1 description 123
[edit]
vyos@r14# commit
[edit]
vyos@r14# compare 1
[interfaces ethernet eth1]
+ description "123"

VyOS 1.3.3 Still have such an issue. Any plan to fix it on VyOS 1.3?

@syncer Will address this after T5160 is merged

PR: https://github.com/vyos/vyos-1x/pull/2087

PR:
https://github.com/vyos/vyos-1x/pull/2086

@zsdc thanks for the detailed explanation; @Viacheslav confirmed this is the case on update, and I will adopt your suggestion.

I'm marking this task as resolved, since it's been in 'Needs Testing' status for more than 6 months

I'm marking this task as resolved, since it's been in 'Needs Testing' status for more than 6 months.

@icyfire0573 Can you re-check if nat op-mode commands works for you?

Marking as invalid, since firewall cli should move to a more organized and flexible cli strycture.

Thanks, @dex, agreed that this is misleading: this will be refined once the PR
https://github.com/vyos/vyos-1x/pull/2079
is merged.

@zoenan7 have you managed to report to upstream?

PR https://github.com/vyos/vyos-1x/pull/2084

@sdev, so what is the state of this?

Closing this task since it has been in "Needs Testing" status for more than one year, for both 1.3 and 1.4 projects.

Once we move to new firewall and re-work on mangle/PBR, this could be achieved easily.

Working on latest build:

As said in previous comments, login banner is available, both on 1.3 and 1.4
I think this task can be marked as resolved

Possible duplicate? https://vyos.dev/T4190

Perhaps this request should be moved to the forums or somewhere a sysadmin can be reached for assistance?

well , I've had an idea how to make a workaround , I've used explicit-null label to add next-hop from the network-address connected sudo ip route add 10.0.0.1/32 encap mpls 0 via 10.0.0.2 dev eth1

I've done extra test , I confirm this behavior is associated transport label that can't be allocated when using interfaces directed connected to created ldp session without IGP protocols(ospf/isis) . let's see what is going on :

Jump action is available in 1.4
Then, I'm setting this task as resolved

There are several issues mentioned in this task so far, and they will be separated out to respective tasks. Firstly, we will address an obvious bug in the implementation that misnumbers entries in the commit log compared to archived commit files ...

During installation, this happens: https://github.com/vyos/vyatta-cfg-system/blob/bac61854acd40b4eae8b12e47be54306171f5c3c/scripts/install/install-image-existing#L201C3-L201C3