I'm pretty sure there is a commit error when you try to use that no longer existing option. It only works because we (sadly) allow partial commits and our commits at this time are not real, transactional commits.

@c-po I think the spirit of it is to keep programs that are not useful for end users separate from programs that are, out of their $PATH, which would only pollute the completion and enable accidental execution of programs that may have strange effect when used in an unintended way outside of their normal workflow.

Turns out updating the hosts entry is more important than I thought: if it's missing, sudo constantly complains that it cannot resolve the hostname. While it appears to have no ill effect, it's still quite a nuisance.

Those commands are now "monitor bandwidth interface $intf".

This task is decidedly *not* complete until we have a migration script for it.

Should be working now.

They are now vyos.version.get_version*

It gets worse: there are also handwritten bmon command templates for some interfaces (those before VC6.6 it seems).

Sorry it took me so long to react to!

Looks like pdns doesn't have a working command to reset all cache, but it has a command for clearing cache for individual domains.

Just tested it on hvinfo and it seems to work as expected. The change is in the jenkins script,

The peer-address option doesn't work quite well in keepalived 1.2.x from jessie. VRRP transition works, but then it goes into an endless loop of sending an ARP who-has request for checking availability of the virtual address.

I've added the Mellanox OFED drivers to the image. Need to check the userspace packages.

@c-po Looks like Debian has it for all platforms that support KVM, including ARM (though, oddly, not Aarch64). Perhaps we should move it from the x86 package list to vyos-world or another platform-independent place at some later point.

Please make sure to read the guideline: http://blog.vyos.net/vyos-2-dot-0-development-digest-number-5-doing-1-dot-2-x-and-2-dot-0-development-in-parallel
You can use the cron script as an example, too.

Closing the task then.

@alainlamar @c-po Multi-nodes should indeed be used whenever possible instead of making the user enter comma-separated values and the like.

Done for all practical purposes. Everything else will deserve its own task.

It's done for OpenVPN. We can later add IPsec as a sub-task.

It will have to be refactored for the new vyos-1x approach, but then the entire package will, so we'll better have the .ac support now, and refactor later.

1. A nicer version of os.system('iw reg get')

This makes me think we should make a shared nicer version that returns a tuple of exit code and combined stdout/stderr and put it somewhere in a utility module.

@tic226 If we continue the chemical theme, since 1.1.x is helium, 1.2.x will be lithium, and 1.3.x will be beryllium.

The downloads.vyos.io is now using mandatory HTTPS. On the dev.packages.vyos.net, HTTPS is optional. To declare this closed, we need someone to independently verify that ISO build works with HTTPS for them.

Hey everyone,

I'll check, meanwhile, could you verify that you still see this issue in the latest build?

@begetan Does creating it with one interface first work for you?
Also, I still need the show version output from the running instance (complete with S/N and UUID) to see if it's the same issue or a different one.

@begetan It is the same build that the marketplace team at AWS distributes to all regions. I've just made an instance in Frankfurt and it worked for me.

I appreciate your work! Could you make the patch easier for us to merge and then to track for release and changelog?
Here's the proper procedure for making patches: https://wiki.vyos.net/wiki/Submit_a_patch

@aopdal I suppose 1.2.0 will stick with quagga, though if we are able to weed out all issues with FRR in reasonable timeframe, perhaps we can attempt migration to FRR in 1.2.0 rather than a release after it.

It works for me. We need more details of your setup and your config to tell anything.