Closed in favour of T4107 - use "default-information originate"

@NikolayP Change it https://github.com/vyos/vyatta-cfg-firewall/blob/1e06e3f891f8238d565ff0eddb4cd8c9b6032346/templates/firewall/name/node.tag/rule/node.def#L5-L9 to the required range.

According to FRR developer this seems to be intentional

this requires a helper that will be responsible for the DNS resolution and update of the corresponding rules
each DNS resolution will refresh IPs every 15 seconds or in smart mode will rely on DNS TTL for records and will do a lookup on TTL expire (and update firewall if required)

Runtime error on the development image

• current https://github.com/vyos/vyatta-op/pull/50
• equuleus https://github.com/vyos/vyatta-op/pull/51

Interestingly if vyos-configd is in use this bug is triggered. If vyos-configd is not used the bug is not triggered :/

Feels like an FRR issue, bug opened: https://github.com/FRRouting/frr/issues/10263

https://github.com/vyos/vyatta-nat/commit/01b9a8598dabd391cc42da4c66d7a8067846b12b

This happened because the rule numbers only got increased in the XML implementation but not in the old Perl backend. This has been fixed.

In 1.3.0 the limitation remains

PR for 1.3 https://github.com/vyos/vyos-1x/pull/1120

Using a space in description withput quotation won‘t work. This is because the underlay of the CLI is bash and needs proper quotation.

@Viacheslav
If i use this format ('test test test') it works well.
Is it possible using description with space without '' ?

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

Forgot about the process "vyos-http-api-server". The process must be launched in the required vrf. Otherwise, we get an error: Otherwise, we get an error:

If anyone actually wants support for source port parameter, feel free to reopen this, but the interface parameter is a no-go. In the meantime, rewriting vyatta-config-mgmt takes precedence.

That's a good idea. What remains in that repo was hardly touched in a decade.

I prefer to rewrite the whole https://github.com/vyos/vyatta-config-mgmt to XML/python

A similar bug I see in 1.2 with such configuration:

set service snmp contact 'test'
set service snmp listen-address 192.168.122.12
set service snmp location 'test'
set service snmp v3 user foo auth encrypted-key '0x2e312e332e362e312e362e332e31302e312e322e34'
set service snmp v3 user foo auth type 'sha'
set service snmp v3 user foo privacy encrypted-key '0x'
set service snmp v3 user foo privacy type 'aes'

Thank you, problem solved!

Working in latest release: