It seems issues with migrations
[ OK ] Reached target cloud-init.target - Cloud-init target. [ 28.675603] vyos-router[1767]: Waiting for NICs to settle down: settled in 0sec.. [ 31.572854] vyos-router[1767]: Mounting VyOS Config...done. [ 42.670126] vyos-router[1767]: Starting VyOS router: migrate configure failed! [ 43.268753] vyos-config[1773]: Configuration error
Add please the simple examples with set of commands to reproduce
set xxxx x.x.xx
The same issue could be with any dynamic interface like PPP that could be don't exists during the boot process/ISP issues
Which version?
It is more of a question for Jool.
Or you can use a range of required ports that aren't used by the system
PR https://github.com/vyos/vyos-1x/pull/2724
vyos@r4:~$ add system image latest
Initially we added it only for 1.3 cloudwatch https://github.com/vyos/vyos-build/pull/206/files
I'll leave this here T4541
In T3476#168872, @eronlloyd wrote:This is exciting! Is there a public endpoint available for testing this yet? GitHub is rejecting requests on that URL:
Connecting error: HTTPSConnectionPool(host='raw.githubusercontent.com', port=443): Max retries exceeded with url: /vyos/vyos-rolling-nightly-builds/main/version.json (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f916bdb2f90>: Failed to establish a new connection: [Errno 16] Device or resource busy'))
Update not found
Example of usage for 1.5
vyos@r4:~$ vyos@r4:~$ show conf com | match upd set system update-check auto-check set system update-check url 'https://raw.githubusercontent.com/vyos/vyos-rolling-nightly-builds/main/version.json' vyos@r4:~$ vyos@r4:~$ vyos@r4:~$ show system updates Current version: 1.5-rolling-202312220023
vyos@r4:~$ vyos@r4:~$ show conf com | match upd set system update-check auto-check set system update-check url 'https://raw.githubusercontent.com/vyos/vyos-rolling-nightly-builds/main/version.json' vyos@r4:~$ vyos@r4:~$ vyos@r4:~$ show system updates Current version: 1.5-rolling-202312220023
@indrajitr Could you take a look? As I remember you are working on it.
On the newest system you can use load /path/to/config
The same task T5712
In T160#168646, @danielpo wrote:That's great!
I tried running make interface_definitions in vyos-1x and copy in the changed files into my vyos install, but the files kept disappearing when rebooting, and couldn't figure out how to build an iso with your vyos 1-x repo.So I wil try it when there is a vyos rolling iso available.
PR https://github.com/vyos/vyos-1x/pull/2677
set interfaces ethernet eth0 address '192.168.122.14/24' set interfaces ethernet eth0 address '192.168.122.10/24' set interfaces ethernet eth2 address '2001:db8::1/64'
Has the interface index changed?
Also I found this log
It binds port 647
set interfaces dummy dum8765 address '192.0.2.1/24'
After update it cannot pass the smoketest
vyos@r4:~$ /usr/libexec/vyos/tests/smoke/cli/test_service_dhcp-server.py test_dhcp_exclude_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_in_range) ... ok test_dhcp_exclude_not_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_not_in_range) ... ok test_dhcp_failover (__main__.TestServiceDHCPServer.test_dhcp_failover) ... FAIL test_dhcp_multiple_pools (__main__.TestServiceDHCPServer.test_dhcp_multiple_pools) ... ok test_dhcp_relay_server (__main__.TestServiceDHCPServer.test_dhcp_relay_server) ... ok test_dhcp_single_pool_options (__main__.TestServiceDHCPServer.test_dhcp_single_pool_options) ... ok test_dhcp_single_pool_range (__main__.TestServiceDHCPServer.test_dhcp_single_pool_range) ... ok test_dhcp_single_pool_static_mapping (__main__.TestServiceDHCPServer.test_dhcp_single_pool_static_mapping) ... ok
Cannot pass smoketest
vyos@r4:~$ /usr/libexec/vyos/tests/smoke/cli/test_service_dhcp-server.py test_dhcp_exclude_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_in_range) ... ok test_dhcp_exclude_not_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_not_in_range) ... ok test_dhcp_failover (__main__.TestServiceDHCPServer.test_dhcp_failover) ... FAIL test_dhcp_multiple_pools (__main__.TestServiceDHCPServer.test_dhcp_multiple_pools) ... ok test_dhcp_relay_server (__main__.TestServiceDHCPServer.test_dhcp_relay_server) ... ok test_dhcp_single_pool_options (__main__.TestServiceDHCPServer.test_dhcp_single_pool_options) ... ok test_dhcp_single_pool_range (__main__.TestServiceDHCPServer.test_dhcp_single_pool_range) ... ok test_dhcp_single_pool_static_mapping (__main__.TestServiceDHCPServer.test_dhcp_single_pool_static_mapping) ... ok
@danielpo marking IPv6 packet is possible
set policy route6 PBR6 interface 'eth1' set policy route6 PBR6 rule 100 set mark '4' set policy route6 PBR6 rule 100 source address '2001:db8::/64'
Some users have issues https://forum.vyos.io/t/grub-menu-fails-to-load-on-serial-only-devices-with-no-kvm/
Not reproduced in 1.3.5
vyos@r1# set service https vrf foo
[edit]
vyos@r1# commit
[edit]
vyos@r1# del service https vrf foo
[edit]
vyos@r1# commit
[edit]
vyos@r1# curl -k --location --request POST 'https://localhost/retrieve' --form data='{"op": "showConfig", "path": ["system", "ip"]}' --form key='foo'
{"success": true, "data": {"arp": {"table-size": "32768"}}, "error": null}[edit]
vyos@r1#
[edit]
vyos@r1# run show ver@SrividyaA could you re-check and close it?
@zsdc Can we backport it?
It won't be implemented for 1.3.x due to old backend
Implemented in 1.4-1.5 T5248
Implemented
vyos@r1# set system option root-partition-auto-resize [edit] vyos@r1# run show ver
You can use policy local-route to archive your goals
There is no way to use eth1v1 for the policy route (rewritten for 1.4/1.5)
Fixed
vyos@r1# set interfaces ethernet eth2 description foo [edit] vyos@r1# set interfaces ethernet eth2 mtu 1200 [edit] vyos@r1# commit [ interfaces ethernet eth2 ] link-local IPv6 address will be configured on interface "eth2", the required minimum MTU is 1280!
Close it, as it is not bug/feature
@zsdc Can we close it?
Fq_codel was added for 1.4/1.5 in T5489
Not planning to do it for 1.3 now
Not sure if Jool supports it.
As I understand, it is better to have a separate address for translations, otherwise, you should define ports for 64 translations. If you set 1-65535 for the "main" address, you will lose connections and can't use those ports for the system (they will be available only for translations)
Jool uses its own bib table instead of conntrack to manage nat mappings.
So you should add a separate pool only for translations.
@w4 could you provide some links or retest? Which patches?
The bug is not clear.
Should be fixed in T5817
Could you re-check?
Done for 1.4/1.5 https://github.com/vyos/vyos-1x/tree/current/python/vyos/utils
It won't be implemented for 1.3 as we risk breaking something.
Firstly, this bug should be fixed T5837
@zsdc Can we close it?