PR for Equuleus: https://github.com/vyos/vyos-1x/pull/2776
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 9 2024
Warning would be much better because it would solve the problem.
When you have the image already loaded and the system was rebooted, the image should still exist and therefore the user/pass is not required (for the moment).
There could be another bug related T5407
I guess we should not Raise config but use the Warning here https://github.com/vyos/vyos-1x/blob/864524ba86b0a4d57ab64d6e9398c3fd5eb2fce4/src/conf_mode/container.py#L405-L408
Viacheslav suggested the following change which worked for me:
I replied to jestabro via email a couple of hours back, but noticed that it didn't show up here. For the benefit of anybody else interested in this bug I'm cutting and pasting the email below:
Jan 8 2024
PR for VyOS 1.4 https://github.com/vyos/vyos-1x/pull/2774
Well, the webserver is for an API - if you wan't to server files you can either use the default document root, or spawn a container. We should focus on packet pushing and administration.
I suppose with the new firewall implementation, this is no longer relevant.
With the migration to nftables, I suppose this is not relevant anymore.
With the current smoke test infrastructure, I'm inclined to call the original task resolved.
I presume the issue is no longer relevant since people do successfully use QAT now, but feel free to reopen if anything.
Just to clarify the issue: note that one can specify the choice of serial console during the 'install image' process; are you not seeing the boot messages with this setting ? or are you unable to set it during installation ? Thanks.
Now that 1.4 is about to be released and 1.3 going into maintenance mode, we definitely will not include it in 1.3.6.
User creation works fine now.
Yes.
The same problem (container config does not get loaded) occurs, when DNS is not available for whatever reason.
This must not prevent the current container settings to be online.
I think I found the problem.
The first thing could be that the container cannot connect to the registry as it happens before static routing (not sure).
vyos@r4# /opt/vyatta/sbin/priority.pl | match "container|static" 450 container 480 protocols/static 481 vrf/name/node.tag/protocols/static [edit] vyos@r4#
Thanks Viacheslav
Ok the file does not have the Release version in config and migration do anyway
https://github.com/vyos/vyos-vm-images/blob/current/roles/install-config/templates/config.boot.j2
vyos@ci-router1# cat /config/config.boot.2024-01-08-083418.pre-migration nat { source { rule 100 { translation { address "masquerade" } outbound-interface { name "eth0" } } } } interfaces { ethernet eth0 { address "dhcp" hw-id "52:54:00:ff:97:48" mtu "1500" } loopback lo { } } service { ssh { client-keepalive-interval "180" port "22" } } system { config-management { commit-revisions "100" } host-name "ci-router1" login { user vyos { authentication { encrypted-password "*" plaintext-password "vyos" } } } ntp { server "time1.vyos.net" server "time2.vyos.net" server "time3.vyos.net" } syslog { global { facility all { level "notice" } facility protocols { level "debug" } } } }
Jan 7 2024
Jan 6 2024
PR for VyOS 1.4 https://github.com/vyos/vyos-1x/pull/2763
The fix from 1.5 was actually not backported. Thanks for testing and feedback
Having support for vhost is handy when you dont want just to blindly share a single documentroot but have the ability to use multiple at a single host.
There is no redirect anymore