@ssasso You can test the fixed box with https://app.vagrantup.com/vyos/boxes/current/versions/20221227.20.48

@ssasso Thank you for creating the PR. I confirmed the issue with the latest box. I will check your PR today.

@hakwerk I'm sorry for the delay of the response. It seems that this PR(https://github.com/vyos/vyos-vm-images/pull/28) fixes the enable_dhcp issue.
I can't reproduce the install-grub issue for now. If I get the warning, I will try to fix it.

There is the ansible playbook for Hyper-V image in https://github.com/vyos/vyos-vm-images.

vmtoolsd --cmd 'info-get guestinfo.ovfEnv' returns "No value found"...

It seems the ovf I made works good.

I tested with only NoCloud.
I understand ovf/ova must include ProductSection with some properties like this https://github.com/cloud-init/cloud-init/blob/master/doc/sources/ovf/example/ubuntu-server.ovf
Where is the ovf @UnicronNL made?

the test image with cloud-init is here. https://dev.vyos.jp/vyos/images/rolling/current/amd64/vyos-1.2.0-rolling-201810250337-vmware.ova

@syncer @UnicronNL sorry. I did it right now on https://github.com/vyos/vyos-vm-images/commit/00a5684ba31ed5c68d168290fb45a35bf5d58177
And it seems there are two styles of VM image build. ansible playbooks in vyos-vm-images and shell scripts in vyos-build.

@syncer I read this: https://twitter.com/vyos_dev/status/1055037448093425664?s=19
so we should use cloud-init for VMware image too?
https://cloud-init.io/

I think we can remove old providers and add options for apn profile like "apn", "user" and "password".

@robinelfrink I'm sorry but I deleted the task for open-vmdk. I fixed it.

https://github.com/vyos/vyos-vm-images

https://github.com/vyos/build-ami/pull/6

@syncer we can put the changes into the image after T650. I'll work for T650 tomorrow.

Working playbook for qemu is here: https://github.com/higebu/build-ami/tree/qemu

Jenkins build setup for sonarcloud is done on https://ci.vyos.net/view/all/job/vyos-1x/ and https://ci.vyos.net/view/all/job/vyos-1x-pr/.

@syncer The result on sonarcloud was generated by running sonar-scanner on my local PC. The step for automated measuring coverage or other metrics is following:

https://sonarcloud.io/dashboard?id=vyos%3Avyos-1x

https://docs.travis-ci.com/user/sonarcloud/

Thanks!

@syncer Can you add me to vyos org on sonarcloud? I'd like to setup unit tests and coverage integration.

https://docs.sonarqube.org/display/PLUG/Python+Unit+Tests+Execution+Reports+Import
https://docs.sonarqube.org/display/PLUG/Python+Coverage+Results+Import

@syncer Yes, but we have no test code.

I think we can use Debian jessie package for 1.2.0-rolling. But for 1.1, we have to build special version, because there is no upstream package.

I confirmed qemu-ga works correctly on libvirt with vagrant-libvirt.

User space implementation in Zebra 2.0: https://github.com/coreswitch/zebra/blob/master/docs/srv6.md

Yes, it's a first step. I think the next step will be wrapper set/show commands for iproute2.

Running Docker on current vyos. https://gist.github.com/higebu/f35fdd27d085b618a872a8b46c625e2e

I started working for 1.2: https://github.com/higebu/vyos-1x/tree/cloud-init

@syncer Could you share the details of the discussion?

https://github.com/vyos/vyos-kernel/pull/16

@ebob9 Thank you! It's very helpful.

@MoyHaj Sorry for the late response. The VHD file is here: https://dev.vyos.jp/vyos/dev-images/vyos_azure_image.vhd

waagent log

my azure image works on azure too. the image is here: https://dev.vyos.jp/vyos/dev-images/vyos_azure_image.img
and walinuxagent is running on it. I'm checking walinuxagent status.

https://www.reddit.com/r/networking/comments/75c30y/create_a_static_public_ip_address_for_home_use/

Created "current" and "helium" branches.

Moved the repo to vyos org. https://github.com/vyos/vyos-integration-test

Moved the repo to vyos org. https://github.com/vyos/vyos-cloudinit

@dmbaturin I agree with adding a configure option. Dependency of VM targets you wrote is correct.

Fix for 1.1.8: https://github.com/vyos/vyos-kernel/commit/ee76a91c5468452a37dda9dd9133acc83014e95b

Fix for 1.1.8: https://github.com/vyos/vyos-kernel/commit/b080c57a1f0f005e0b6c20de67fc0add4d4a3294

Fix for 1.1.8: https://github.com/vyos/vyos-open-vm-tools/commit/c149ffb6127f52653d9ee90883fa48608a5936ec

@syncer I think we can remove this task from 1.1.8 backlog, because this is new feature.

@syncer I think we can remove this task from 1.1.8 backlog, because this is new feature.

Fix for 1.1.8: https://github.com/vyos/vyatta-cluster/commit/de4974ac517e37dc5ac6d1d65df4c2e0f9961028

Fix for 1.1.8: https://github.com/vyos/vyos-kernel/commit/3326adbda316de01bb4b620124e434183bb2d564

https://github.com/vyos/vyos-kernel/commit/9158e8196faa47205a7fee449322d0b44e8a9331

Fixed in helium branch for 1.1.8: https://github.com/vyos/vyatta-quagga/commit/e18428d724ba20af4d9282a90900de8d96758610

Sorry. It's wrong. Linux kernel through 4.9.11 is affected. So 1.1.x is affected.

VyOS 1.1.x is not affected. See http://www.cvedetails.com/cve/CVE-2017-6074/

CVE-2014-8104 is fixed by this commit: https://github.com/vyos/openvpn/commit/eb42da67b9a971a1cec94e3c65350d2e5dccf096

@syncer The version of openvpn in 1.1.7 is 2.1.3. 2.1.3 is not affected by these CVEs. See https://www.cvedetails.com/vulnerability-list/vendor_id-3278/product_id-5768/version_id-176319/Openvpn-Openvpn-2.1.3.html

Good!

@syncer I guess we need Squeeze host for building packages. But if we use pbuilder, we can build packages on Jessie.
Example script is here: https://gist.github.com/higebu/139c786fab3c88113d54eef16b462655

Packages for testing:

Jenkins job is broken. https://ci.vyos.net/job/vyatta-strongswan/

I applied the patch for CVE-2015-8023 to helium branch. https://github.com/vyos/vyatta-strongswan/commit/1f431fed4988a5e7f20a3f8ab464fed85c5f7e1c

The CVSS score of CVE-2015-4171 is low, and it needs a valid certificate for attack. Can we ignore CVE-2015-4171?

1.1.7 has 4.5.2-1.1-bpo60+vyos1+helium4. We should apply 2 patches, CVE-2015-4171 and CVE-2015-8023 to vyatta-strongswan helium branch.

@xrobau and I talked about this on IRC, and agreed on the following points.

Where is the log?