It causes the issue with no qos config after update (from 1.3.5)
Before migration
set traffic-policy shaper-hfsc SHAPE-10mbit bandwidth '400mbit' set traffic-policy shaper-hfsc SHAPE-10mbit class 10 linkshare m2 '200mbit' set traffic-policy shaper-hfsc SHAPE-10mbit class 10 match MARK mark '10' set traffic-policy shaper-hfsc SHAPE-10mbit default linkshare m2 '200mbit'
Incorrect firewall setting block the communication
We agree not to implement this, at least in the proposed format.
Close it as wontfix.
Waiting for the stable release Release v2.20
In T5947#172846, @kevinrausch wrote:Well, it didn't start on 1.3.2, so I don't know how the empty leaf nodes could have disappeared over time.
Is there a way to force a full rewrite of the config.boot before attempting upgrades?
Your original config looks corrupted.
For example
Loopback entry:
loopback lo
Expected entry:
loopback lo {
}Which user are you expecting? Hows to check from which user container was started?
Any idea for CLI?
@kevinrausch I cannot reproduce it, all works fine.
before update
vyos@r1# run show conf com | match route6 set protocols static interface-route6 2001:db8::/64 next-hop-interface lo set protocols static table 10 interface-route6 2001:db8::/64 next-hop-interface tun0 set protocols static table 20 interface-route6 2001:db8::/64 next-hop-interface tun1 [edit] vyos@r1# [edit] vyos@r1# run show version
@Daya @trae32566 Is it not the issue anymore?
I'd tag it as wontfix
Domain name was never configured for FRR in our templates
r4# conf t r4(config)# domainname WORD This system's domain name r4(config)#
Seems fixed:
Before reboot:
set interfaces ethernet eth1 description 'LAN' set interfaces ethernet eth1 hw-id '52:54:00:04:33:2b' set interfaces ethernet eth1 vif 20 address 'dhcp' set interfaces ethernet eth1 vif 20 disable
Fixed for both VyOS 1.5-rolling-202401140026 and VyOS 1.4.0-rc2
I'm against this implementation. We agree do not use boolean values yes|no enable|disable on|off
It will add more mess than usefulness. Configuring features in 2-3 places is a bad idea!
What will be if I add "ssh server" ? Which port will it see? Does it allow all addresses to ssh? What sense in this rule?
The same goes for VRRP; which addresses will it use? Multicast/unicast?
And there are also questions about priorities and what to do it it is accepted via this feature and dropped by a regular firewall.
@Nova_Logic Describe what exactly you want to do
Policy and firewalling are possible now
vyos@r4# set firewall ipv4 input filter rule 10 inbound-interface name eth1.v10 [edit] vyos@r4# set policy route foo interface eth1.v10 [edit] vyos@r4#
@giga1699 it was merged on Dec 12, 2023 https://github.com/vyos/vyos-1x/commit/b149a386400c0f869654ac26b0fee2e7f1bbc282
after building 1.3.5 Built on: Mon 04 Dec 2023 21:36 UTC
Good practise add a set of the commands to reproduce
Thanks
Works fine
vyos@ci-router1:~$ cat /var/log/cloud-init-output.log Cloud-init v. 22.1-437-g3e026561-1~bddeb running 'init-local' at Tue, 16 Jan 2024 15:08:04 +0000. Up 17.93 seconds. Cloud-init v. 22.1-437-g3e026561-1~bddeb running 'init' at Tue, 16 Jan 2024 15:08:09 +0000. Up 21.96 seconds. ci-info: ++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++ ci-info: +--------+------+-----------------+---------------+--------+-------------------+ ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | ci-info: +--------+------+-----------------+---------------+--------+-------------------+ ci-info: | eth0 | True | 192.168.122.172 | 255.255.255.0 | global | 52:54:00:e3:4f:82 | ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | ci-info: | lo | True | ::1/128 | . | host | . | ci-info: +--------+------+-----------------+---------------+--------+-------------------+ ci-info: +++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++ ci-info: +-------+---------------+---------------+---------------+-----------+-------+ ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags | ci-info: +-------+---------------+---------------+---------------+-----------+-------+ ci-info: | 0 | 0.0.0.0 | 192.168.122.1 | 0.0.0.0 | eth0 | UG | ci-info: | 1 | 192.168.122.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U | ci-info: +-------+---------------+---------------+---------------+-----------+-------+ ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++ ci-info: +-------+-------------+---------+-----------+-------+ ci-info: | Route | Destination | Gateway | Interface | Flags | ci-info: +-------+-------------+---------+-----------+-------+ ci-info: | 1 | multicast | :: | eth0 | U | ci-info: +-------+-------------+---------+-----------+-------+ Cloud-init v. 22.1-437-g3e026561-1~bddeb running 'modules:config' at Tue, 16 Jan 2024 15:08:10 +0000. Up 23.28 seconds. Killed old client process Internet Systems Consortium DHCP Client 4.4.3-P1 Copyright 2004-2022 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/
Could you get the original 1.3.x config file copy to the 1.4 instance and load config? I tested 1.3.5 looks good
load path_to_config_1.3
It will be included after 1.4-rc2
Create a new feature request if you need some specific feature/features
For example, for offloads we use:
vyos@r4# set interfaces ethernet eth0 offload Possible completions: gro Enable Generic Receive Offload gso Enable Generic Segmentation Offload hw-tc-offload Enable Hardware Flow Offload lro Enable Large Receive Offload rfs Enable Receive Flow Steering rps Enable Receive Packet Steering sg Enable Scatter-Gather tso Enable TCP Segmentation Offloading
@greywolfe You probably need to use -e without_login=true option. Could you re-check?
To reproduce, we can use the interface description
1.3.5 in config file we see \\
vyos@r1# set interfaces ethernet eth1 description 'WAN\interface' [edit] vyos@r1# set interfaces ethernet eth0 description 'WAN\interface' [edit] vyos@r1# set interfaces ethernet eth1 description 'My\LAN interface|for lan | network' [edit] vyos@r1# compare [edit interfaces ethernet eth0] >description WAN\interface [edit interfaces ethernet eth1] +description "My\LAN interface|for lan | network" [edit] vyos@r1# commit [edit] vyos@r1# save Saving configuration to '/config/config.boot'... Done [edit] vyos@r1# run show conf com | match desc set interfaces ethernet eth0 description 'WAN\\\\interface' set interfaces ethernet eth1 description 'My\\LAN interface|for lan | network' [edit] vyos@r1#
After update to 1.4-rc1+
vyos@r1:~$ show conf com | match desc set interfaces ethernet eth0 description 'WAN\\\\\\\\interface' set interfaces ethernet eth1 description 'My\\LAN interface|for lan | network' vyos@r1:~$
@greywolfe could you re-check? There were several fixes for ddclient.
@greywolfe Could you re-check?
If you can reproduce it, describe please in more detail, which flavor/platform/version
Merged
Removed
Merged
The best option for now would be to delete those commands and re-implement them in a separate feature request if required.
https://github.com/vyos/vyatta-op/tree/current/templates/show/remote-config
@fdcastel The thing is, we don't have secrets_lines in the dictionary.
So, it is a wholly broken script and must be deleted or rewritten.
In T5932#172324, @marc_s wrote:I take it RC2 will contain these new versions @Viacheslav?
Do static addresses/gateways work stable enough?
Always use "set commands" to make it easier for developers to reproduce it.