external works for me, can you re-check?
vyos@r5-roll:~$ show ip ospf database external 10.20.40.0
external works for me, can you re-check?
vyos@r5-roll:~$ show ip ospf database external 10.20.40.0
Can be cherry-picked for equuleus and crux
@craterman Will be fixed in the next rolling release, can you check it tomorrow?
NTP doesn't work when you configure listen-address 0.0.0.0.
@tuxis-ie
FRR doesn't allow you to set that value. It's not a bug of VyOS.
In commands description allowed values (0-4294967295)
r12-1.2.6(config)# route-map FOO permit 100 r12-1.2.6(config-route-map)# set local-preference (0-4294967295) Preference value r12-1.2.6(config-route-map)# set local-preference (0-4294967295) Preference value r12-1.2.6(config-route-map)# set local-preference -10 % Unknown command: set local-preference -10
Proposed CLI
set interfaces tunnel tun0 parameters ip disable-pmtu-discovery
Similar task T2045
@jack9603301 if you mean option "--clamp-mss-to-pmtu" so it was in wrong chain/hook T2868
Fix typo in script description
PR https://github.com/vyos/vyos-1x/pull/663
I got this when several times change boot with
set system image default-boot
1.2.6 => 1.3 => 1.2.6 => 1.3
I successfully update the image from 1.2.6-s1 to VyOS 1.3-rolling-202012231522
The main problem is that you use the same name for different group types.
@tjh How you want to integrate it with CLI or use it as a separate pkg?
@robertoberto Can you provide next commands?
show interfaces ethernet eth0 physical sudo ethtool -k eth0 | grep offload
@primoz What are the benefits?
PR for crux https://github.com/vyos/vyos-build/pull/138
It's FRR logic.
It was deleted/deprecated in T1990
@vlesk Will be fixed in the next rolling release.
Can you check the release after 10 Dec?
vyos@r11# set interfaces vti vti2 ?
To reproduce
set interfaces vti vti2 address '10.0.0.1/30' set interfaces vti vti2 description 'Tunnel to 100.64.0.2'
PR for fixing bgp template (prefix-list) and add the ability to use updated frr.py framework functions.
Not sure that it makes sense to downgrade the image from 1.3 to 1.2.
Because there are also no migration "downgrade" scripts.
I propose to add an additional check and disable downgrade images for "add system image".
Still old format for completion help
PR https://github.com/vyos/vyos-1x/pull/632
fix regex in smoketest.
maybe it happened after that commit https://github.com/vyos/vyos-1x/commit/c87ad948999c28c3c9449f98d60b545481ea29d5
because it was work in VyOS 1.3-rolling-202011250217
Perhaps replace config (from_re "interface" | from_re "isis *") delete also and route-maps/prefix-lists from FRR configuration.
https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/protocols_isis.py#L121
Before update
@c-po It's mean all NOT ports. If you want to drop not 22,23,24,25
Fixed.
Fixed
set nat source rule 1000 outbound-interface 'eth1' set nat source rule 1000 source address '203.0.113.1-203.0.113.4' set nat source rule 1000 translation address '10.0.0.1-10.0.0.4' vyos@r5# commit [ nat ] Warning: IP address 10.0.0.1 does not exist on the system! Warning: IP address 10.0.0.4 does not exist on the system!
@jjakob can you check the latest rolling?
This probably happens at this stage.
https://github.com/vyos/vyatta-cfg-system/blob/current/scripts/install/install-image-existing#L217-L224
It seems a wrong logic.
We want that option to have an effect on "local" and "forward" directions, so we use table mangle and "PREROUTING" and VYATTA_FW_IN_HOOK hook
Generated rules
@olofl Can you check the latest rolling release? Are all logs sent correctly?