Fixed
vyos@r1# set interfaces ethernet eth1 description test [edit] vyos@r1# time commit
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Jan 19 2024
Jan 19 2024
IGMP was migrated to PIM https://github.com/vyos/vyos-1x/commit/383231dae8c01ea58d0c956688ecd87f739be97e
Viacheslav changed the status of T5543: Fix source address handling in static joins from Unknown Status to Resolved.
Viacheslav changed the status of T3871: Resolve unexpected interface name reordering from In progress to Needs testing.
Impossible with FRR
r1# conf t r1(config)# no ipv6 prefix-list PUB seq 10 permit 2001:db8::/32 le % Command incomplete: no ipv6 prefix-list PUB seq 10 permit 2001:db8::/32 le r1(config)#
@carl.byington Could you re-check? is it fixed?
Viacheslav changed the status of T3403: Error on interrupting list of pppoe sessions from Resolved to Not Applicable.
Viacheslav changed the status of T3403: Error on interrupting list of pppoe sessions from Unknown Status to Resolved.
Viacheslav changed the status of T3159: L2TP MTU mismatch between client and server from Open to Needs reporter action.
If the problem exists, it should be fixed on accel-ppp site.
I am not sure that I can help here as it is written on C
1.3.5 fixed
vyos@r1:~$ reset vpn remote-access user Possible completions: <text> Terminate specified users current remote access VPN session(s)
Create a new task and provide links and examples for the KEA-DHCP-server implementation if it is supported.
ISC-DHCP-server is deprecated.
Viacheslav closed T1620: Leases in "show dhcp server leases" lose Pool and Hostname after some time as Wontfix.
ISC-DHCP is deprecated, and we do not expect new updates.
The 1.5 is migrated to KEA-DHCP
Close it as wontfix
Use the persist option as after each interface, recreation indexes are created dynamically.
Since it didn't function properly in either Quagga or FRR...
I suggest addressing this issue to the upstream codebase, as we currently do not maintain SNMP MIBs. Your attention to this matter would be greatly appreciated.
Viacheslav closed T1199: SNMP BGP4-MIB: bgp4PathAttrCalcLocalPref and bgp4PathAttrLocalPref filled incorrectly as Wontfix.
Since it didn't function properly in either Quagga or FRR...
I suggest addressing this issue to the upstream codebase, as we currently do not maintain SNMP MIBs. Your attention to this matter would be greatly appreciated.
@olofl Open the task with a new actual description and examples for nftables.
Both links are unreachable
Viacheslav edited projects for T1810: Commit to add new l2tp local user shouldn't disconnect all current l2tp sessions, added: VyOS 1.5 Circinus; removed VyOS 1.3 Equuleus (1.3.6), VyOS 1.4 Sagitta.
Viacheslav changed the status of T5963: QoS policy shaper rate calculations could be wrong for some ethernet devices, a subtask of T4284: QoS: rewrite to XML and Python, from Open to Needs testing.
Viacheslav changed the status of T5963: QoS policy shaper rate calculations could be wrong for some ethernet devices from Open to Needs testing.
Viacheslav updated the task description for T5961: QoS policy shaper vif with ceiling fails on commit.
Viacheslav added a comment to T5962: QoS policy set default speed to 100mbit or 1gbit instead of 10mbit.
Viacheslav renamed T5963: QoS policy shaper rate calculations could be wrong for some ethernet devices from QoS policy shaper rate calculations with percent could be wrong for some ethernet devices to QoS policy shaper rate calculations could be wrong for some ethernet devices.
Viacheslav updated the task description for T5963: QoS policy shaper rate calculations could be wrong for some ethernet devices.
Viacheslav triaged T5963: QoS policy shaper rate calculations could be wrong for some ethernet devices as High priority.
Viacheslav triaged T5962: QoS policy set default speed to 100mbit or 1gbit instead of 10mbit as Normal priority.
Viacheslav added a parent task for T5750: Upgrade from 1.3.4 to 1.4 Rolling fails QoS: T5938: Migration fail root task for 1.4-rc.
Viacheslav added a parent task for T5961: QoS policy shaper vif with ceiling fails on commit: T5938: Migration fail root task for 1.4-rc.
Viacheslav updated the task description for T5961: QoS policy shaper vif with ceiling fails on commit.
Viacheslav updated the task description for T5961: QoS policy shaper vif with ceiling fails on commit.
Jan 18 2024
Jan 18 2024
Viacheslav closed T905: The command show remote-config does not work for remote-platform openvpn as Resolved.
Deprecated commands are deleted.
It should be reimplemented if it is needed in a separate feature request/task
PR https://github.com/vyos/vyos-1x/pull/2852 basic implementation
Viacheslav changed the status of T5958: QoS policy shaper-hfsc is not implemented, a subtask of T4284: QoS: rewrite to XML and Python, from Open to In progress.
Viacheslav changed the status of T5958: QoS policy shaper-hfsc is not implemented from Open to In progress.
Viacheslav changed the status of T5957: Firewall fails to delete inbound-interface name from Needs reporter action to Confirmed.
Let's not close it now, as we do not fully understand the cause
Expecting minimal working config:
set qos policy shaper-hfsc SHAPE bandwidth '400mbit' set qos policy shaper-hfsc SHAPE class 10 linkshare m2 '200mbit' set qos policy shaper-hfsc SHAPE class 10 match DST ip destination address '192.0.2.1/32' set qos policy shaper-hfsc SHAPE default linkshare m2 '111mbit'
Viacheslav added a subtask for T4284: QoS: rewrite to XML and Python: T5958: QoS policy shaper-hfsc is not implemented.
Viacheslav added a parent task for T5958: QoS policy shaper-hfsc is not implemented: T4284: QoS: rewrite to XML and Python.
Viacheslav changed the status of T5927: QoS policy shaper-hfsc class does not have a `bandwidth` node but requires one in the check, a subtask of T5938: Migration fail root task for 1.4-rc, from Open to In progress.
Viacheslav changed the status of T5927: QoS policy shaper-hfsc class does not have a `bandwidth` node but requires one in the check from Open to In progress.
Viacheslav added a comment to T5927: QoS policy shaper-hfsc class does not have a `bandwidth` node but requires one in the check.
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'
Viacheslav changed the status of T5957: Firewall fails to delete inbound-interface name from Open to Needs reporter action.
Incorrect firewall setting block the communication
Viacheslav closed T5509: Add capability to add firewall rules similar to CoPP through VyOS configuration as Wontfix.
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?
Jan 17 2024
Jan 17 2024
Your original config looks corrupted.
For example
Loopback entry:
loopback lo
Expected entry:
loopback lo {
}Viacheslav changed the status of T5941: [1.3.5 -> 1.4.0-RC1 Migration] Orphaned Configuration Nodes Cause Issues, a subtask of T5938: Migration fail root task for 1.4-rc, from Open to Needs testing.
Viacheslav changed the status of T5941: [1.3.5 -> 1.4.0-RC1 Migration] Orphaned Configuration Nodes Cause Issues from Open to Needs testing.
Which user are you expecting? Hows to check from which user container was started?
Any idea for CLI?
Viacheslav renamed T5954: Enable nvme_hwmon and drivetemp in KERNEL from Enable nvme_hwmon and drivetemp to Enable nvme_hwmon and drivetemp in KERNEL.
Viacheslav triaged T5947: [1.3.2 -> 1.4.0-RC1 Migration] Static ipv6 routes dropped as Normal priority.
Viacheslav changed the status of T5947: [1.3.2 -> 1.4.0-RC1 Migration] Static ipv6 routes dropped, a subtask of T5938: Migration fail root task for 1.4-rc, from Open to Needs testing.
Viacheslav changed the status of T5947: [1.3.2 -> 1.4.0-RC1 Migration] Static ipv6 routes dropped from Open to Needs testing.
@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
Viacheslav added a comment to T1641: VRRP conntrack-sync dropping packets passing through the router.
@Daya @trae32566 Is it not the issue anymore?
I'd tag it as wontfix
Viacheslav lowered the priority of T2004: BGP FQDN capability not sending domain name from High to Normal.
Domain name was never configured for FRR in our templates
r4# conf t r4(config)# domainname WORD This system's domain name r4(config)#
Viacheslav closed T2163: Disabled vif interface with "address dhcp" requests DHCP address as Not Applicable.
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
Viacheslav closed T4425: Hide DHCP leases from interfaces without active DHCP client as Not Applicable.
Fixed for both VyOS 1.5-rolling-202401140026 and VyOS 1.4.0-rc2
Viacheslav closed T5932: 1.4-rolling-202304120317 to 1.4.0-rc1: dynamic dns migration fail, a subtask of T5938: Migration fail root task for 1.4-rc, as Resolved.
Viacheslav closed T5932: 1.4-rolling-202304120317 to 1.4.0-rc1: dynamic dns migration fail as Resolved.
Viacheslav added a comment to T5509: Add capability to add firewall rules similar to CoPP through VyOS configuration.
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.
Viacheslav added a comment to T4488: allow manual configuration changes of interfaces created by high-availability with rfc3768-compatibility option .
@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
Viacheslav changed the status of T5935: ddclient tries to bind to Ethernet VIFs before they're configured on boot from Open to In progress.
Viacheslav added a comment to T5948: pdns-recursor crashes on restart if hostfile-update is enabled and dhcp client sends hostname with trailing dot.
Good practise add a set of the commands to reproduce
Thanks
Jan 16 2024
Jan 16 2024
Viacheslav closed T5889: Migration NAT 5-to-6 bug, a subtask of T5907: cloud-init root task for 1.5 and 1.4 , as Resolved.
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/
Viacheslav changed the status of T5889: Migration NAT 5-to-6 bug, a subtask of T5907: cloud-init root task for 1.5 and 1.4 , from In progress to Needs testing.
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
Viacheslav changed the status of T5889: Migration NAT 5-to-6 bug, a subtask of T5907: cloud-init root task for 1.5 and 1.4 , from Open to In progress.
Viacheslav renamed T5889: Migration NAT 5-to-6 bug from Cloud-Init not processing user data correctly NAT to Migration NAT 5-to-6 bug.