Please try again with latest rolling

We keep the proxy for authentication and filtering

need to use wpa_supplicant on a wired interface. Currently running on 1.3 rolling 2020-08-01 and used a manual entry in /etc/network/interfaces 'wpa-driver wired' . Attempted on rolling 2020-12-24 and it seems that VyOS no longer respects settings in /etc/network/interfaces so would require this capability. On boot, running sudo /usr/sbin/wpa_supplicant -Dwired -ieth0 -c /config/myconfig.conf works but no survivable on reboot

We had problems with ospf6d crashing on VyOS 1.3 using FRR 7.3 (from around August 2020). However, according to FRR #6086 and FRR #6735 this might have been fixed in FRR 7.5 (which is in latest/current VyOS 1.3).

Put in PR for op commands:

@c-po PR:https://github.com/vyos/vyos-1x/pull/658

https://github.com/vyos/vyatta-cfg-quagga/pull/60

• https://github.com/vyos/vyos-1x/pull/643 only missing part is squidguard. Smoketests are already live for the other parts.
• ddclient 3.9.1 with cloudflare api4 support not in Debian Buster
• udp-broadcast-relay -> there is no upstream Debian Package
• mdns-repeater -> There is no upstream Debian Package

After the testing with a standalone User-Data handler, this feature was ported to the main cloud-init package in https://github.com/vyos/vyos-cloud-init/pull/27.
Currently, supported only set and delete commands processing. They must be provided as a list in the vyos_config_commands option.

https://github.com/vyos/vyatta-cfg-quagga/pull/59

Hi there,

vyatta-biosdevname:
https://github.com/vyos/vyatta-cfg-system/blob/ebbdfe44aa321a2de35ddccaa255d384a5fd99e4/scripts/vyatta_net_name#L96
Used for calculating initial interface order, to try getting a ordered list and not only the random init-order used by the kernel

Does it possible to cherry-pick to 1.3? Because in 1.3 rollings we have the same bug.

PR https://github.com/vyos/vyatta-wanloadbalance/pull/8

vyatta-webproxy: 80% done, @cpo grabbed it since I had no time to continue for a while and put it on hold. I removed obsolete options which implies the need of a migration script. Ldap, AD, IP and user/passwd auth works, I removed caches, squidguard, include domain filters (just a list) and so on, but I stopped it now since it's been taken away.

Kernel modules are pre-compiled and can be loaded.

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

Thanks for the feedback and telling us about how to solve this issue.

Successfully tested on 1.3-rolling-202012230217

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?