Put in a PR to add op commands for LDP.

PR:

@runar You're right, my bad.

Created PR #648 in vyos-1x

So how are userspace packages for this sort of stuff handled? I assume we need to itemize out individual phabricator tickets?
Off the top of my head, relevant things to add to uspace would be:

1. eoip binary
2. eoip CLI wrapper
3. Xtables userspace with GeoIP table data and updater script (we would need to figure out how to deal with rule placement for persistence)
4. Xtables-related CLI for firewall matching on GeoIP, DNS, etc
5. Xtables-related CLI for firewall actions to TARPIT or DELUDE
6. UKSM userspace (or just wrappers for the sysfs interface in CLI)
7. Hardened Malloc with system-wide LD_PRELOAD or maintain a vyos-specific libc package with it built-in

The CLI command set interfaces ethernet <interface> offload-options xdp enables the XDP generic mode on the given interface.

In your example the use of ge is redundant as as you have allready specified a limiting subnettmask you cant go outside the boundry of the prefix specified.

It's FRR logic.

See PR: https://github.com/vyos/vyos-1x/pull/647

Ok. I will try to use containers, this good idea.
Containers will be more predictable and stable I suppose.

@vlesk once container support is added you have a better way by usibg a dedicates container on your VyOS installation.

If your device supports virtualization, you can consider running both VyOS and cups servers in KVM (there are many open source projects that can do this, such as Proxmox Ve)

Yes I know that I must install printer driver. I successfully solved this problem long time ago by using additional partition. And YES I KNOW that VyOS is not a general server operating system. But some time convenient use ONE universal host instead two or more.

Why install the remote print sharing service on the router and use cups, you must install the printer driver on the cups server to make it work. VyOS is not a general server operating system, so you should install cups on a physical server or virtual server

I prefer build images with some additional packages, such as cups. For example in order to administer printer I should add user to group lpadmin. In releases 1.2.x it was easy, but now I necessary after each update do it manually.

Why you would line to add a user to an additional group?

Where possible, we can consider MBR+UEFI dual boot, which also exists in most distributions

Furthermore, I've attempted changing the interfaces-wireless.xml.in priority to a value before interfaces-bridge.xml.in and it still fails. Not sure how else I can debug.

I just tested 1.3-rolling-202012141037. It actually seems to be a bug. When applying wifi settings and adding to a bridge in the same commit, I'm hit with

Pull request submitted to change the permissions:

In T1773#46307, @runar wrote:

With this, will there also be possible to parse the same json into an json import? This to allow for a more programatic way to add things than via set commands

PR: https://github.com/vyos/vyos-1x/pull/644

@primoz Use the latest rolling version test the day after the merge is submitted