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?

Why is this closed? If you don't want the functionality, fine, but don't leave broken functionality in the installer....at least take it out so you're not confusing your users when it doesn't work.

outdated

outdated, no follow ups

limitations of old backend
may come back to this later after new backend live

Updated link https://github.com/vyos/vyatta-cfg-quagga/blob/2fa0f52e45f4491b760cf03e72c871020492dfb7/templates/protocols/ospf/passive-interface/node.def#L29-L35

this was solved in the latest versions of 1.2
config is now sticky to what VMWarew reports

@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.

We will not update FRR to 8.x for 1.3 LTS releases.

Closed for 1.3 too, because FRR version used in 1.3 doesn't support the feature

@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

@zsdc was this ever backported to 1.3?

@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